Hey all, I logged on today for the first time since maintenance and noticed a macro I’ve been using for ages is no longer working. It’s just a simple @player macro for myself.
#showtooltip
/cast [@player] Surging Totem
That’s it. It just casts surging totem at my feet and moves it to me when I hit it again. It tells me that the spell is not learned even though I can cast the totem without the macro and use the macro to move the totem, it just won’t make the initial drop anymore. Was there a change to @player macros that I missed?
That generally indicates that the macro is trying to cast the wrong version of the spell. That’s been happening a lot since DF. Does logging out and back in fix things?
Nope. It doesn’t even show the icon anymore. I didn’t change anything, it was by pure chance I noticed it. I did an entire rss without it because I didn’t realize my macro was broken. I just thought I was getting some weird lag.
deep sigh
Try this:
#showtooltip
/cast [known : 1221348][@player] Surging Totem(2);[known: 444995][@player] Surging Totem
I know, I know. But for some reason the ability to summon the totem and the ability to move the totem are broken out into two different spells, both with the same name, and the movement one overrides the other in your spellbook when it’s active. I’m only taking a guess at the name of the movement spell based on how collisions like that are handled elsewhere in the UI, but God knows they’re not consistent so the only way to really know is to have a shaman and shift-click both names into the macro yourself.
[Edit: forgot an @player!]
[this, and this]
[this] [or this]
; else this
#showtooltip
/cast [known:1221348,@player] Surging Totem(2); [known:444995,@player] Surging Totem