Forum Replies Created
-
Posts
-
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.Yes, this feature will be a part of the future Gathering updates:
In fact, we were planning to work on this feature next. However, our community has decided that Gathering improvements must be postponed in favor of (Lv80) Trust Dungeon support.
Please refer to this thread for details: Level 80 Trust DungeonI at times reach points where Miqo chooses to spam patient touch and rapid synthesis… to the point where it fails melds as a result.
Miqobot does not include an emotional response. Regardless of how many times Patient Touch fails, Crafting Solver continues to follow the optimal synthesis path. It will make no attempt to salvage a failing craft.
There is no magic that would allow RNG abilities to succeed. If the RNG has decided that the current synthesis must fail, it will fail.However, when Crafting Solver detects a 100% solution that does not depend on Good / Excellent procs, it will stop using RNG abilities automatically.
DO you reccomend ALL abilities be present on bars?
It depends on your goals.
– If you craft a lot of expert recipes and would like to achieve maximum rating over a big number of crafts, then yes, RNG abilities are paramount.
– If you craft only a few recipes and would like to see a stable process instead, then please remove RNG abilities from hotbar.Yes, this feature is already planned. It is classified as QoL improvement.
We will be working on Quality-of-Life improvements after Scenario Engine updates:Thank you for your request.
At the moment there are three possible workarounds:
- If you don’t wish Miqobot to use a certain ability, you can remove it from your hotbar.
- If you still wish to be able to use it yourself, you can put it in a macro and hide it behind a different icon.
- If you need to see the cooldown as well, then you can place it on Cross Hotbar.
If neither of these methods work for you, then we don’t have any other suggestions.
We sincerely apologize for inconvenience.What exactly do the %s mean for the abilities?
This setting indicates the race progress percentage at which Miqobot should use an ability.
For example, in order to use it at the start, this setting should be set to 0%.
You can also find additional information in our Help section: Chocobo RacingIf this information doesn’t help, then please contact our Tech Support and we will do our best to help you: https://miqobot.com/#support
We haven’t discovered any viable alternatives to (Lv53) Sohm Al.
- (Lv60) dungeons give -32% of Sohm Al experience and thus are not efficient.
- (Lv57) The Vault gives +3.6% experience boost, but the wipe rate becomes extremely high due to many mechanics hitting your character for 90% HP.
If you have any other ideas, we are open to suggestions.
