Forum Replies Created
-
AuthorPosts
-
Of course, both Venture support and Materia Extraction are already planned in the form of new scenario functions. They will be a part of the upcoming Scenario Engine updates:
Thank you for your request.
Is the 80 trust dungeon support going to include the 80 rotations for more combat classes or is that a seperate part of the process?
Combat rotations are gradually improving over time.
Each update introduces new abilities support, but we can not implement them all at once.Out of Curiosity is the update going to be for all level 80 trusts or just one?
The update will include one level 80 dungeon.
Yes, this function is already planned along with the rest of Scenario Engine updates:
Please note, however, that selecting a string and selecting a levequest are in fact two different functions. In general, every additional ingame window to be supported by Miqobot will require a separate algorithm.
Understood, thank you for clarification.
In this case yes, this feature is already planned. It is classified as QoL improvement, because it will not introduce new features to the crafting system besides the ability to share rotations. Implementation of this kind of UI will require a full development cycle.
Quality-of-Life improvements are planned after Scenario Engine updates:Thank you for your request.
Custom fights and Monster grind are not supported at the moment.
These features will be a part of the upcoming combat system which is currently in early beta. You can read about our progress here: [Beta] CombatFor additional information about open-world combat, please read this thread:
Asking the community: Thoughts on Open World Combat and User ProtectionThank you for your request!
Currently, crafting has solver, and a line for macros–which don’t save.
Would you please clarify this part?
Miqobot has a special list on the right side of UI that is dedicated to saving crafting macros.– a notes section like on the navigation page for the crafting tab.
All right, we will add your suggestion to the list of QoL improvements.
– in a perfect world id love to see a rotation tool for the crafting tab (like the gathering one).
Would you please clarify your request? Miqobot offers two crafting methods, Macro Crafting and Crafting Solver. Which of them do you wish to be improved exactly?
– runScenario(Name)
– runScenarioUntil(Name)
– toChapter(x)
Yes, these functions are already planned for implementation along with the rest of Scenario Engine updates.
– id love a way to define variables even if its just integers.
Defining variables is a step towards making scenarios unnecessary complex, and this is something we would like to avoid.
But we will try to implement a similar functionality.– useCorials(0/1)
This setting is activated or deactivated automatically as a part of gatherPreset() function. You can also use a cordial via sendIcon() function.
Additional function with automatic hotbar slot detection is planned as well.– if the Scenario Engine gets expanded an option to reorganize the scenarios/chapters would be nice.
Yes, this feature is already planned.
Thank you for your feedback.All right, we will consider your request.
However, this feature will require a more reliable way to identify the correct moment to activate Sprint.If we implement it as a simple auto-sprint during movement, Miqobot might use it when it’s not needed or even undesirable. For example, if you make a simple side step to dodge an AoE omen, sprint is most likely unnecessary. But since Miqobot doesn’t know your intentions, there will be problems with discerning between continuous movement and short steps.
Another request / idea, and let me know if this is something I should do myself as a scenario type of deal but what about applying food buffs / squadron battle manuals before dungeon runs?
Yes, food and battle manuals usage is already possible with Scenario Engine. All you have to do is place the desired item on hotbar and activate it via sendIcon() function.
Miqobot, do you have an estimate about when the Lv 80 trust dungeons will be supported? Much appreciated! Thank you always for the hardwork.
As we already said, the standard development cycle is 4-8 weeks.
In addition, the recent series of game patches has created a period of congestion. Each game patch downgrades existing features and extends the workload by 1-3 weeks. -
AuthorPosts