Forum Replies Created
-
Posts
-
Yes, this approach would probably work for level 70 exclusively.
But since we are implementing rotations for all levels we still have to consider cases when there are not enough abilities to make the rotation completely static. Also, Miqobot supports both single-target and AoE rotations and for seamless performance they have to be fully entangled.That’s why our battle algorithms are based on multi-layered priority systems, which in addition to the advantages mentioned above are capable of picking up the rotation at any moment in the fight and even handling extreme lag spikes.
Whoa, I didn’t expect development of it being so far yet.
That’s a really convenient forecast and I’m curious, what is already working by then. I guess simple jobs like DRG who has a static rotation like a brick will be ready early?All job rotations are being developed with equal priorities.
Assist Mode will allow you to use Miqobot’s combat system in any location, but this is still an early beta release so please don’t expect it to support level 70 rotations just yet.Is there by chance an ETA on the next beta release?
We are sorry, we don’t have an ETA.
Due to the arrival of new patches we are being overwhelmed with urgent hotfixes and tech support questions. The amount of work in this department is unpredictable.Please keep an eye on the latest beta thread for updates: [Beta] Combat
All low level gear you get from these dungeons can be used for Expert Delivery in exchange for GC seals. This way, you get back about 60-70% of the cost invested in the command mission.
You can also make all newly obtained gear drop into your inventory instead of the armoury chest.
This option can be found in the game under System -> Character Configuration -> Item Settings.In addition, our community has already created several scenarios that automate the Expert Delivery process after each run.
You can find them here: Squadron ScenarioSo we apologize for asking twice, but we have to make sure that we understand the request.
You would prefer Miqobot to ignore all treasure coffers and abandon the Expert Delivery reward. Is this correct?Thank you very much, additional data is not required 🙂
We have managed to reproduce your issue and identify the cause of this behavior.The problem is caused by the BRD ability Foe Requiem.
It is capable of pulling mosnters without direct line of sight and even from areas locked behind the fire wall. This event triggers a standard mechanism designed to handle face pulls, but since those monsters are unreachable it results in AI deadlock.As a temporary workaround, please remove Foe Requiem from your hotbar.
We have to carefully review and redesign Foe Requiem algorithm in order to prevent this kind of issue from happening in the future. In addition, we will create special triggers to detect similar cases and interrupt AI deadlocks. These solutions will take some time to implement and most likely will be released in the next beta version.
In the meantime, please use the workaround described above and don’t let Miqobot use Foe Requiem.We apologize for temporary inconvenience.
Yes, Assist Mode is planned for release in the next beta update.
It will support all locations, including Eureka Pyros.
The battle rotations however are still in development, so please don’t expect full level 70 optimization from the start.As the core combat system is now stable enough for the first iteration of Assist Mode, there will be an intermediate release before we continue working on battle rotations for high level tiers.
Thank you for your request!Yes, additional collectability settings for gathering and crafting are already planned.
Currently they are classified as Quality-of-Life improvements, therefore new combat features are of higher priority. But we will try to push some QoL upgrades into one of the upcoming betas.Thank you for your request!
You can safely use Miqobot on as many computers as you like.
Just be careful if you copy catnip.license file, because it stores your license code in ecnrypted format and Miqobot won’t be able to decrypt it on another computer.
You can find more information in this thread: Question regarding licenseYes, this is a possible workaround and we have recently researched this option.
Unfortunately, it turned out to cause even more problems later.Disengage command works only once until the first ice sprite dies. After that, the squadron tank stops fighting again and runs away to pull a dragon aevis anyway. It seems that Engage command puts your current target in a permanent enmity list of all squadrons and it inevitably becomes their primary objective at the first opportunity.
It may lead to even more problematic cases wherein all your squadrons leave you alone in the middle of the fight.Therefore in order for this solution to work consistently, Miqobot would have to spam Disengage command constantly throughout the whole fight after each monster kill.
However, this is additionally complicated by the fact that Disengage makes the squadron healer to stop healing completely for a few seconds regardless of consequent Engage commands. In this light, a temporary disobedience of the squadron tank seems to be the lesser evil.Perhaps you are right, and Miqobot should keep the player character in the back even when leveling a melee DPS.
We would like to investigate this issue further before we decide on the final solution.
Thank you for your assistance very much!Yes, it will be possible when we implement additional scenario functions for custom fights.
We have to make a few more iterations in order to make the Combat system stable enough for scenario usage.Please keep an eye on the latest beta thread for updates: [Beta] Combat
Thank you for your request!Yes, we are aware of this issue but we couldn’t find a workaround.
There is a bug in squadron tank AI which prevents them to follow the Engage order under certain conditions.You can verify this by spamming Engage manually while fighting ice sprites, and the tank NPC will still ignore your commands and simply run away to pull a dragon aevis.
This is not a critical issue and it doesn’t break anything, except an occasional KO event which Miqobot can easily recover from. Therefore we decided not to delay the release any further.
Please let us know if you discover a reliable solution, and we will implement it in a future update. Thank you very much!Miqobot v1.3.16
Important Note.
Rook Autoturret (MCH) requires placement macro setup.
Please read the new guide section on Placement Macros in the first post.New dungeon is supported.
– (Lv41) Stone VigilSpecial cleave mechanic is implemented for certain bosses.
– Tanks will attempt to face the boss away from the party, while other jobs will avoid standing in front of the boss.Several improvements are implemented.
– Arena algorithms are adjusted to support bigger areas.
– Ungarmax safety condition is adjusted.
– Pull delay for non-tank jobs is adjusted.
– Aetherial barrier detection at dungeon start is implemented.
– Melee-caster movement for certain jobs is implemented.Several issues are addressed.
– Fixed an issue wherein a healing cast would be intentionally interrupted under certain conditions.
– Fixed an issue wherein Miqobot would lose track of navigation mesh if a monster is pulled immediately after KO event due to persisting DoTs.
– Multiple minor issues are addressed.
