Forum Replies Created
-
Posts
-
Miqobot can not recognize the new Ishgard area because it did not exist when we released the previous version.
In addition, Ishgard Restoration is not supported by deliverCollectables(). It requires a new scenario function.We are already working on it and will try to push this feature into the next version.
Thank you for your request.Yes, automatic pause for chat is planned for all features.
It’s not as trivial as it seems, because certain Miqobot modules will break if interrupted by chat. They have to be carefully redesigned before interruptions become possible. Otherwise, we would implement it a long time ago.We are working non-stop to release new features as fast as possible and we thank you for your patience.
I know the limitations of the Crafter Solver and will make my most important High Level Craft manually if needed.
Here i have again a mysterious behavior where the Bot uses the same Calculation for 3 different recipes.
Those recipes have the exact same difficulty so the bot is brilliantly, thank you for this, reusing his calculation.
But as you will see on the third item he decides to go full Synthesis ….Yes, this behavior is caused by the same issue as already mentioned in the previous posts.
The Crafting Solver hasn’t adapted the new math and may perform unpredictably.
Please refer to this post for detailed explanation: Shadowbringers – Miqobot StatusThe reason why it happened only the third time is because the first two cases were affected by Good condition procs as indicated by Precise Touch. Crafting Solver rotations are dynamic and every proc affects the entire synthesis sequence.
In your particular case, the problem is caused by the combination of Ingenuity and Rapid Synthesis. Please keep in mind that there is no guaranteed solution at the moment, but we would suggest temporarily removing Rapid Synthesis from your hotbar.For protection and making the calculation easier maybe the use of the fantastic skill that shields the synthesis to one less than the maximum could be cool.
Yes, Final Appraisal is also planned for implementation.
Thank you for your request.This system is fantastic, but, I know I don’t teach you anything, there’s still moments where we would need to turn off momentarily AoE, to prevent killing/damaging targets where fight mechanics require to handle them in a specific way, such as the current new Alexander Ultimate, where players must take care of linked dolls without killing them, as well as taking care of keeping the Living Liquid and Hand Liquid within the same HP percentage, etc.
Miqobot is too efficient there, she destroys everything, it’s beautiful, but deadly. And if Alexander is later anything like A8S, I see where we would have to handle the 4 robots by keeping each of them at different HP percentage in the same area.I know nothing is easy, and that you likely had that planned already for the Raid features, but since Miqobot already knows how to do AoE and Single target, if it is possible to implement in advance a feature similar to the Pause one, where we can set up ourself a keybind to go from Default (the current mode where Miqobot herself choose when to use AoE) to a forced Single Target mode, that would be awesome.
I agree with Carl. Sometimes we shouldn’t use AoE even when there are multiple enemies for mechanics. So far I always paused miqo and do it manually but it would be nice if miqo can do as Carl’s suggestion.
Yes, a setting to disable AoE rotations is planned, but it’s not a trivial one and we won’t be able to implement it for the current Ultimate race.
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.Better control of cooldowns via hotkeys would be nice too. I would like for Miqo to not dump cooldowns on the trash pull prior to a boss.
Precise cooldown customization is planned as well, but it will take more time to implement.
If you wish to temporary disable a certain ability, please use the workaround described above.Just had this error happen.
It happened after finishing a GC squadron, i left the room and then teleported to Mr Dhona, whilst the zone was loading that error popped up before the zone had full appeared on screen.
Thank you for reporting.
We will analyze your issue and will make the necessary adjustments to prevent this error message in the future.Can you add support for the new Gorilla mount? Miqo doesnt recognize it and wont mount if its the only mount of hotbar
Of course, we are already working on that.
In the meantime, please use a simple workaround by creating a macro with an icon of another mount./micon "Fenrir" mount /mount "Ufiti"Is there any workaround to deliverCollectables() in firmanent at the moment?
Ishgard Restoration is not supported by deliverCollectables(), it requires a new scenario function. We are already working on it and will try to push this feature into the next version.
Thank you for your request.We are very sorry, but we can’t.
This feature is already planned, but at the moment we are not ready to implement it.
As simple as it sounds, there are many hidden issues that must be carefully analyzed and resolved, otherwise it will do more harm than good. A few of them:- In order to login with the correct character, Miqobot must identify your server and save your character name between sessions. Users may see it as a violation of privacy.
- Certain disconnection errors force the game client to close. In this case, Miqobot will require your Login and Password to relaunch the game which can put your account at risk.
- Each disconnection and login may attract unwanted attention from your friends and FC members since they receive notifications about your actions. If they try to communicate with your character, you have to be able to provide a human response.
There is a total of 17 related issues in our development plans. We are working on them when there is time, but critical upgrades must be implemented first.
We sincerely apologize for inconvenience.Tank stances and defensive cooldowns are now classified as buffs. You can disable “Heals and buffs” setting and they will no longer be triggered.
In addition, Miqobot will not use Provoke without a tank stance.These adjustments were tested in alliance raid environment, but as always we are open for feedback.
You can find additional information in the latest patch notes: Miqobot v1.3.29 – Patch Notes
Final Appraisal does not advance the synthesis step and may indeed break your macro.
However, there is a simple workaround for that. Please create the following ingame macro and put it on your hotbar instead of Final Appraisal:/ac "Final Appraisal" /ac "Delicate Synthesis"This macro will execute two actions at step #8.
Thank you for reporting.
As we stated in the main status thread, Crafting Solver was not tested with 71+ content and may perform unpredictably. Especially if you are using Ingenuity.
Please refer to this post for detailed explanation: Shadowbringers – Miqobot StatusIt will take time before Miqobot adapts the new crafting math.
If you are not satisfied with the current state of Crafting Solver for any reason, please consider resorting to macro crafting for the time being.
