Stance conditional not working properly since 9.0.5
cgsub opened this issue · 3 comments
Stance conditionals seems to not be working properly.
In my case it happen with castsequence.
For instance this sequence below will actually cast in caster form (form 0):
/castsequence [form:4] reset=combat/target Starfire, Starfire, Starfire, Sunfire, Moonfire, Starfire, Starfire, Starfire
I tried with [stance:4] it didn't help.
I didn't have problem until recently with this, I wonder if it came with 9.0.5
I also noticed issues with other gse macros not using castsequence.
You would need to google what was available based off stances in WoW's macro language
Ok this is going to sound confusing but in both cases you have a WoW issue not a GSE issue.
GSE doesn’t execute your macro or perform any actions in any way. All it does is prepare a macro that is passed to WoW to execute and interpret each click of the button.
Castsequence has been broken at the WoW level since 8.0.0 and Blizzard have no intention of fixing it any time soon. In its case it is not recommended to be used in any way shape or form. GSE can’t fix it as it’s not the one interpreting or executing the command. WoW is and will do whatever it chooses to do.
With your form/stance problem again it’s WoW not interpreting the command. All you can do is what you have tried of a different conditional. If that doesn’t work then you will need to look at executing the command in a different way.
TimothyLuke
… On 22 Mar 2021, at 3:16 am, cgsub ***@***.***> wrote:
Stance conditionals seems to not be working properly.
In my case it happen with castsequence.
For instance these sequence below will actually cast in caster form (form 0):
/castsequence [form:4] reset=combat/target Starfire, Starfire, Starfire, Sunfire, Moonfire, Starfire, Starfire, Starfire
I tried with [stance:4] it didn't help.
I didn't have problem until recently with this, I wonder if it came with 9.0.5
I also noticed issues with other gse macros not using castsequence.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.