Main Issue
E.G.
#show Glacial Spike
/castsequence reset=2.5 ice floes, Glacial Spike
/cast glacial spike
When using this macro on scroll wheel up or down, it uses 2 charges before Glacial Spike casts. I believe this effects other spells without global cooldowns. According to the script sequence it should use one ice flow, glacial spike, and then reset in 2.5 secs. Or use Glacial spike if there are no ice flow charges.
While I can bind it another key, I would prefer to have it on the scroll wheel. Additionally, I believe this is a bug and not working the way it was intended to.
Sub Issue
The cast sequence above was meant to be a workaround to another macro issue. So it is more so frustrating that the workaround isn’t working as it should.
Below was the original issue with making the ice floes macro. According other forums, quiet a few people have reported on the way that the server registers ice flow charges, which causes macros to not work properly.
/cast glacial spike
/cast ice floes
//if first spell unavailable, uses the second. //uses ice floes even if prior spell is on cd
//includes global cds (if pressed before GCD is up)
//need option to not use the second spell before the first (intentional?)
//need to stand still to work since it registers movement, then spell
Since castsequence is allowed, there should be a command that stops the second spell if the first one is not available. (or would that make it too much of a conditional macro which breaks terms? intended? (This shouldn’t apply to the main issue)
//using macro that casts ice floes first
e.g
/cast ice floes
/cast Glacial Spike
rather than vise versa,
if cast while moving, causes you to use ice floes a second time. You can use macro while moving the second time,
but it will consume the ice floes charge at the same time. The second click is the initial intent.
It happens only the second time because in the second key press, the move condition is removed.
I’m not entirely sure if the Sub Issue section is working as intended. Not sure if it is a bug or not, but the main issue almost definitely is.
Thanks for reading.