Forum Replies Created
-
Posts
-
Monk rotation is updated.
Please refer to the main status thread for details: Miqobot v1.3.39 – Patch NotesWe are sorry, this feature is technically very complex and would 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. At the moment this feature has a low priority.The details are explained in this thread: Save/Load solver alghoritms
Please note that Crafting Solver already has a cache.
If you craft two different recipes with the same stats and the same set of abilities, there will be no recalculation. But even a single change in the input data triggers cascading changes in the solution map.I am asking purely for curiosity — is there the possibility of if/elseif/else blocks in Scenario Engine’s future?
For the reasons mentioned above, creating complex mechanisms usually available in programming languages is not a priority.
But if there is enough demand and the community decides that it justifies postponing other features, the development plans will be adjusted.Or if not that complex, perhaps a jump command for moving between chapters?
Yes, special functions for switching chapters and scenarios without a call stack should not create additional complexity and are already planned.
Yes, we researched Chocobo Challenges but haven’t managed to find a simple solution for them.
Due to unique navigation layouts and additional data patterns, this feature will require a full development cycle of 4-8 weeks. At the moment this activity is not popular and the community demands other features. Chocobo Challenges are at low priority.Miqobot v1.3.39 – Patch Notes
Combat
- (Lv80) Heroes’ Gauntlet support.
- (MNK) Rotation is reimplemented in accordance with Patch 5.4 changes.
- (MNK) Enlightenment is supported.
Crafting
- When crafting level 80**** recipes, Miqobot will prefer the Muscle Memory opener.
- Intensive Synthesis efficiency is adjusted.
- Fixed an issue, wherein certain r460 recipes were incorrectly identified as r450.
Scenario Engine
- New fish are supported.
- Fixed an issue with Aetherial Reduction, wherein it did not detect the item animation correctly.
In accordance to the previously announced schedule (link), Collectable Gathering is still broken.
During the next 2 weeks, the development process will follow the announced schedule.
– Implementation of new gathering mechanics.This issue usually indicates that there is a keybind conflict in your game settings.
You can find the detailed explanation of this problem in our Keybinds and Icons Recognition guide.Our Tech Support can analyze your keybind mappings and identify the exact cause.
If you require technical assistance, please contact us directly: https://miqobot.com/#supportsuggestion : can you add a “pause” button ? and resume too
Yes, pause is planned for all features. It is classified as QoL improvement and will be implemented along with the rest of Quality-of-Life updates: Upcoming Features
Thank you for your request.We have investigated your issue.
According to our logging system, there are irregular downtimes in your Miqobot application activity. We do not observe this pattern with other connections, so it appears that there is a problem with your internet.If you require additional assistance, please contact our Tech Support and we will try to help you with network diagnostics: https://miqobot.com/#support
All right, we will consider your suggestion for the future development.
Thank you very much.In any case, better Diadem support is one of the things planned in Gathering Updates. We will try to design special functions for weather-based decision making. Once we find a suitable solution, it might be possible to generalize it for time-based chapter selection as well.
Would like miqo to implement this routine for retainers 😀
Yes, additional scenario functions with native retainer support are already planned.
They will be implemented along with the rest of Scenario Engine updates:Thank you for your request.
This feature would be an extension of a more basic mechanism – the ability to call scenarios recursively.
Such algorithm would require an implementation of call stack which is a rather complex mechanism in itself. We will look into this when we start working on new Scenario Engine functions.Please keep in mind that this system will occupy a full development cycle and may be implemented only at the cost of other features. But we will try our best.
