Get an Epic Experience with Premium


Unit Frames Login to Add Favorites
  • World of Warcraft
  • 410 Monthly Downloads
  • Supports: 6.0.3
  • 163,621 Total Downloads
  • Updated 11/10/2014
  • Created 10/22/2008
  • 156 Favorites
  • Project Site
  • Comments
  • Release Type: Release
  • License: GNU General Public License version 3 (GPLv3)
  • Newest File: v1.7-toc6.0

About 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 ;-)

r76 | julith | 2014-11-10 09:23:34 +0000 (Mon, 10 Nov 2014) | 1 line
Changed paths:
   A /tags/v1.7-toc6.0 (from /trunk:75)

Tagging as v1.7-toc6.0
r75 | julith | 2014-11-10 09:19:57 +0000 (Mon, 10 Nov 2014) | 1 line
Changed paths:
   M /trunk/GridStatusShield.toc

GridStatusShield: updated toc


First Previous Page 2 of 7 Next Last
  • #82

    No update makes me sad. :-(

  • #83

    Why? Is it broken or are you missing any features?

    If you want I can update it for the current version of WoW so it isn't marked as outdated anymore in the addon list but that is a pure cosmetic change. Well, maybe not completely cosmetic but pretty much :-)

  • #76
    Maybe this will help

    1x GridStatusShield-1.23\GridStatusShield.lua:208: attempt to index field 'unitShieldLeft' (a nil value)
    Grid-\GridCore.lua:164: in function `ResetModules'
    Grid-\GridCore.lua:107: in function `Reset'
    Grid-\GridStatus.lua:406: in function `Reset'
    Grid-\GridCore.lua:321: in function `ResetModules'
    Grid-\GridCore.lua:259: in function
    : in function `?'
    CallbackHandler-1.0-6 (Ace3):147: in function

    : ?
    :"safecall Dispatcher[3]":13: in function `?'
    CallbackHandler-1.0-6 (Ace3):92: in function `Fire'
    AceDB-3.0-22 (Analyst):462: in function `SetProfile'
    : ?

    (tail call): ?:
    AceConfigDialog-3.0-54:793: in function
    (tail call): ?:
    : ?

    (tail call): ?:
    AceGUI-3.0-33 (Ace3):314: in function `Fire'
    Ace3-Release-r1032\AceGUI-3.0\widgets\AceGUIWidget-EditBox.lua:74: in function
  • #77
    Hmm, strange error, when does it occur? What happens if you disable everything except grid and gridstatusshield? What happens if you backup and remove your "wtf" folder?
  • #80
    Last try, i enabled all addons i have with wiped WTF folder. It doesn't work. Wanna send u the list of my addons? is gonna help?
  • #81
    yes please. You can also narrow the addon down by deactivating one half of the addons and see if it works. if so its one of the deactivated half if not its one of the activated ones. THen you can repeat that procedure with these addons. And so on until you have only the problematic addon left.
  • #79
    I backuped wtf folder and removed it. then i disabled everything except these 2. it works fine.
  • #78
    Just checked as u told. Disabled everything except grid and gsshield. It didn't work. Still the same. The funny thing is that i don't see any lua error or something. Or propably I m missing it somehow... :
  • #75
    Can't understand this add on :( 2 days before it worked fine (i logged wow after some time installing the new release for 1st time) but now it doesn't show me the amount of shields. What i need to provide so u can help me with this?
  • #74
    HOORAY! I was about to delete Grid altogether, but now this is back!
  • #73
    Is it correct that shields are no longer displayed since 4.1 Used to work fine
  • #72
    hi, thanks for your addon.

    for french langage, the info are :
    name : "Mot de pouvoir : Bouclier"
    tooltip of the buff : "Absorbe xxxx points de dégâts."
    (i do not know if accent are important...)

    contact me if you want to make tests.
  • #70
    Patch 4.0.1.

    When using the combat log for detecting it works fine wit no problems. Otherwise it shows weird numbers even if there's no shield on etc..

    So the "fast and unreliable" works perfectly whilst the "slow and reliable" has bugs or something in it.

    Other than that, works great:) ty
  • #71
    Which client language do you use? Currently the not-combat log parsing is only tested for the german (my) client. For the other languages I need the tooltip lines of the shields auras (should be something along "Absorbs xxx damage" or "Absorbs xxx shadow damage". For the english client I have the tooltips from wowhead but couldn't test if parsing them works correctly.
    I push a beta where the english ones might work.
  • #66
    Nothing will show up for me =\ I enabled the shield status and changed the colors and everything and when I shield nothing shows up on grid. I am a priest too...
  • To post a comment, please login or register a new account.
Login to Curse

Don't have an account? Create One.

Get an epic experience with Curse Premium
  • Faster addon downloads
  • Premium-Only Beta Giveaways
  • Ad-Free Curse experience
  • Premium Curse Client
  • and many More Features
  • Learn More »

Darkest Dungeon Wiki Editing Contest