Nothing to be done here for now, I think Grid 2.0 will use a different roster lib which will handle units without resorting to names but for now there's no solution, tell your hunter friends to stop jerking around and use "Rex" or "Groink" as a pet name like everybody else :)
Not sure if this is the right place, but it doesn't seem like the addon GridStatusMissingBuffs has it's own thread.
Since grid moved to LibBabble-Spell-3.0, GridStatusMissingBuffs no longer functions as it still calls Babble-Spell-2.2. Is there anyway we can get that addon updated? I'm sure it's a quick fix, I just don't know enough about .lua to do it myself. I was hoping it was as easy as pointing GridStatusMissingBuffs.lua (line 8) at LibBabble-Spell-3.0. It worked but failed at line 147 when it starts to call the buff descriptions.
again if there's a more appropriate thread for this, I'll repost there.
edit: of course after I post this i find a thread about the addon.
New issue I've found with recent update... For paladins, the range has reset itself to the range of Holy Shock (20 yards) instead of 40 yards.. manually changing it to 40 does nothing, as the next time you get into a raid it resets itself back to 20. This is an issue I've noticed that only paladins have.
I've noticed that the out-of-range setting changes for me too. I think it has to do with playing multiple characters. On my shaman I set the range to 40 yards. If I only use my shaman, then it stays set at 40 yards. However, when I logon to my rogue I notice that the range gets reset to 28 yards. This setting remain even when I return to my shaman.
It's not paladin-specific. Randomly on login Grid will fail to detect any non-default ranges, leaving me to choose between 10, 28, and 100 yards. Reloading the UI sometimes fixes the issue, sometimes not. This has happened on my shaman and druid, and on a friend's priest and hunter. The issue has only cropped up in the last few days, not sure exactly when, and as it isn't consistent it would be almost impossible for me to track it down to a specific revision.
I have no idea why the range iterator would not find the available range.
I have just committed a workaround so that the user requested range value is never reset if the corresponding range has not been found by the iterator.
Please be aware that this will have strange side effects if you keep sharing profiles between classes that do not have the same available ranges. It is still strongly advised not to use the same profile for this reason.
Hopefully this issue will be less of a problem once 2.4 hit live and every class has a 40 yard range check ability.
Not sure if this info will help track down the problem, but manually calling the range iterator in a /script command (don't recall the exact function name offhand) post-load doesn't generate any errors, but doesn't give me the 30yd and 40yd ranges that are normally available to me either. (Going to update to your workaround here shortly.)
As I recall ExtraBar was used to show incoming heals so it would stack on the health bar, which would explain what you're seeing? What I do for Lifebloom timer is to enable the second text line and assign the Lifebloom duration status to that so I see a numeric countdown of the time.
Doxxx, thank you, thank you, thank you! What a simple -- and elegant -- solution to a problem I've had forever. All those other countdown timers were way up there and I am so focused on Grid that I couldn't take in all the info from the counters. Now it's right in the grid! Tried it out in raid last night. Was so much more efficient at keeping the hots up! Thanks again.
There is an option for party frame in Pitbull to show 5-man raid as a party. It's really usefull for arena.
Is there any chance to get something like this in Grid, so I can have Grid only as a raid frame, but not in arena.
I would strongly object to any and all annoying flash effects in Grid. Just set "crucial debuffs" to display as the center icon (i.e. if you're a shaman, set the center icon indicator to show poison and disease debuffs). If a big icon filling the frame isn't enough to make you notice it, you should probably be paying more attention to your raid frames.
I would strongly object to any and all annoying flash effects in Grid.
I don't think he was saying make it the standard for all Grid users. I think he was saying add "flashing" as an indicator option... like color, size, etc.
I think Grid really shines for healers, but I know non-healers (like raid leaders, etc.) install it because it gives them so much information about the raid at a glance. These non-healers may not be focused so intently on their Grid frame as the healers, and may sometimes miss important debuff information, etc.
I have just the opposite problem. As a healer, I'm sometimes so focused on my Grid frame, that I miss things going on outside of it -- like error notifications for LoS, etc.