Forum Replies Created
-
Posts
-
Thank you for providing the requested information.
In this case, please try removing the Shift modifier from Mudra keybinds.The problem is caused by the fact that Miqobot can not send a composite keybind instantly, because the game requires a delay for it to be registered. On average, it takes about 250-500 milliseconds more to send a Shift shortcut versus a single key shortcut. And since the Mudra cooldown is only 0.5 seconds, the most likely outcome is that the cooldown animation completes before Miqobot has a chance to notice it.
Thus, for Miqobot it looks like the Mudra action wasn’t triggered and she tries to activate it again.You can find additional information about this problem in our Keybinds and Icons Recognition guide.
This is why we recommend to have all the most important skills to be mapped to the shortest shortcut possible.
There are multiple factors that may cause this problem.
Since Miqobot doesn’t use code injections, she has a limited number of tools to track the correct Mudra sequence. These factors were always present and the GCD queueing algorithm has of course introduced additional restrictions.First of all, would you please clarify, what keybinds have you assigned to each of the Mudra actions?
According to our logging system, you attempt to run Miqobot in trial mode.
We are very sorry, but unfortunately our trial system is not available.It was abused many times and some users have tried creating exploits to use Miqobot for free. Therefore fixing the trial system is a low priority task at the moment.
We sincerely apologize for inconvenience.A setting to disable AoE rotations is planned, but it’s not a trivial one.
The only solution you have at the moment is to remove AoE abilities from your hotbar, and Miqobot will have no choice but to perform a single target rotation. But if the fight requires constantly switching AoE on and off, then of course it will not suffice.There is another workaround.
You can create two hotbar manipulation macros. One will remove AoE abilities from your hotbar and the other will quickly put them back./hotbar remove 9 1 /hotbar remove 9 2 /hotbar remove 9 3/hotbar action "Quick Nock" 9 1 /hotbar action "Rain of Death" 9 2 /hotbar action "Shadowbite" 9 3This example assumes that you’re playing Bard and your AoE abilities are placed on hotbar 9 in slots 1 / 2 / 3 respectively. Please adjust them to your own hotbar setup.
We understand that this is an extremely unnatural solution, but it’s the only one we can suggest at the moment.
We sincerely apologize for inconvenience.Yes, there is.
Here is the list of settings that must be disabled in order to deactivate 3D Radar overlay completely:- 3D Radar tab -> Show -> Nothing.
- 3D Radar tab -> Show FATEs -> List / World.
- 3D Radar tab -> Show Gathering -> Out of reach.
- Navigation tab -> Show on radar.
- Gold Saucer tab -> Racing -> Show -> Rails / Mid-rail / Progress / Waypoints.
- Combat tab -> 3D Radar -> Show arena.
- Combat tab -> Assist -> Pause -> Show pause status.
You can verify that 3D Radar is deactivated by looking at the top left corner of the game.
- If you see a transparent box, it means 3D Radar application is rendering the overlay window.
- If the top left corner is empty, it means 3D Radar application is deactivated.
Is customization strictly “fonts/color scheme” and nothing else?
Yes, it is.
Would the ability to maximize Miqo’s window be part of the customization update, or an overhaul?
In order to resize or maximize a window, it must have easily resizable elements.
For example, you can already maximize the Gathering Rotations designer, because its UI elements were originally designed to be resizable. Main Miqobot window has only one easily resizable element – the message log, which is probably not what you wish to resize to begin with.So if we start working on the ability to maximize Miqobot window, we need a different UI layout that was originally designed to be resizable.
Alternatively, we need a special algorithm of new space distribution as it was explained by @vixen in the post above.The voting period is now complete.
The results are as follows:- 62% – Quality-of-Life updates.
- 11% – Scenario Engine updates.
- 9% – Triple Triad support.
- 6% – Level 61 Dungeon support.
- 4% – Blue Mage support.
- 2% – Gathering updates.
- 0% – Patch 5.5 Dungeon support.
- 0% – Level 60 Dungeon support.
The rest (6%) is spread equally among the following:
1 vote – Rotations Customization
1 vote – Additional Rotation Optimizations
1 vote – Automatic ReloginIn accordance to the community demand, we begin implementation of Quality-of-Life updates.
Thank you for your contribution to Miqobot project!Voting results will be reflected on the development roadmap:
Please keep in mind that the roadmap is for informational purposes only.
The community demand might change in the future, so we will hold another voting period after the next development cycle is finished.Thank you everyone for your feedback very much!
First, we will answer the questions posted during the voting period.Could you add sorting by name of gathering lists, maps and scenarios?
Better yet, a search by name.Yes, this is one of the features in Quality-of-Life updates.
Would it also be possible to add a function like “if character level is xx move to next scenario step”?
Yes, new scenario functions belong to Scenario Engine updates.
This request refers to “Switching chapters and scenarios” entry in the planned functions list.The UI could also need a modern touch. This may doesn’t sound like a huge thing, but it would make it look much cleaner and more professional.
and I second what another here has said, that the UI could use an overhaul.
Please note that UI overhaul is not on the list of proposed features at the moment. Quality-of-Life updates contain UI customization which refers to the ability to change fonts and color scheme, but it’s not the same as redesign.
A complete UI overhaul would require 3-5 months and a complete feature freeze.
While it is classified as a QoL improvement, it is not minor at all. Once we begin this process, it will be impossible to switch development priorities in the middle. And if the result turns out worse than you expected, it will be impossible to go back after that.If you believe that the risks are justified, please voice your opinion in this thread: GUI Update
The beta post mentions vendor npc interactions, could this also include the scrip vendors?
Yes, of course.
– Smart food and manuals usage. (I think that includes medicine for crafters?)
Yes, it does.
could you add an Auto re-login upon disconnection?
We tried to implement this feature already, but unfortunately we encountered several problems.
If Miqobot attempts to relogin while the connection is not restored, the game displays a lobby server error and closes the client completely. And in order to restart the game client, your login and password would be required which is a serious security concern. As we don’t have a better solution at the moment, this feature is assigned a low priority.Logging out function maybe?
Yes, a logout() function is planned in Scenario Engine updates.
just wondering, when 6.0 comes what’s the first thing that Miqo is going to get back up?
Just like with any game patch, all features will be restored for 6.0 in a single core update.
If you ask about what features will be upgraded for level 90 first, then we don’t have an answer at the moment. It will depend on the community demand after the arrival of Endwalker expansion.
If there is a question we missed or if you have additional suggestions, please use the main feedback thread:
Shadowbringers – Issues & FeedbackThank you for clarification very much.
All right, we will consider your suggestion.The problem with this approach, however, is that gathering is an open-world activity.
If we include a default profile for leveling, everyone will be using it and things might get very dangerous. Since everyone would be taking the same navigation routes, certain areas of the game would get unnaturally overcrowded and draw unwanted attention.By allowing users to choose their own leveling method and design their personal adventures, we keep the community scarce and diversified. And yes, we understand that we might lose a few subscribers along the way, because some players do not enjoy managing presets and would prefer a single leveling button instead. But this is a little price to pay to keep the project running in the long term.
Of course, if you create a combined leveling scenario and share it with the community, we will be very grateful and will include it in the Scenario Index thread.
But we are not sure if making it a default Miqobot profile would be beneficial in the big picture.Thank you for your feedback very much!
Would you please clarify, what exactly do you mean by a revamp of scenarios?
If you ask about additional scenario capabilities, then this is already on the list of planned features.
If you ask about presets created by the community, then this is a little bit harder to achieve.We do not impose any quality standards for the navigation grids and scenarios that our users create.
Do you suggest we start doing so?And is it even possible to have the bot gather multiple item’s at once?
This is one of the additional improvements planned under Gathering updates.
If you wish for it to be implemented sooner, please send your vote by replying to this thread: Voting: Next FeatureThank you for your request!
This issue indicates that there is another application interfering with Miqobot.
Please contact our Tech Support and we will do our best to help you: https://miqobot.com/#supportAssist Mode is an attended Miqobot mode and does not support AFK farming by design.
The feature you ask about belongs to a separate feature pack called open-world combat.Our community assigned a low priority to this feature due to inherent danger posed by open-world combat. Therefore we focus on implementing private instance activities and Assist Mode instead.
For additional information about open-world combat, please read this thread:
Asking the community: Thoughts on Open World Combat and User ProtectionWe will consider your voice in our development plans.
Thank you for your request!
