I know about that, but I may have used the wrong term to describe what I meant. In the talent page you can save different presets (I called them loadout), basically if you want an optimized AoE spec for unholy, and a full single target spec for Unholy, you can save both. I was asking if the talent switch macro could go directly to one of those specs, that way it would do one casting of talent switch instead of 2 (assuming the one you land on with basic spec switch is not the right one you want at that moment).
They apparently changed this functionās scope. I did some searching on an API reference and found that itās not global anymore. They associated it with the C_SpecializationInfo object. So I prepended that to the call and got it to work, though I just removed all the boolean stuff. My call is
/run C_SpecializationInfo.SetSpecialization(2) for Enahancement, and /run C_SpecializationInfo.SetSpecialization(3) for Resto. I didnāt notice the /spn command. Iāll probably switch to that since itās less bytes.
1 Like
Blizzards fault. I think they use some ambiguous terminology, now you mention it. Anyway, since those names could potentially be the same, I doubt that would work. Itāll just put you into your most recently used talent loadout for that specialization.
Yeah thatās what I would expect.
Thatās really clean and fast. Nice job finding the changes they made.
I appreciate the post, and that you found a working fix. Iām wondering if in your research youāre looking around you found another way to do it.
I actually like the direction that I though they may be going, adding console support with the /spn instead of using lower level functions.
I feel like itās way more user friendly and less intimidating for users, especially newer ones.
Iām interested in abstracting the spec name, so that I donāt need to create multiple macros for every single class.
I was hoping this would actually support dynamically updating the macro, so that you could, for example, just sayā¦
#showtooltip
/spn 1
the macro and associated tool tip could then update regardless with what spec you use it on.
Iād have four macros and use at least two on most characters.
ā¦ itās even marginally more efficientā¦ marginallyā¦ lol
ā¦ because it allows people to store fewer macros overall, instead of character by character, while still allowing char by char macros with named parameters like they have now with Protection, Retribution, etcā¦
I currently use this on single buttons alone, and have in the past use this with opieā¦
I think given their new macro system to allow for trays and flyouts, Iāll just stick to that, if I can get this sortedā¦
If anyone finds anything, Iād appreciate you posting.