My final thought... While *I* am 100% sold on Grid, my guild isn't. It's an overwhelming tool to the average user who wants to install and play without messing with any settings. So I find it hard to sell it to them, even though the guild could benefit tremendously. Most of the documentation on the WowAce site is geared towards Ace users who are generally more of the tinkerer type then your average user. I think a short "idiots" guide is in order to help sell this wonderful addon to the average joe. Maybe one guide focusing on how to configure for healing, and another guide to show how to configure for curing debuffs. I also think talking about click-casting mods would be helpful as well since I betting that 80%+ of the users use some click-casting mod in conjunction with Grid.
I added the subgroup weighting like I promised. I consider it alpha code at this point as I haven't tested it thoroughly. I also added more events that trigger a priority update (aggro, buff/debuff).
I'm still undecided whether to use the bucketevent (aceevent.lua) registration. I think this mod should be quick with it's updates and I don't want to put any delays into the system. I also want to be resource cautious so I could go both ways on it.
I wish there was an event I could work from for incoming heals since that would help out a lot with minimizing overheals and time wasted by the healers in a raid.
Please test the code and tell me how it works for you.
Made a mistake in current SVN version, which will probably result in some null errors.
-- If PvE raid, modify priority depending on how many healers, main tanks, & melee classes are in each subgroup
if (select(2, IsInInstance()) ~= "pvp") and (GetNumRaidMembers() > 5) then
local u = RL:GetUnitObjectFromUnit(unitid)
m = m + subgroupModifier[u.subgroup]
local u = RL:GetUnitObjectFromUnit(unitid)
local u = RL:GetUnitObjectFromUnit(UnitName(unitid))
I will commit changes when I get home tonight.
I will also add the GridStatusGained & GridStatusLost events for updating the priority when "alert_heals" (incoming heals) is on a unit. This should help prevent overhealing and wasting time casting a heal on someone who is already being healed.
I tested the current version last night and it seems to be working great. I think I finally have a very stable version. If you've had any bad experiences with previous versions, I recommend updating to the latest and trying it out now.
have a quick question. in the instructions you say to disable the other borders. i've been using this for awhile with both the low health and low mana borders still enabled. i've noticed that the low health border will not display at all now, is that due to this addon? i should probably just disable it though, as it would complicate the display if it did work.
i would like to keep the low mana border though so i can see when a mana break is needed, and i'm wondering if it effects this addon at all if i have it enabled? is it really all that important to have the other borders disabled if they are a lower priority than gridstatushealer? showing who needs to be healed is a lot more important than showing who has low mana, so i would disable it if need be.
oh, and another question. is the default color for the second priority less visible on purpose? i just realized this might be the case which i think is a good idea, it's less distracting that way. i changed my colors though and i'm wondering if there is a way to reset them to the defaults?
Ok, this might get confusing but I will do my best to explain.
Grid has a priority concept that should not be confused with my healing priorities. Grid's priority is used to determine which indicator takes precidence when both statuses are "on" for a unit. The values can be set between 1 and 99 I believe. 99 means it has the highest priority and 1 the lowest. So if you enable both the low mana and the healer priorities, I suggest setting the low mana priority to something lower then 99. So if a mage in g1 has low mana, the low mana border will show, unless they also become a healing priority, then the healing priority will overwrite the low mana indicator.
The good news is that if a unit has no mana, they probably will never be a healing priority since they have become somewhat useless to the raid anyways. I have code that lowers their priority when they are out of mana.
My instructions to disable the other indicators is just a personal preference. You are welcome to turn on any status indicator you want. My plugin should never interfere with any other status indicator plugin... whether it's the build in ones or third party.
not confusing at all, it's how i thought it worked, just wanted to be certain. thanks for the reply.
i would still like to know if there is a way to reset to the default colors?
Sorry, I missed that question. I can't really answer that question properly until I went home and looked at how the settings are saved in the WTF folder. I'm embarrassed to say I don't know if the data is saved into a GridStatusHealer settings file or in the main Grid settings file. I'm sure you can find it if you look though. Just open the file up with wordpad and change the color values to what they are in my LUA file. I think I used a bright tennis ball yellow for the "First Priority" and a darker, greener, more faded color for the "Second Priority".
If there is a way to reset the colors from the GUI, Maia or Pastamancer would need to answer that.
The settings of all Grid modules are saved in WTF/Account/ACCOUNTNAME/SavedVariables/Grid.lua - you'll have to search for the module name, the rest should be intuitive. The GUI itself does not offer and way to reset to defaults - but given the progress of WaterfallLib (check Niagara) we might see better ways to configure Ace2 addons soon.
I haven't updated GridStatusHealer in some time now. I plan on doing an update soon, but I wanted to find out if there are any problems people would like to see fixed, or suggestions before making the final update.
- add functionality from GridStatusThreat to priorize people with high threat
- add functionality from GridStatusHealingReduced
- update the addon for all the new raid boss debuffs that might be relevant
- support IncomingHealsLib besides the default CastCommLib
In my local copy:
-Tweaked the classModifiers for Shaman since I now play a Shaman and I know who they are best at healing
-Lowered the priority for players with Prayer of Mending buff
-Eliminated priority for players with healing prevention debuffs
-Raised priority for players that are within 80% of the threat of the highestThreatEnemy (I look through player/maintank targets & targettargets).
I know nothing about the IncomingHealsLib. Is it stable? Is it used in any other addons that work well?
Unfortunately there's no way of searching the SVN for addons using a specific lib - but I think sRaidFrames are using it, and maybe also xPerl and some other (non-raidframes) addons. So probably its support should be added to Grid core to be abe to track more heals than with GridComm.
I commited the changes I mentioned. Please try out the latest version and give me feedback.
I could not find any reference to IncomingHealsLib in either sRaidFrames or X-Perl. I am assuming that the lib is not highly used, so I will stay away from it until I find out it's used in a stable addon.