if you make a castsequence macro on a unholy dk lets say " /castsequence unholy frenzy, apolacypse " the macro will always get stuck on apocalypse and button presses wont work on it. It works with /cast apocalypse but not castsequence the macro will get stuck.
3 Likes
You misspelled âapocalypseâ in your first macro. Did you copy that from your macro in the game or just mistype it when posting here?
I reported this bug today. I had the same issue for more than a week now. I had to /reload to get it to work. The weird thing is it works sometimes but seldom. In an old forum, it was mentioned the issue was coming from a duplicate tooltip name for the spell. There was a legendary item that is also called Apocalypse which is causing the issue. The fix would be to rename the spell but not sure if Blizz will give value on looking into this.
1 Like
For single spells, â/useâ supposedly looks for items first while â/castâ looks for spells first. But for â/castsequenceâ, the game always looks for items first (which makes very little sense, IMO).
The same problem happens with âHealing Stream Totemâ, which is both a shaman spell and a follower upgrade item. If you donât have the item, the /castsequence macros work, but as soon as you get one of those items, they stop working and the game opens the follower panel (often mid-combat) instead. Great playtesting, eh? Or maybe I shouldnât blame playtesters; Iâve worked as a tester for a major publisher and the studio developing the game basically ignored our reports because (their words) âif we fix something we might break something else, so we donât bother unless it crashesâ. They had like 5 coders playing solitaire all day, so yeah⊠
Anyway, now that the problem has been clarified, hereâs how to solve (or at least work around) it: 
In the /castsequence, simply add () (open parentheses and close parentheses) right after the name of the spell. So âApocalypseâ becomes âApocalypse()â and âHealing Stream Totemâ becomes âHealing Stream Totem()â. That will force the game to ignore the item and cast the actual spell.
34 Likes
Funny how this is still a problem today⊠Shouldnât this be fixed?
1 Like
How is this still an issue? It still doesnât work. What the heck?!
edit: OHHHH I found a work around that uses less text use !Apocalypse No idea why it works, but it does.
1 Like
This did the trick for me (for anyone searching for the fix over the next five years).
I canât figure out how to intentionally trigger the glitch, but I just have to reload my UI and the problem goes away. So typically Iâll /rl when I enter a raid or key just to be safe when I may be in Unholy spec. :3