Welcome to the Achaea Forums! Please be sure to read the Forum Rules
I've been delving into Magi combat over the past few weeks and have run into some problems with the way that Magi class interacts with the queueing system. Ideally the purpose of the queueing system is to reduce response time and potentially minimize the amount of commands entered to execute abilities.
From what I've experienced, there seem to be some idiosyncrasies when trying to queue both staffstrike and golem attacks together. Sometimes they go off together without a problem. Other times they will ping pong back and forth between eq and balance when the intention is for them to be executed together. (There may be a way to account for this using GMCP to track my eq and balance and only enter one attack or the other depending on which balance state i'm in, but it seems like a system level issue)
I've been experimenting with the different configurations of:
Queueing the balance attack (staffstrike) with EQBAL, Golem attacks with EQBAL
I have had the most success with this option, but often encounters scenarios where you get ping-ponging dependent on when you use your attack. (Most successful when used after regaining equilibrium).
Queueing the balance attack (staffstrike) with EQBAL, and leaving out designation for queueing (only works with auto queueing CONFIG turned on)
Similar to the above, as i've been told that the system tries to apply the attack to the queue that's most appropriate for it.
Queueing the balance attack (staffstrike) with EQBAL, Golem attacks with EQ
Results in consistent bouncing back and forth between staffstrikes and golem attacks. Basically just doesn't work.
Am I doing something fundamentally wrong that i've overlooked?
Despite what I've been told after having bugged this, is this functioning as intended? (also have noticed some similar issues when queueing combos as a sentinel)
If the above answer to 2 is yes, can we please have some sort of combo ability added to Artificing that allows for some easing of this functionality? It feels unnecessarily complicated and makes the class very difficult to code for.