Forum Replies Created
-
Posts
-
Yes, 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.The event zone is unlocked in Miqobot v1.3.16 Beta.
There are still a few important tasks that we have to complete before we make the official release announcement, but the new version is already available for download: [Beta] Combat
It appears that you have altered the default Target Filter settings in the game.
Please follow these steps:- Open System -> Character Configuration -> Control Settings -> Filters tab.
- Make sure that the following settings are checked:
– Enable target cycling.
– When weapon is sheathed -> NPC/Objects.
– When weapon is drawn -> NPC/Objects.
Did it help to resolve your issue?
Korean version is on a different patch schedule. At the time of writing Korea plays Patch 4.3 versus the international version has seen updates for Patch 4.4.
Therefore the reason is the same as to why Miqobot breaks after every game patch.
The memory layout is significantly different, and we would have to reimplement several critical modules from scratch. This also implies that we would have to support two versions of Miqobot and keep track of two patch schedules, which would drastically affect the development of core features.As much as we would love to help Korean and Chinese players with the tedious grind, we simply don’t have enough resources to make it happen at the moment.
Please accept our apologies.Thank you for asking!
From the technical point of view, Korean version is an entirely different game. Therefore it will take twice more work to adapt Miqobot for Korea.
At the moment we focus on implementing core features and polishing the AI.
After we catch up with the core development, we will be ready to talk about a new project.Thank you for your interest in Miqobot very much! But right now we can not give any ETA on KR version support.
We sincerely apologize for inconvenience.The event zone is unknown to Miqobot because it did not exist prior to the release of the current version.
By default, all unknown locations are locked for automation.While we can unlock it for the current event, the problem is that it’s an area of high player congestion and therefore is extremely dangerous for any kind of automation. We would highly recommend to avoid using Miqobot in this location.
We are sorry, we don’t have an ETA.
Due to the arrival of Patch 4.4 we are being overwhelmed with tech support questions and new feature requests. The amount of work in this department is unpredictable.We implement dungeons for each level tier as we make progress on combat rotations.
Next tier is level 40-50.Yes of course, custom fights are already planned. You can read about upcoming combat features in the latest beta thread.
If you wish to vote for a feature request, please reply to the corresponding topic.
We review all threads and remember all feature requests. So a new reply in a request thread is an indication for us that the request is still relevant and depending on the current state of development we may be able to increase its priority.Thank you very much!
