[MiqobotKeymaster]

This issue usually indicates that you haven’t removed keybind conflicts from chat actions.
You can find instructions on how to avoid this problem in the [Beta] Combat thread.

Miqobot wrote:

Important Note!
Please remove any keybinds from “Reply” and “Switch Chat” actions.

If you use the common WASD style for navigation, there’s a very high chance that a keybind collision will occur if Miqobot sends key input at the same time.
For example, if you assign Alt+1 – Alt+= to a hotbar Miqobot uses at the moment and press S at the same time, the resulting keybind will become Alt+S which by default triggers “Temporarily Switch Chat Mode to Say”. This will activate the chat mode in the middle of the fight and break your movement completely.
In order to avoid this problem, we recommend to fully clear the Keybind -> Chat tab.

(You can leave the first two actions intact: “Ready Chat Log” and “Ready Text Command”.
Assuming they contain no Ctrl / Alt / Shift modifiers.)

[MiqobotKeymaster]

In this case, you can simply remove Nocturnal Sect from the hotbar and Miqobot will have no choice but to use Diurnal.

[MiqobotKeymaster]

The default choice has no effect when there are other healing classes in party.
Miqobot always tries to select a Sect that would complement the second healer:

• If the second healer is Scholar, Diurnal Sect is selected.
• If the second healer is White Mage, Nocturnal Sect is selected.
• If the second healer is Astrologian in Diurnal, Nocturnal Sect is selected.
• If the second healer is Astrologian in Nocturnal, Diurnal Sect is selected.

[MiqobotKeymaster]

All right, we will consider your suggestion.
Thank you for your request!

In the meantime, you can achieve a similar functionality by utilizing Scenario Engine with randomAfkFor() and sendIcon() functions.

[MiqobotKeymaster]

Level 80 Rotations are implemented.
Miqobot v1.3.43 – Patch Notes
Miqobot v1.3.44 – Patch Notes

[MiqobotKeymaster]

New scenario functions are implemented.
Miqobot v1.3.36 – Patch Notes
Miqobot v1.3.37 – Patch Notes
Miqobot v1.3.42 – Patch Notes
Miqobot v1.3.44 – Patch Notes

[MiqobotKeymaster]

Because Miqobot does not treat Assize as a healing ability. Its primary effect is 400 potency damage with an addition of 5% MP restoration. Since it has a cooldown of only 45 seconds, using it as soon as possible is a DPS gain.
If you wish to hold it for some reason, then yes, please move it to a different hotbar and instruct Miqobot to ignore it.

[MiqobotKeymaster]

Thank you for reporting.
However, we are not sure how we can help. Miqobot does not use code injections and does not alter the game client. Game crashes usually indicate problems in the game client itself and are not related to Miqobot.

[MiqobotKeymaster]

There is no need to download a new version for Patch 5.55.
Please restart your Miqobot and she will update automatically.

[MiqobotKeymaster]

Miqobot is fixed for Patch 5.55!

Please restart your Miqobot for the changes to take effect.
Thank you for your patience very much!

[MiqobotKeymaster]

As always, Miqobot is broken due to the arrival of Patch 5.55 and we are working to fix her as fast as possible.
The changes are minor and should take only a few hours.

[MiqobotKeymaster]

There is no priority.
Miqobot selects a random DPS among those who are not already designated as dance partners. If you don’t like this behavior, you can simply pause Assist Mode before entering an instance and select a dance partner manually.

[MiqobotKeymaster]

White Mage optimizations are minor. They are mostly related to reprioritizing certain spells and abilities which are usually more efficient than alternatives.

The list of adjustments includes Afflatus Solace priority slightly increased, Afflatus Misery having a second trigger condition, Temperance being used more often, better GCD queueing, and several others. Overall, you probably won’t notice any significant changes on White Mage. Most of the work in this update is related to Scholar and Astrologian.

[MiqobotKeymaster]

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

[MiqobotKeymaster]

Thank you for reporting.
Yes, we are aware of this issue. It happens not only with Gunbreaker, but also with Machinist and several other jobs. However, there is no way to predict whether the enemy will still be available after finishing the combo, therefore prioritizing low potency weaponskills may lead to losing DPS instead.

Rotations are currently optimized to achieve 90% performance and the cost of every additional improvement after this grows exponentially. This would be one of them.

[Author]

Posts