Forum Replies Created
-
Posts
-
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.Yes, this feature will be a part of the upcoming QoL feature pack.
In the meantime, please use the workaround mentioned by Arc:- Close your Miqobot.
- Open presets.miqo in any text editor.
- Disable “Word Wrap” setting. (Located under “View” menu in most editors.)
- Follow our guide to understand the inner format: Help – General
- Adjust presets order to your liking.
- Close presets.miqo and restart Miqobot.
I encountered the weird bug a couple of other people mentioned in the past, Miqobot Assist stop doing something at a 3rd summons of The Shifting Altars of Uznair.
I think it was for a lesser summons.
I tried pause/unpause, stop/restart, didn’t work. We got ejected after, so I don’t know if for the next summons Miqobot could have worked, what I can tell, is that once outside, she started to work again.I was running as PLD.
Yes, we have managed to reproduce this issue a while ago.
- It happens under very rare circumstances due to a bug in the game client, which allows the Cast Bar to remain active (albeit invisible) if it is interrupted by a cutscene, a loading screen, or in another non-standard way.
- In addition, another bug may occur randomly wherein the Cast Bar would indicate that it’s not interrupted and is still proceeding normally.
- When both of these bugs occur at the same time, it affects Miqobot’s ability to identify the Cast Bar correctly. She assumes that a cast is still in progress and therefore does not attempt to perform another action.
In order to recover from this problem, all you have to do is initiate the cast manually once. You can immediately interrupt it by moving.
The purpose of this action is to trigger the normal behavior of the Cast Bar, which will allow Miqobot to identify it properly once again.As this issue is extremely hard to reproduce, it will take some time for us to design a proper solution.
In the meantime, if you encounter this problem again please use the workaround described above.
We sincerely apologize for inconvenience.my miqo start jumping inside boss aoe in squadron dungeons, anyone know what my problem?) (sry my bad english)
Our Tech Support has contacted you by email.
Please send us the information requested and we will do our best to help you.What would you guys think about a feature to enforce the max collectability. To ensure the solver doesnt spend cycles using hasty touch and observe when i only need the bar to be half full for maximum scrips.
Yes, this feature has already been requested and planned for implementation.
In the meantime, if you don’t want Miqobot to use Hasty Touch or Observe you can simply remove them from your hotbar.
Thank you for your request!I’ve always been of the opinion that the priority should be small efford, big impact.
Examples would be inventory conditions (if inventory has 3 slots left go turn in, repair, keep farming, max collectability (to save alot of time), diffrent collectability for diffrent fish, etc.I agree that the combat system is massively helpful and has to be done, but it would be good if someone in the team could dedicate some small time to QoL changes, but then again, i have no insight into this teams working and im very happy with the product.
At the moment we have 1,748 pending minor feature requests. We agree that implementing them would indeed make Miqobot more flexible and versatile, but at the same time the Combat system would never see the light of day.
We apologize if our priorities made you unhappy.
