Hey mages, I tried doing a macro so that I could cast Blast Wave but have it cast Flamestrike when Blast Wave is on cooldown.
I thought a simple macro like this would work:
#showtooltip
/cast Blast Wave
/cast Flamestrike
It seems to only cast Flamestrike. I'm no Macro expert, am I doing something wrong? I'm thinking perhaps Blizz will not let us put more than a spell in a macro to avoid over-powered macros?
Any thoughts?
You aren't following scripting effects. You simply cannot cast two spells at once, it breaks the GCD rules.
Try this:
#showtooltip
/cast [nomod] Blast Wave
/cast [mod:shift] Flamestrike
This way you have one keybinding that you have both abilities on, you simply need to hit shift to get to the other one. ( You can swap out shift for alt, or ctrl )
That will work very well, thank you Alcarran.
Anytime :)
To be perfectly honest I got that macro type from Brang the Night Elf hunter famous on youtube.
#showtooltip
/castsequence Blast Wave, Flamestrike, Flamestrike, Flamestrike, Flamestrike, Flamestrike, Flamestrike, Flamestrike, Flamestrike, Flamestrike
Just adjust the number of flamestrikes until it lines up with your blast wave cooldown.
You can't use if:then, or if:else statements so you can't really do what you're trying to do. For your macro to work it would have to be something like if blast wave off cd /cast blast wave else /cast flamestrike. The WoW macros stop issuing commands as soon as the first spell which causes a gcd is cast, or as soon as a spell command fails. Keep in mind that the structure you put together for your macro WILL work for any spells/abilities which are instant and do not consume a gcd.
You can either do a modifier like Alcarran posted, or you can do the following:
#showtooltip
/castsequence reset=30 blast wave, flamestrike;
The above macro will cast blast wave the first time you press it, and flamestrike the second time you press it. If you don't cast flamestrike within 30 seconds (blast wave's cd), then it resets and will cast blast wave again, even if you haven't casted flamestrike.
No comments:
Post a Comment