Forum Replies Created
-
Posts
-
Yes, we remember about this request.
This is what the Development section of the forum was created for. And yes, we know that both Development and Help sections require an update to reflect the current state of Miqobot.You are correct, at the moment we are overwhelmed with the amount of work introduced by the Shadowbringers expansion. But when the important hotfixes and feature upgrades are implemented, we will be working on forums reorganization as well.
In the meantime, if you have any questions about the development process you can contact our Tech Support directly:
https://miqobot.com/#support
Thank you for your understanding!At the moment we are making the necessary preparations for the Shadowbringers expansion.
If you have any questions, please contact our Tech Support directly: https://miqobot.com/#supportMiqobot v1.3.24
Healer adjustments.
– (Healers) Esuna is used to remove Silence.
– (Healers) Esuna is used to remove Pacification.
– (WHM) Rotation is upgraded for 1-68.
– (SCH) Rotation is upgraded for 1-68.
– (AST) Rotation is upgraded for 1-68.Tank adjustments.
– (Tanks) Combo is no longer interrupted by ranged weaponskills when its not required for enmity.
– (PLD) Rotation is upgraded for 1-68.
– (WAR) Rotation is upgraded for 1-70.
– (DRK) Rotation is upgraded for 1-68.Melee DPS adjustments.
– (Melee) Goad is implemented.
– (MNK) Rotation is upgraded for 1-66.
– (DRG) Rotation is upgraded for 1-70.
– (NIN) Rotation is upgraded for 1-68.
– (SAM) Rotation is upgraded for 1-66.Ranged DPS adjustments.
– (BRD) Rotation is upgraded for 1-70.
– (MCH) Rotation is upgraded for 1-66.Caster DPS adjustments.
– (BLM) Rotation is upgraded for 1-66.
– (SMN) Rotation is upgraded for 1-68.
– (RDM) Rotation is upgraded for 1-70.In preparation for future dungeons and features.
– Multiple core systems are implemented.
– Multiple boss mechanics are implemented.
– New omen types are detected.Minor issues are addressed.
– Fixed an issue, wherein Miqobot would prioritize casting over stack mechanic.
– Fixed an issue, wherein Miqobot would select an incorrect recipe number when using search function under certain conditions.Yes, farming primals 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 main beta thread for updates: [Beta] Combat
Thank you for your request!Once again, we would like to kindly remind everyone to keep the conversation friendly and constructive.
We are fully aware that Miqobot is not perfect. And we also know that it never will be.
We are working non-stop to release new features as fast as possible, however the rate at which we receive feature requests far exceeds our capability of implementing them. Therefore there will always be more work to do.We always welcome constructive criticism and new ideas for improvement.
But please understand that emotional discussions do not speed up the development process.
They only slow us down because we have to spend more time on community management.Thank you for your understanding very much!
MSQ and Questing support will be a part of the Combat system, which is currently in early beta.
You can see our progress so far in this thread: [Beta] CombatThank you for your request!
Miqobot traverses beacons in increasing order of their waypoint numbers.
For example, if beacon A is #3, beacon B is #7, beacon C is #11, the order will always be:A -> B -> CThis way you are always in control how you want Miqobot to visit beacons, regardless of linear distances, navigation path distances, or unidirectional connections. If you wish to change the traversal order, all you have to do is delete beacons and recreate them in the preferred order.
The only time distance calculation takes place is the moment you click “Start”.
At this time Miqobot detects the closest beacon and rotates the sequence to make it the first to visit. But the order remains unchanged:B -> C -> A
Even if you start Miqobot at the position between A and B (with A beacon being closer at this moment), she will backtrack to A only once. But this issue is indeed very easy to avoid with the method Lyfox described.In addition, if Miqobot visits a beacon implicitly while navigating from one gathering node to another, it still triggers a sequence rotation. This rule is designed to prevent occasional backtracking when the next gathering node is visible directly on minimap and the beacon is not used.
If you have any other ideas for AI improvement, please let us know.
We would like to kindly remind everyone to keep the conversation friendly and avoid sensitive off-topics.
There is nothing wrong with healthy criticism as long as it remains constructive and useful.
So please focus on providing constructive feedback as this is the best way you can help us deliver new features faster.If you wish to discuss philosophical aspects of automated gameplay, we would recommend creating a separate thread.
Thank you for your understanding!
