Forum Replies Created
-
Posts
-
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!I wouldn’t mind honestly saving a few gig files on HDD to save recalculations.
The main problem is not HDD space, but technical complexity and limited value.
It would take approximately 4-8 weeks to implement this feature and it would still require 30-60 seconds to compress and decompress solution maps.Maybe i’m doing something wrong, but switching from different food/pots def recalculates whole thing. I’ll check maybe I have some missmatched materias in my tools.
Yes, this is correct.
Using different food alters your character stats and changes the input data for Crafting Solver algorithm.It takes a 5.3 min for me to do with all options checked.
There is very little benefit in activating all options at the same time.
You can find the list of recommended settings in the patch notes for Crafting Solver upgrade:
Miqobot v1.3.34 – Patch NotesThis question has already been answered a few times.
The short answer is because this feature is technically very complex and will not result in a significant boost.
Saving and loading solutions will require additional CPU time due to compression and decompression, and this time is comparable to solving itself. This feature is classified as QoL improvement and has a low priority.The details are explained in this thread: Save/Load solver alghoritms
Also I don’t understand why Miqo needs to redo Solver for different items if a lot of items have same difficulty with the same amount of Durability.
If you craft two different recipes with the same parameters, the same character stats, and the same set of abilities, there will be no recalculation indeed. But even a single change in the input data triggers cascading changes in the solution map and it must be reconstructed from scratch.
All right, we will consider your proposal.
Thank you very much.If I may piggyback this thread for another dancer assist mode issue?
For Assist Mode feedback and similar questions, please use the main feedback thread:
Shadowbringers – Issues & FeedbackThis issue usually indicates that you haven’t removed keybind conflicts from chat actions.
You can find instructions on how to avoid this problem in the [Beta] Combat thread.Important Note!
Please remove any keybinds from “Reply” and “Switch Chat” actions.If you use the common WASD style for navigation, there’s a very high chance that a keybind collision will occur if Miqobot sends key input at the same time.
For example, if you assign Alt+1 – Alt+= to a hotbar Miqobot uses at the moment and press S at the same time, the resulting keybind will become Alt+S which by default triggers “Temporarily Switch Chat Mode to Say”. This will activate the chat mode in the middle of the fight and break your movement completely.
In order to avoid this problem, we recommend to fully clear the Keybind -> Chat tab.(You can leave the first two actions intact: “Ready Chat Log” and “Ready Text Command”.
Assuming they contain no Ctrl / Alt / Shift modifiers.)
