As melee I don't need to see every raid debuff though. So at this time there is no whitelist option I take it?
Ah ok. No, it is what it is right now. It could be more specific in the future though. Meanwhile you can edit the file and keep a copy of it then just paste your custom stuff if there is an update.
Are there any plans to get quickhealth 2.0 or something similar to work with grid2?
The difference between grid+quickhealth&shadowed uf's with quick health enabled vs grid2 is not neligible.
Are there any plans to get quickhealth 2.0 or something similar to work with grid2?
None that I'm aware of.
I suspect it would be somewhat easy to adapt an existing solution, if anyone is interested to try it. I'm not completely sold on the idea that using this kind of addon has a beneficial effect on raid performance (i.e. it's more a tool to enhance one's healmeter position than anything else).
I'm getting a white box indicator in the bottom center and can't figure out why. They show up regardless of what buffs I have/do not have it seems. They went away once when I manually deleted my saved variables, but then came back when I used "reset setup" and now seem to be sticking around even after a manual deletion again.
All right then, 337 beta is what you can revert to during the coming instability on the alpha branch as the layered preferences get checked in and sorted out.
Azethoth, I noticed you have SacredShield-mine hooked up to the side-left indicator. I'm a little surprised you didn't - as far as settings for paladins go - mirror the default druid config, showing SacredShield and BeaconOfLight on any the top indicators.
(At least, this is how it seemed to make sense to me, and when comparing it to the settings for Renew and PW:S for priests).
Just testing it on my priest/druid/paladin to see the differences now, however, and I'm noticing that for my druid, it shows numbers, and yet not for my priest. Is this something specific being done with certain spells? I noticed that abolish poison (on my druid) only shows a square dot indicator, rather than an option to show a countdown. Same on my pally - before I updated to the newer alpha builds, it was letting me 'show numbers' on other classes.
Not sure if this is something you had to simplify for the changes you're working on, or if it slipped through.
...SacredShield-mine hooked up to the side-left indicator...for my druid, it shows numbers, and yet not for my priest...abolish poison ... only shows a square dot indicator, rather than an option to show a countdown...
The default druid one is quite specific to what I want. I may try out abolish with a count down as well. I do feel blind not knowing when it is expiring ;-p
As for paladins I do not think anyone has provided a definitive default layout yet. If you are volunteering great, because my level 7 paladin is no good for testing.
I think a missing thing for paladins would be a aura group buff check (or custom status plugin) to make sure you have personally buffed each group member with something. For raids with more pallies than buffs this would probably need additional smarts to just make sure all buffs are there. Probably integration with pally power would not be wrong.
To get a timer you need to use a text indicator instead of a square one. One day icon / square / text indicators will be able to have their type changed to each other which would make that easy. For now you have to delete the old one and replace it with a text one.
I'm happy to help with paladin layouts, but I was wondering if it'd be better to work on a more thematic, overall layout that worked across multiple classes, so that no matter what class/spec you're using Grid2 from, you'll always find similar information in a similar place.
Taking how you've set the druid module up, for instance, the top three indicators (top left/right, side top) would be used to show things like HoTs and shields (including ES and Prayer of Mending, I guess) and healing-based cooldowns (bacon, GS, etc). There are cases where there will be more than three things that need to be tracked (druids having four hots, etc), but I would imagine that healers would want healing-based information up the top, and DPS would maybe want some defensive-type things up there too (OK, so a mage hitting frost or fire ward - and possibly mana shield - and a frost mage hitting ice barrier are the only ones I can think of : p).
While it may make sense for tanks to also have their defensive cooldowns being shown up the top, I would argue that they should be shown at the bottom of each box. This way, assuming that scanning for such auras wouldn't be too intensive, healers would be able to see when tanks use various cooldowns, and how much longer they're likely to last for. In my mind, at least, such cooldowns could probably be shown across the bottom three indicators (bottom corners plus sidebottom), with barkskin/shieldwall/divine protection/IBF sharing one indicator, ardent defender/last stand/survival instinct/vampiric blood sharing another, etc.
As far as paladins and a group buff check, hooking into pallypower may be a little redundant - it will already show when someone isn't buffed with whatever blessing you're assigned. From a raidleading perspective - or at least, a RL who isn't running pallypower themselves - I guess it might be handy to be able to filter for combined auras (with class filters) to show if the raid is missing some form of Kings, if melee are missing either bshout or bomight, if mana users are missing manaspring or bowisdom, if marked tanks are missing bosanctuary or [insert the name of the disc priest equivalent here]. I'm not sure if that would be overkill, tho' : )
Playing upon the above concept, I've been fiddling with the latest alpha for the last hour or so. I'm not sure how genuinely useful it would be for other people, but I seem to have had good luck setting the bottom right corner indicator to show icons, and adding mitigative cooldowns to it - for all four tanks, as well as some other not-quite-random things (bubble, forbearance, hand of sacrifice, safeguard, dispersion, cloak of shadows, etc.)
Made another icon indicator for side bottom, to overlay 'hp boosting' things like AD, VB, SI, LS. I'm not particularly happy with this placement, because it overwrites the default placement of things like wild growth, but I'm not entirely sure what to do about that now, or if it's really going to be an issue.
I created another indicator in the bottom left corner, set to show icons for threat related cooldowns, such as fade, hand of salvation, and intervene.
As far as the top three, I'm not really sure what to do - for a while now, when my paladin is healing and not tanking, I've had it set up so Bacon is shown in the top right, SS in the top left, and the FoL HoT (from SS) being shown as side top. I don't know if that's actually something other people would find handy. Using that kind of layout, tho', I'd probably have PW:S also in the top left corner, GS in the top right corner, and renew on side top. For shamans, I guess I'd be showing riptide as side top (it having the most in common with regrowth). This gives me pause for a few reasons (and probably others if I thought about it >.>): I don't know where I'd put divine aegis, for disc priests; ideally prayer of mending and earthsield would share the same indicator location, and yet priests are already crowded, and shamans have not much else to show.
I understand that you're still working on changing the type of statuses to be dynamic, rather than having to create a new one with the type a user needs.
In playing around with the newer builds over the last few days, tho', I've found that changing something from a 'dot' to an 'icon' or 'text' is a good way to break things, and force me to reset my SV.
Which would be fine except it means I lose a dozen or so customisations that make tanking and healing easier for me (adding certain raid debuffs to prioritise what is shown on tanks, adding numerical timers for bacon/sacred shield to mirror the druid hots, adding an icon overlay on top of 'aggro' to show when someone has threat reducing abilities on them, etc). The holy paladin, and threat-related, changes are trivial to re-add. Remembering which raid debuffs are for which bosses is annoying.
Is it possible that there be some kind of temporary measure to stop people doing that, until it's working as intended? If it helps narrow things down, I can try to deliberately break it and fish for exact error messages that're thrown up.
Getting back to the paladin thing: Grid2AuraGroup has healing-prevented etc at the moment. It would make sense to add something for mitigation as you describe. corner-bottom-right seems like a good spot for it. If you have the spell ids for them I can throw one together. There may already be something like that in Grid as well.
Unbreakable Armor: 51271
Bone Shield: 49222 (The above two talented CDs I'm a little unsure of, because they're also used as DPS cooldowns by non-tank DKs)
Hand of Sacrifice: 6940
Dispersion: 47585
Safeguarded Intervene: 46947
Divine Sacrifice: 64205 (I'd argue this one should be shown because the paladin casting it may not always pair it up with bubble or divine protection to reduce the damage redirect - something healers would probably want to know about so they can try to heal them)
Divine Guardian: 53530 (I've read it's possible to macro a cancelaura with the divine sacrifice cast, such that you can remove the damage transfer but keep the group/raid damage reduction aura in effect. I'm not sure if this should then be shown on everyone, or just the paladin who put it up)
HP-increasing (quasi-mitigative) CDs:
Last Stand: 12975
Survival Instincts: 61336
Vampiric Blood: 55233
Ardent Defender: 66233 (I think)
(Glyph'd) Frenzied Regeneration: 54854 (I think)
Guardian Spirit: 47788
I've found it easiest to set them up on an icon indicator just to see which ones they are at a glance. I'm not yet sure on what priority you'd want them, either showing the weakest on top of the stack, or the strongest.
YMMV, but I've also found it easy to track the HP increasing CDs by associating them with side-bottom-right, which is created via Grid2StatusTargetIcon.
(Something I was curious about and can't seem to find an answer to - when setting up class filters for the various buffs/debuffs, does that create a higher/lower/similar processing overhead?)
Having a weird issue that I know is related to Grid2 but I don't think it's necessarily it's fault, just perhaps an addon conflict. Sometimes when you or one of your party mates zones/drops out of the instance (we've only noticed it on randoms via LFD) WoW will completely lock up. It's possible to use Task Manager to kill the process and log back in, but something at that moment is totally hanging the game client.
For reference, I'm the author of ArkiveUI, and if you know my comp you know it has a lot of addons. Couple that with the fact that it doesn't happen every time and so far only at the end of randoms it's becoming very hard to troubleshoot. Only conflict I could think of might be Pitbull, which I use for non-raid unit frames. At any rate, if you know of anything I should check, or can think of a scenario where something like that could happen I'd love to hear about it.
A few final notes. It's never happened when someone has dropped/left/booted during the instance...only at the very end. Also, multiple users have confirmed the problem vanishes when Grid2 is removed. And finally, the Grid2 plug-ins I'm using are AFK, Aura, Group, and Res (all latest builds via Wowace).
I have been working on issues that could be potential causes. Nothing has fixed it yet however it seems less frequent now. I think jerry said he would take a look at it sometime next week as well. There is a ticket for it already:
The post narrows it down to versions 337+, however I suspect it started earlier as the code changed in 337 is limited to raiddebuffs. If someone has the intestinal fortitude to figure out the exact version it started in it would help a lot.
I'll see if I can't test a few, but r332 and to lesser degree r334 seem like good candidates for causes. It'll take a while, but I'll probably roll back to r331 and start from there. Perhaps the person who said it started with r337 just happened to be on an older release than they thought.
I have been working on issues that could be potential causes. Nothing has fixed it yet however it seems less frequent now. I think jerry said he would take a look at it sometime next week as well. There is a ticket for it already:
The post narrows it down to versions 337+, however I suspect it started earlier as the code changed in 337 is limited to raiddebuffs. If someone has the intestinal fortitude to figure out the exact version it started in it would help a lot.
I haven't looked at this specific issue. It seems strange indeed. I haven't logged in the game for quite a while. Testing this issue is difficult.
Finding the exact changeset that caused the issue would be ideal for me. 332 is more likely to be culprit than 334, but I'm not seeing anything wrong with it.
Ah ok. No, it is what it is right now. It could be more specific in the future though. Meanwhile you can edit the file and keep a copy of it then just paste your custom stuff if there is an update.
Grid2StatusRaidDebuffs.lua
change
to
to disable Glittering Sparks for example.
The difference between grid+quickhealth&shadowed uf's with quick health enabled vs grid2 is not neligible.
None that I'm aware of.
I suspect it would be somewhat easy to adapt an existing solution, if anyone is interested to try it. I'm not completely sold on the idea that using this kind of addon has a beneficial effect on raid performance (i.e. it's more a tool to enhance one's healmeter position than anything else).
if you go into settings / indicators / side-bottom, which statuses does it have set?
http://forums.wowace.com/showthread.php?t=17672
-
View User Profile
-
View Posts
-
Send Message
Curse Premium(At least, this is how it seemed to make sense to me, and when comparing it to the settings for Renew and PW:S for priests).
Just testing it on my priest/druid/paladin to see the differences now, however, and I'm noticing that for my druid, it shows numbers, and yet not for my priest. Is this something specific being done with certain spells? I noticed that abolish poison (on my druid) only shows a square dot indicator, rather than an option to show a countdown. Same on my pally - before I updated to the newer alpha builds, it was letting me 'show numbers' on other classes.
Not sure if this is something you had to simplify for the changes you're working on, or if it slipped through.
The default druid one is quite specific to what I want. I may try out abolish with a count down as well. I do feel blind not knowing when it is expiring ;-p
As for paladins I do not think anyone has provided a definitive default layout yet. If you are volunteering great, because my level 7 paladin is no good for testing.
I think a missing thing for paladins would be a aura group buff check (or custom status plugin) to make sure you have personally buffed each group member with something. For raids with more pallies than buffs this would probably need additional smarts to just make sure all buffs are there. Probably integration with pally power would not be wrong.
To get a timer you need to use a text indicator instead of a square one. One day icon / square / text indicators will be able to have their type changed to each other which would make that easy. For now you have to delete the old one and replace it with a text one.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumTaking how you've set the druid module up, for instance, the top three indicators (top left/right, side top) would be used to show things like HoTs and shields (including ES and Prayer of Mending, I guess) and healing-based cooldowns (bacon, GS, etc). There are cases where there will be more than three things that need to be tracked (druids having four hots, etc), but I would imagine that healers would want healing-based information up the top, and DPS would maybe want some defensive-type things up there too (OK, so a mage hitting frost or fire ward - and possibly mana shield - and a frost mage hitting ice barrier are the only ones I can think of : p).
While it may make sense for tanks to also have their defensive cooldowns being shown up the top, I would argue that they should be shown at the bottom of each box. This way, assuming that scanning for such auras wouldn't be too intensive, healers would be able to see when tanks use various cooldowns, and how much longer they're likely to last for. In my mind, at least, such cooldowns could probably be shown across the bottom three indicators (bottom corners plus sidebottom), with barkskin/shieldwall/divine protection/IBF sharing one indicator, ardent defender/last stand/survival instinct/vampiric blood sharing another, etc.
As far as paladins and a group buff check, hooking into pallypower may be a little redundant - it will already show when someone isn't buffed with whatever blessing you're assigned. From a raidleading perspective - or at least, a RL who isn't running pallypower themselves - I guess it might be handy to be able to filter for combined auras (with class filters) to show if the raid is missing some form of Kings, if melee are missing either bshout or bomight, if mana users are missing manaspring or bowisdom, if marked tanks are missing bosanctuary or [insert the name of the disc priest equivalent here]. I'm not sure if that would be overkill, tho' : )
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumMade another icon indicator for side bottom, to overlay 'hp boosting' things like AD, VB, SI, LS. I'm not particularly happy with this placement, because it overwrites the default placement of things like wild growth, but I'm not entirely sure what to do about that now, or if it's really going to be an issue.
I created another indicator in the bottom left corner, set to show icons for threat related cooldowns, such as fade, hand of salvation, and intervene.
As far as the top three, I'm not really sure what to do - for a while now, when my paladin is healing and not tanking, I've had it set up so Bacon is shown in the top right, SS in the top left, and the FoL HoT (from SS) being shown as side top. I don't know if that's actually something other people would find handy. Using that kind of layout, tho', I'd probably have PW:S also in the top left corner, GS in the top right corner, and renew on side top. For shamans, I guess I'd be showing riptide as side top (it having the most in common with regrowth). This gives me pause for a few reasons (and probably others if I thought about it >.>): I don't know where I'd put divine aegis, for disc priests; ideally prayer of mending and earthsield would share the same indicator location, and yet priests are already crowded, and shamans have not much else to show.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIn playing around with the newer builds over the last few days, tho', I've found that changing something from a 'dot' to an 'icon' or 'text' is a good way to break things, and force me to reset my SV.
Which would be fine except it means I lose a dozen or so customisations that make tanking and healing easier for me (adding certain raid debuffs to prioritise what is shown on tanks, adding numerical timers for bacon/sacred shield to mirror the druid hots, adding an icon overlay on top of 'aggro' to show when someone has threat reducing abilities on them, etc). The holy paladin, and threat-related, changes are trivial to re-add. Remembering which raid debuffs are for which bosses is annoying.
Is it possible that there be some kind of temporary measure to stop people doing that, until it's working as intended? If it helps narrow things down, I can try to deliberately break it and fish for exact error messages that're thrown up.
Getting back to the paladin thing: Grid2AuraGroup has healing-prevented etc at the moment. It would make sense to add something for mitigation as you describe. corner-bottom-right seems like a good spot for it. If you have the spell ids for them I can throw one together. There may already be something like that in Grid as well.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumBasic tank mitigative CDs:
Divine Protection: 498
Shield Wall: 871
Barkskin: 22812
Icebound Fortitude: 48792
Anti-magic shell: 48707
(Glyph'd) Hand of Salvation: 63871 (I think)
Unbreakable Armor: 51271
Bone Shield: 49222
(The above two talented CDs I'm a little unsure of, because they're also used as DPS cooldowns by non-tank DKs)
Tank 4pt10 bonus mitigative CDs:
Warrior - Stoicism: 70845
DK - Blood Armor: 70654
Paladin - Deliverance: 70760
Druid - Enraged Defense: 70725
Optional extras:
Hand of Sacrifice: 6940
Dispersion: 47585
Safeguarded Intervene: 46947
Divine Sacrifice: 64205 (I'd argue this one should be shown because the paladin casting it may not always pair it up with bubble or divine protection to reduce the damage redirect - something healers would probably want to know about so they can try to heal them)
Divine Guardian: 53530 (I've read it's possible to macro a cancelaura with the divine sacrifice cast, such that you can remove the damage transfer but keep the group/raid damage reduction aura in effect. I'm not sure if this should then be shown on everyone, or just the paladin who put it up)
HP-increasing (quasi-mitigative) CDs:
Last Stand: 12975
Survival Instincts: 61336
Vampiric Blood: 55233
Ardent Defender: 66233 (I think)
(Glyph'd) Frenzied Regeneration: 54854 (I think)
Guardian Spirit: 47788
I've found it easiest to set them up on an icon indicator just to see which ones they are at a glance. I'm not yet sure on what priority you'd want them, either showing the weakest on top of the stack, or the strongest.
YMMV, but I've also found it easy to track the HP increasing CDs by associating them with side-bottom-right, which is created via Grid2StatusTargetIcon.
(Something I was curious about and can't seem to find an answer to - when setting up class filters for the various buffs/debuffs, does that create a higher/lower/similar processing overhead?)
For reference, I'm the author of ArkiveUI, and if you know my comp you know it has a lot of addons. Couple that with the fact that it doesn't happen every time and so far only at the end of randoms it's becoming very hard to troubleshoot. Only conflict I could think of might be Pitbull, which I use for non-raid unit frames. At any rate, if you know of anything I should check, or can think of a scenario where something like that could happen I'd love to hear about it.
A few final notes. It's never happened when someone has dropped/left/booted during the instance...only at the very end. Also, multiple users have confirmed the problem vanishes when Grid2 is removed. And finally, the Grid2 plug-ins I'm using are AFK, Aura, Group, and Res (all latest builds via Wowace).
http://www.wowace.com/addons/grid2/tickets/
The post narrows it down to versions 337+, however I suspect it started earlier as the code changed in 337 is limited to raiddebuffs. If someone has the intestinal fortitude to figure out the exact version it started in it would help a lot.
I haven't looked at this specific issue. It seems strange indeed. I haven't logged in the game for quite a while. Testing this issue is difficult.
Finding the exact changeset that caused the issue would be ideal for me. 332 is more likely to be culprit than 334, but I'm not seeing anything wrong with it.
I did look at r369, and it looks fine too.