So I know the minimum range was removed for charge…when I read this change, I thought it was a general change but turns out it was specific to only Arms/Fury specs…not prot. As a result, charge macros doesn’t work for prot anymore…(-_-)
Simple macro I like to use…but because Charge has two different spell ID’s now, this macro doesn’t work in prot spec…any thoughts how to adjust this? Can a spell ID number be used for macros?
#showtooltip
/cast [nomod] Charge
/cast [mod:alt, @cursor] Heroic Leap
Yes.
What would you like it to do?
You can use stance conditionals, for example:
/cast [stance:2/3] Charge; Heroic Leap
There is also a UI and Macro section of the forums, in case you’re interested.
The stance doesn’t seem to change anything. The ability is still the same in each stance while in Protection “spec”.
If I can just use the spell ID like you said, that will fix my issue. If not, I can redirect this question to the other forum.
The stance conditional works by using stance 1, 2, 3, etc. where the stances are in order of how they appear on your stance bar. You may wish to play with that, if you want to use those conditionals. However, that was intended as just an example.
Then Defensive Stance is probably not the stance you’re in when you want it to change. This isn’t about “spec” it’s about “stance.”
Then use the spell id?
AFAIK, the way that works is as a conditional for known, which might be suitable if you know a spell in one spec and not another, as I gather may be what you’re getting at?
`/cast [known:12345] SomeKnownSpell; OtherwiseOtherSpell
Seems like a good idea.
Charge isn’t locked to stances anymore.
I just tested your macro on my level 20 prot warrior, charged a chicken in Orgrimmar. It worked fine.
Edit: Just re-specced to fury, works in that spec too.
Yeah, it’s working fine for me now as well…I didn’t change anything haha. I was switching between specs and relogged a few times. Whatever the issue was, glad it’s resolved now.
1 Like