GridStatusShield
This addon provides a grid status which provides the remaining amount of your shields on a unit.
Ok, 4.0 is there and Blizzard heard my prayers and added absorb tracking support. Therefore now also shields of other players and classes should be displayed correctly (at least when I'm done with it :-). And they should be very accurate now.
Currently I'm still experimenting whats the best way to use these therefore GridStatusShield currently provides two different methods to use. The first is based on the combat log and the other one on internal events and the tooltip of unit buffs. You can change the method in the settings of GridStatusShield. So if you encounter any problems try changing the tracking method (and let me know about the problems).
Some pros and cons of the two methods
Combat log based:
- PRO: independent from clients language
- PRO: pretty fast
- CON: not very reliable (out of range units, broken log, lag, missing events for certain shields, multiple shields of the same kind (divine aegis))
Buff-tooltip based:
- PRO: reliable concerning lag, range, and multiple shields of the same kind
- CON: very slow at the moment because it parses every buff tooltip every time something changes (can be improved a lot)
- CON: parsing needs to be done for every language separately (If you can help me with your language there it would be awesome!)
A FAQ (just to amuse me ... and maybe it helps you :-))
Q: I don't see any shield values!
A: Maybe your language isn't supported yet, try changing to combat log based shield tracking.
Q: I don't see any value for Power word: Barrier!
A: This shield does not create any combat log messages, try disabling combat log based shield tracking.
Q: This ** addon slows my PC extremely down in fights!!!
A: The current default shield tracking method is very slow, try changing to combat log based tracking, that should be much faster.
Q: The shield values aren't displayed correctly if there is more than one Divine Aegis on a unit (or any other shield which can occur multiple times on the same unit).
A: Yeah, those are hard to keep a part using the combat log. Try disabling combat log based shield tracking.
Q: "Try this! No, try that! Then try this! Nom no! Try that method!"... you are messing with us right?
A: Maybe... just wanted to show the pros and cons of the two methods in another way ;-)
A blue poster said that if multiple Valanyrs are present in a raid, they all contribute to the same bubble.
Thanks again !
If you want to know the time elft of a shield (or any buff) you can just add a new "aura" status for it with grid and display it as icon or whatever.
My bad, there's 3 things:
- Grace, I like the way your addon does it right now
- PW:Shield, I like the way it's done right now, but would like the option to actually NOT display the shield left, since I usually cannot refresh it anyway due to the debuff. Grid provides a way to know who has a shield up, and who has the weakend soul debuff, that's enough for me. Currently, sheilds dut to PW:S and due to Aegis are mixed. I'd like them separated.
- Divine Aegis, which is what I was calling "shield", and which is what I'd like to de a bit differently, if at all possible:
+ should be listed apart from PW:S: I want to know when DA as fallen off the MT, so that I can stack it again. With PW:S mixed with DA, I don't really know.
+ In the same format you're using for Grace: it also has a duration, and stacks. Right now we see only the stacks (mixed with PW:S) and not the duration.
Am i making any sense know, as to the what and why ? (I'll let you figure out the how ^^)
And with showing only the Aegis: Theoretically this whouldn't be a problem to add, but practically currently GSShield assumes that the shield with the lowest duration is used up first. This is wrong since 3.1 as I've found out a few days ago. It seems like now the shield with the lowest amount remaining is used up. This means most times aegis will be used up before PW:Shield (because it doesn't stack that often above 6k) so how GSShield currently works is still correct in most cases (aegis duration is shorter than PW:Shield).
But in your case where you want to explicitly stack it as high at possible in most times it whould give you correct numbers.
So before I can add your request I have to correct the model how the shields are used up, which can take a time because it is far more complex then it was before 3.1 and needs a lot of recoding.
edit: "But in your case where you want to explicitly stack it as high at possible in most times it WHOULDN'T give you correct numbers. "
I'm having problems with the Shield part, though.
The Shield text does not go over 1.3K when I spam-heal myself. This seems wrong as Divine Aegis is supposed to stack up to 10k.
I tried grouping a colleague, made the group a Raid group (even though we were only 2 in it), and the Shield text only idicated 0 on him, even though I was critting plenty.
I've tried adjusting the Aegis detection tolerance down to 0.1 or up to 1 or 2. I do get a non-0 figure at 2, but then that figure climbs way above 10k which sould be the limit.
It's going to be hard adjusting that while raiding. Any recommendations on what the Shield Lag should be ? What do the other sliders mean ?
Thanks again for your work !
- this is veeeery strange. Which language (of WoW) do you use?
That feature is kinda working, but it's very imprecise and laggy, I think. IDuring my raid yesterday, I did see the DA stack go up and down on my MT, but with a faire bit of lag. Probably due to Blizzard not supplying the info needed to do better to start with.
I can leave with just a rough indication.
Overheal crits counted for Aegis since ever, I don't know why blizzard said in the patch notes of 3.1 that they do now.