This site works best with JavaScript enabled. Please enable JavaScript to get the best experience from this site.
What steps will reproduce the problem?1. Attempt to cast Earthshield on someone other than yourself. It will not track it, or the number of charges remaining...and will insist that you recast it on yourself.
What is the expected output? What do you see instead?Previous to WoW 3.2, it would track the current ES'd target and charges remaining unless target was switched in combat. Now it only tracks self.
What version of the product are you using?Current ZOMGBuffs-3.2_Release__5_.zip
Do you have an error log of what happened?...It doesn't produce a LUA error for me...If there is something else that would be of help, I'll try.
Please provide any additional information below. I've tried deleteing the associated Zomg WTF files for this character, no luck. I've had to disable Earthshield tracking entirely.
Don't have access to a shaman of sufficient level atm, but I'll test the code out with Pala and Sacred Shied (identicle code).
Since you mentioned it being identical code...I tried it on my end and Sacred Shield replicated the same problem I had with ES. Fine on self targets, not tracked on other party / raid members.
Well, this is working perfectly for my paladin. Correctly selects targets and everything. Do you maybe have some other tracking mod installed for these ?
I have other mods, but nothing that should be interefereing...
I'll describe what I'm trying to do and what happens again and the additional testing I tried to do.
I join a party or raid. Out of combat I cast Earth Shield on myself to start the tracker. It lists 8 charges and the time limit. I now cast Earth shield on someone else...it lists 0 charges plays the attention sound, and refuses to adjust to the new target whomever it may be....unless its recast on self. (*then it works fine untill I try to use it on someone else)
(*What I want it to tell me is the charges of earth shield on the current target its on...and if out of combat adjust to that target so that if I click the button it'll recast it on them. It used to do this as long as it was out of combat...it combat it would track charges but not adjust to a different target...this was fine as I assumed it was part of the combat UI limitations.
I have repeated the test above under the following conditions:
All mods loaded: Fails to adjust
Only Zomgbuffs and Zomg Raid buffer loaded: Fails to adjust
Removal of WTF folder so that wow creates a new one from scratch: Fails to adjust
Anything you can think of left I could try?
PS: Running the current release version from a day or so ago
And yes, that's what it should be doing. And the few people i've asked recently they say it's fine. Not sure what to suggest. I've been looking over the code, and I can't see anything up with it.
Zeksie...you're gonna love this one.
I tracked the problem down. It's hillarious.
The culprit is a macro. And its not even obvious.
Basically a few weeks ago when 3.2 hit I did a totem consolidation for my UI. I combined a few totems into share keybindings. In this particular case I setup a conditional mouseover macro to share EarthShield and Grounding Totem. Like so:
#showtooltip /cast [target=mouseover,exists,nodead,helpful] Earth Shield; /cast Grounding Totem
Basically on a valid mouseover for a non-dead existing target that qualifies for helpful buffs...Cast earthshield. Otherwise cast Grounding Totem.
The 2nd line (/cast Grounding Totem) evidently confuses the hell outta the Buff tracker for some reason. If I remove the 2nd line...buff tracker correctly re-assigns the Earthshield cast to the mouse over target. If however the 2nd line exists...Buff tracker does not recognize a valid Earthshield cast...Holds the previous tracked target, and assumes you lost the buff for some reason and yells for it to be re-applied. (Previous to 3.2 ES was on a mouseover macro by itself)
I'm perfectly fine modifying my macro for the time being...thought you'd like to hear. Could you lemme know if its anything you "could" fix eventually or more of a bug on Blizzards side of the house.
Tolken
I'll try this myself and see what's going on internally. Thanks.
To post a comment, please login or register a new account.