[MiqobotKeymaster]

As it was already mentioned, this feature will not remove the recalculation time completely.
Regardless of the storage, it would still require 30-60 seconds to load and unload solution maps after every change in the input data. Instant loading is physically impossible.

[MiqobotKeymaster]

For Assist Mode feedback and similar questions, please use the main feedback thread:
Shadowbringers – Issues & Feedback

Diplomacu wrote:

(11:27:58 PM) Uhoh. There’s no key bound to action ‘Switch to Hotbar 3’.
Any idea what this is for?

This message indicates that you’re missing an important keybind in the game settings.
You can find it under Keybind -> System -> Switch to Hotbar 3.

Please take a look at this guide for detailed information: Keybinds and Icons Recognition

Diplomacu wrote:

and for the SCH question does it heal NPC’s? (mainly for certain dungeons where you gotta keep them alive)

Miqobot heals party members only.
If you are in a dungeon with Squadron or Trust NPCs, then yes, Miqobot will target and heal them.
If you are in a duty without a party, then no, they will be ignored.

Diplomacu wrote:

also the sacred soil macro would just be a /cast sacred soil macro right?

Here is an example of placement macro for Sacred Soil:

/micon "Sacred Soil"
/merror off
/ac "Sacred Soil" <t>
/ac "Sacred Soil" <me>

You can find detailed explanation of placement macros and how to create them in the main combat thread:
[Beta] Combat – Placement Macros

[MiqobotKeymaster]

We are sorry, but this is a duplicate thread.
Please continue the discussion here:
Blue Mage Support

If you wish to see the latest community voting results, please read this thread:
Voting (June 2 – June 9, 2021)

[MiqobotKeymaster]

This issue usually indicates that Auto-Lock Target setting is enabled.
It is not related to Assist Mode or Miqobot in general, this is an ingame setting that you can toggle at your own convenience.

You can find it under System -> Character Configuration -> Control Settings -> Target -> Automatically lock on target when initiating auto-attack.

[MiqobotKeymaster]

Training chocobos in stables is one of the functions planned in the future Scenario Engine updates.
You can find the list here:
Planned Functions

If you ask about active leveling via FATE Farming, then no, it is not supported at the moment.

Our community assigned a low priority to FATE features 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 Protection

[MiqobotKeymaster]

Yes, of course.
When your level is synced, your character loses access to all high-level abilities and traits.

[MiqobotKeymaster]

Yes, if you play Samurai at low level, please disable positionals in Assist Mode settings.

[MiqobotKeymaster]

• On Samurai, there are no positionals until level 52, therefore True North is not used before this level.
• On Ninja, True North is used to ensure the correct positional of Trick Attack. It will be used only when Trick Attack is ready but your character is not at a target’s rear.
• On Monk, True North is used on cooldown as long as Riddle of Earth is not active.
• On Dragoon, True North is used on cooldown. There is a minor issue wherein True North is used before level 50 when it’s not necessary (similar to Samurai). It will be addressed in the next release.

In addition, Miqobot always tries to keep one charge of True North ready, in case you have need to trigger it manually due to the ongoing mechanics.

For Assist Mode feedback and similar questions, please use the main feedback thread:
Shadowbringers – Issues & Feedback

[MiqobotKeymaster]

Yes, this feature is already planned.
You can find it among the planned functions for Scenario Engine.

During the recent voting period our community has voted in favor of Quality-of-Life updates, so they will be implemented first:
Voting (June 2 – June 9, 2021)

Thank you for your request!

[MiqobotKeymaster]

Thank you for providing the requested information.
In this case, please try removing the Shift modifier from Mudra keybinds.

The problem is caused by the fact that Miqobot can not send a composite keybind instantly, because the game requires a delay for it to be registered. On average, it takes about 250-500 milliseconds more to send a Shift shortcut versus a single key shortcut. And since the Mudra cooldown is only 0.5 seconds, the most likely outcome is that the cooldown animation completes before Miqobot has a chance to notice it.
Thus, for Miqobot it looks like the Mudra action wasn’t triggered and she tries to activate it again.

You can find additional information about this problem in our Keybinds and Icons Recognition guide.

This is why we recommend to have all the most important skills to be mapped to the shortest shortcut possible.

[MiqobotKeymaster]

There are multiple factors that may cause this problem.
Since Miqobot doesn’t use code injections, she has a limited number of tools to track the correct Mudra sequence. These factors were always present and the GCD queueing algorithm has of course introduced additional restrictions.

First of all, would you please clarify, what keybinds have you assigned to each of the Mudra actions?

[MiqobotKeymaster]

According to our logging system, you attempt to run Miqobot in trial mode.
We are very sorry, but unfortunately our trial system is not available.

It was abused many times and some users have tried creating exploits to use Miqobot for free. Therefore fixing the trial system is a low priority task at the moment.
We sincerely apologize for inconvenience.

[MiqobotKeymaster]

A setting to disable AoE rotations is planned, but it’s not a trivial one.
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 3

This 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.

[MiqobotKeymaster]

Yes, there is.
Here is the list of settings that must be disabled in order to deactivate 3D Radar overlay completely:

1. 3D Radar tab -> Show -> Nothing.
2. 3D Radar tab -> Show FATEs -> List / World.
3. 3D Radar tab -> Show Gathering -> Out of reach.
4. Navigation tab -> Show on radar.
5. Gold Saucer tab -> Racing -> Show -> Rails / Mid-rail / Progress / Waypoints.
6. Combat tab -> 3D Radar -> Show arena.
7. Combat tab -> Assist -> Pause -> Show pause status.

You can verify that 3D Radar is deactivated by looking at the top left corner of the game.

• If you see a transparent box, it means 3D Radar application is rendering the overlay window.
• If the top left corner is empty, it means 3D Radar application is deactivated.

[MiqobotKeymaster]

jponry wrote:

Is customization strictly “fonts/color scheme” and nothing else?

Yes, it is.

jponry wrote:

Would the ability to maximize Miqo’s window be part of the customization update, or an overhaul?

In order to resize or maximize a window, it must have easily resizable elements.
For example, you can already maximize the Gathering Rotations designer, because its UI elements were originally designed to be resizable. Main Miqobot window has only one easily resizable element – the message log, which is probably not what you wish to resize to begin with.

So if we start working on the ability to maximize Miqobot window, we need a different UI layout that was originally designed to be resizable.
Alternatively, we need a special algorithm of new space distribution as it was explained by @vixen in the post above.

[Author]

Posts