I know there are issues with castsequences, and one of the large reasons is if an item is similar to the palceholder the game will try and use that item and it can mess things up. I was doing some googling and forum diving to look more into it and i found this thread, specifically the last post in it.

https://us.forums.blizzard.com/en/wow/t/cant-for-the-life-of-me-figure-this-macro-out/428553/7

"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.

Anyway, now that the problem has been clarified, here’s how to 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."

This is the first i've heard of appending () to force the game to look for a spell, but it makes sense. Just posting it here for awareness and as a possible check. You know more about the interactions behind the macros than i do so i thought it atleast might be interesting. But i also did not want to spread misinformation if it is false.

sorry for the long letter here, i almost sent this over discord, but i thought i remembered you saying you preferred github for this sort of thing.

Doesnt work putting () at the end means execute the Function and unless Spellname() returns a value you will just break GSE.

Shoulda figured it couldn't be that easy lol. But that is why i was asking.