Forum Replies Created
-
Posts
-
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!Indeed, this is a keybind conflict.
The game always prioritizes UI actions over hotbar actions. If you have an ingame window in focus, such as Synthesis, pressing ‘2’ key will trigger UI module instead due to ‘Ctrl-Shift-2’ shortcut assigned to Move Cursor Down.When you make a mouse click in the game, it removes focus from the Synthesis window and the UI module no longer intercepts shortcuts. This is why it seems like it’s working with the game in the foreground.
In order to prevent this issue, please avoid assigning similar shortcuts to hotbar actions and UI actions.
This issue usually indicates that there is a keybind conflict in your game settings.
Would you please give us more information?- What shortcut is assigned to Great Strides?
- What shortcuts are assigned to Move Cursor actions?
- What shortcuts are assigned to Cycle through Tabs actions?
You can find detailed explanation of this issue in our Keybind and Icons Recognition guide.
At the moment we have 1,793 pending minor feature requests.
And we believe that the arrival of Shadowbringers expansion will extend this list by a few hundreds.Converting them all to a publicly readable format will take some time. It will also further delay the release of new versions due to the necessity of synchronizing the public list and keeping it up-to-date. But if everyone agrees that it has to be done, we will of course add this to our development plans.
Thank you for your request!In the meantime, if you have any questions about development please contact our Tech Support directly: https://miqobot.com/#support
This way you will receive an answer faster than waiting for it on public forums.
Thank you for understanding!Loooooove the crafting feature of Miqo, but whenever I try to do a plus 3 minute solver she goes “Not Responding”. I’ve checked my task manager and she’s not over stressing my CPU, RAM, or anything else at all. Just curious if someone has any ideas.
Yes, this behavior is completely normal and expected. Miqobot will freeze for the amount of time displayed in the solver box. Please refer to our basic guide on Crafting Solver to understand how it works: Help – Crafting
In order to reduce the amount of time Miqobot freezes before crafting, do not enable too many CPU intensive settings at once.
Please aim for 20 seconds of solving or less.
There is almost no benefit in waiting longer, except for crafting 70**** star recipes.
You can find detailed information on Crafting Solver setup in this thread: Stormblood – Upgrade Stage 2.As well, curious if there will be any updates to the crafting AI in the near future at all. Or are devs waiting till ShB to see what will need adjusted?
At the moment Crafting Solver is fully optimized and compatible with all Stormblood recipes.
New crafting updates will be introduced after the launch of Shadowbringers expansion.MSQ and Questing features are still in development and 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!
We are very sorry, but Miqobot does not support any PvP activities.
She will immediately trigger an integrated kill switch upon entering a PvP zone.Please note that PvP activities are extremely dangerous for botting due to high player congestion.
There is a very high risk of being reported by another player in PvP. And it will most likely result in account suspension.It is true that PvP grinding would be relatively easy to implement with Scenario Engine, and it would drive a lot of attraction to Miqobot.
But at the same time it would trigger much hatred from players who prefer to grind Frontlines manually. They would most likely take it as a personal insult and initiate witch hunting, which could potentially lead to a schism in the game community and significant damage to the game itself.We care about our players very much, and we would not want Miqobot to become a tool for game destruction.
We sincerely apologize, but at this time we have to postpone all PvP features requests.
Judging from the message log, this problem is caused by an issue in Sohm Al itself wherein the first briar gate is not unlocked even after defeating all monsters and pollen clusters.
We received a similar report a while ago, but we could not reproduce it. Therefore Miqobot AI does not have any instructions on how to handle this case.
We believe that the problem is caused by a lag spike, but since it’s extremely rare we don’t have enough data to prove it.
