Bug: Macro [spec:2] condition broken

WoW Classic Mists of Pandaria Classic Discussion
1

I just finished my macros yesterday for a couple of classes and today I logged in after the restart and a lot of my Macros are broken.

Examples - Druid (Spec: 1 is Bear, Spec: 2 is Cat):

#showtooltip
/use [spec:1,noform:1] Bear Form;[spec:2,noform:3] Cat Form
/use [spec:1] Enrage; Tiger's Fury
/use [combat] 10

If I am in Spec 1 (Bear) I expect to go into Bear and cast Enrage and if I am in Spec 2 (Cat) and cast Tiger’s Fury

Spec 1 is working as expected, Spec 2 is giving me Bear Form and if I am in Bear it shows a Questionmark (because Enrage is unknown)

Another Example - Hunter (Spec: 1 is SV, Spec: 2 is BM)

#showtooltip
/use [noform:1] !Aspect of the Hawk
/use [spec:1,mod] Black Arrow; [spec:1] Explosive Shot
/use [spec:2,mod] Focus Fire; [spec:2] Kill Command
/startattack

I expect in SV Black Arrow and Explosive Shot to be active and otherwise Focus Fire and Kill Command.

Neither is the case, in both specs (1 & 2) only [spec:1] is working and the else condition ; is not working at all

It looks like the [spec:1] is always true and [spec:2] always false, this might be internally due to changes / removable of the GetSpecialization() function

1 Like
2

Same issue, completely broke my UI for my 2nd spec making it unplayable, also wasnt fixed after maintenance today

3

I have the exact same issue using “[spec:1] Kill Command; [spec:2] Explosive Shot” and similar for Black Arrow and Focus Fire. Worked fine last lockout, doesn’t work after logging in today.

4

Still a broken thing, this makes nearly all my chars unplayable in mostly second spec and some in first spec even

5

Any update from Blizz if/When the [Spec:n] conditional will be fixed?

6

none so far as I’ve heard

7

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.