I’m not at home to try it, but I doubt this would actually fix the problem. The problem stems from different specs sharing the same spellid for an ability, but with talents that can modify that ability.
A similar issue happened in s1 with evokers and empowers spells due to font of magic. If you were devastation with that talent, swapping to preservation would lock your macro for spiritbloom unless you had font of magic for preservation as well. The macro was still linked to the 4 rank spiritbloom, so if you didn’t have font of magic you would be unable to macro spiritbloom. This was only fixed when they changed devastation’s font of magic to be different from preservation’s, so that it no longer interacted with preservation’s empowers.
In case anyone new comes to this thread from DECEMBER 2022, no they haven’t fixed it yet. Yes, it’s still completely broken. I still refuse to believe this would be that difficult to fix but I’m not game dev, so what do I know?
Seems tempremental, open world it will be available 50% of the time, but as soon as you queue into an instance, it is greyed out and you get the Spell Not Learned error
Fix this please blizzard. So taking precise sigils off my havoc, and turning it on my vegeance spec allowed me to make macros again for vengeance? but precise sigils HAS to be on one spec or the other to make macros for me…
WELP, little bit surprised to see this is going on 3 years and still not fixed. I believe the cause is known, and is due to another spec having precise sigils selected, which then buggs every other spec. A fix would be real nice, its limiting my talent choices…across all my specs. Plz/ty blizz.
I had this bug happen 4 times yesterday which is unprecedented. I was swapping between Havoc and Vengeance demon hunter specs. Each time required a relog to fix it. I could swap back to Havoc and Sigil of Flame would be usable but going to vengeance it showed Spell Not Learned when I used my usual macros of years old. I could drag the ability from the spell book to use it annd it worked, and confirmed that the spell IDs are exactly the same, so the issue is only when they’re macro’d.
You can literally replicate this issue 100% of the time on multiple classes by swapping specs with the proper talent setup and then entering an instance. The spellids are also not the same. While the tooltip may update to reflect the updated talent, the macro cast does not and will always be attempting to cast the old spellid that is no longer learned. It’s partially a drawback of different ability overrides sharing the same name with different spellids and the macro system being unable to cast by spellid.