Macro problem, diadnosis gleefully useless #1653
Replies: 3 comments
-
I would suggest that with the TWW changes You are using Spell blocks for a spell you not longer know. This can be caused by Changing spec or talents. By changing this back to a macro block you will resolve your issue. |
Beta Was this translation helpful? Give feedback.
-
When you create a sequence, GSE creates a SecureActionTemplateButton which is what you click. SATB from wow has some rules one of which is everything has to exist and be known all the time. As soon as you ask SABT to do something you don’t know it (not GSE) throws this error. The only this it doesn’t checks at creation is macro commands. These aren’t checked at all and just sent to WoW which checks at execution and rejects any that are invalid at the time. |
Beta Was this translation helpful? Give feedback.
-
Thanks mate! here's the old china now, DW fury and all that lot. Quite.
8.2FURYSTTalents: {} This macro contains 1 macro template. This Sequence was exported from GSE 3.2.14-d. |
Beta Was this translation helpful? Give feedback.
-
This drives me nuts I cannot find the issue and it's persistent. I've used this sequence for many years.
Beta Was this translation helpful? Give feedback.
All reactions