H.H.T.D.
H.H.T.D.
In World of Warcraft healers have to die (H.H.T.D). This is a cruel truth that you're taught very early in the game. This add-on helps you influence this unfortunate destiny in a way or another depending on the healer's side...
This add-on is now known as H.H.T.D.
I originally chose the original name as a provocation to make one of the basic cruel truths of World of Warcraft perfectly obvious to everyone. Now I find this name too harsh, too long and mostly not specific enough to WoW.
As an author I could not stand that name anymore. This add-on does have an existence (and meaning) both in WoW and in the real world where obviously we don't want the death of our beloved healers...
While H.H.T.D is just an acronym of the original name, it will stay in World of Warcraft where it belongs.
Current features:
HHTD automatically adds healer symbols on top of players nameplate indicating their class and healing rank. Unlike other add-ons it only takes into account actively healing players. (It uses different symbols for friends and foes).
HHTD lets you apply custom marks on top of any unit's nameplate. These are the same marks as the default raid markers but you can set as many as you want and customize their look. These marks persist across game sessions. (They are only visible to you)
IMPORTANT NOTE: You have to enable nameplates, else you won't see any healer symbol!
HHTD lets you announce through a customizable message who the enemy and friendly healers are (using the Raid Warning channel if possible).
It will also help you protect the healers who are on your side alerting you when they are being attacked (check the option panel for details).
Helps you target healers easily when they are in a pack.
All of this applies to PVP and PVE.
NOTE: Type /HHTDG to open the configuration panel. There are many settings to check!
HHTD's options are not directly available in the "Interface" panel due to ongoing tainting issues Blizzard is not willing to fix.
That player is not a healer?
If you see a player marked as healer that should not be:
If their mark's background is NOT grey, check the 'Logging' option in the option panel (/HHTDG) ; then when you see such a player, reopen the option panel and check the content of the 'Logs' tab and report to me by opening a ticket. Please avoid comments on Curse.com as it's impossible to follow what happens there).
If their mark's background is grey then enable the 'Healer specialization detection' option so as to only report specialized healers ignoring others.
Also note that the healer's rank is displayed as a number in the center of the displayed mark so you can judge the importance of that player in the healing currently being done (the lower the number, the better the healer).
How it works
HHTD uses the combat log events to detect friendly and enemy healers who are currently healing other players (during the last 60s). HHTD detects specialized healers spells (for human players only) and differentiates specialized healers from hybrid ones.
HHTD also lets you choose a specified amount of healing healers have to reach before being marked as such (50% of your own health by default). This threshold is the only criterion used for NPCs.
When a healer is identified it will be marked with a healer symbol above their nameplate. If the healer is specialized, the symbol's background will be colored according to their class. In other cases the background will be grey.
In all cases a number in the center of the symbol indicates the rank of the healer, the lowest the number the better the healer (ie: '1' represents the most effective healer while '9' is the least effective).
You can force HHTD to only report specialized healers through HHTD's options (/hhtdg).
Needless to say that self-heals and heals to pets are filtered out.
Commands
/HHTDP (or /hhtdp) posts healers name to the raid channel ordered by effectiveness for all to see (Will use the Raid Warning channel if possible).
You need to configure the messages in the announce module options first.
You can bind the above command to a key (WoW key-bindings interface)
/HHTDG opens option panel
/HHTD gives you access to the command line configuration interface (useful for changing settings through macros...)
Planned features
- Detection when a friendly healer is being attacked and alert others through /yell, /say and emote.
Compatibility
HHTD is only compatible with nameplate add-ons which have been coded responsibly and do not modify internal parts of Blizzard nameplates (a very selfish behaviour as it prevents any other add-on from re-using them).
HHTD will detect these incompatibilities and report to you so that you can ask the culprit add-on authors to fix their code and make it compatible with ALL nameplate add-ons.
Guidelines for other add-on authors:
Do not call :Hide() or :Show() on nameplates' base frame. This breaks nameplate tracking for other add-ons by unduly firing OnHide/OnShow hooks...
Instead, make its sub-frames invisible by changing their size and/or setting them to the empty (not nil) texture. (check out how TidyPlates does)
Do not call :SetParent() on nameplates' subframes, this would prevent other add-ons from finding and hooking nameplate elements.
Do not use SetScript() EVER. You don't need it. :SetScript() shall only be used on frames YOU create. You can simply replace all your SetScript() calls by HookScript().
Videos
Here is a video by Hybridpanda featuring HHTD in the Eye of the Storm battleground:
YouTube - This makes me a sad Panda
Articles
Here are two excellent articles about HHTD by Cynwise (A must read if you have some doubts about the fairness of this add-on!) :
HHTD and the PvP Addons Arms Race
Using HHTD to Protect Friendly Healers
Here is another article written by Gevlon (a PVP healer).
type /hhtdg to open the configuration interface, or /hhtd for command-line access
Comments and suggestions are welcome :-)
To report issues or ask for new features, use the ticket system.
Bitcoin donation address: 1JkA5Ns1dMQLM4D8HUsbXyka6yhp312KnN
Hopefully we get a patch for this :) I'm donating now to help.
I couldn't live with out it.... literally
:)
Thank you for this master peace.
Hello. Lately I keep getting a debug 1612.722 and debug 1685.367. Not sure why I'm getting these all of a sudden or what it means or what I should do. Thanks for any help.
Is there anything else in these debug messages?
as a healer, i do not approve this addon.
This add-ons simply states a hard fact of WoW...
I've changed the description to make it more friendly and emphasize that it works both ways...
As a healer, your place is at gy.
Hello there :) I just had a quick question. So basically, to my knowledge the only way to get the icon to appear is for someone to actually do a chosen percent of healing. But my issue is that a lot a dps specs can self heal (WW monk, Ret paladin). So a lot of the time I guess a dps with a healing icon above there head, which is somewhat misleading. So is there any way to configure it so that it only shows people in healing spec and not dps? Love the addon either way :) Thanks!
Self heals are ignored. DPS specs who happen to heal enough to reach the threshold should have a greyed-background icon and a lower ranking (number > 1 in the center of the symbols).
You also have an option to force HHTD to only tag true healers.
Check the screenshots
Is there a way to fix the error incompatibility between TukUI and LibNameplateRegistry? I'm not sure why this hasn't been ironed out after all of these years, but if there is some simple change I could make to TukUI (which I understand could be looked at as being more blame-ful here) then I'd like to do it at least locally, and see if I could get it into the main TukUI distribution.
You have to check that with TukUI's author but the main points are (as said in the description above):
Guidelines for other add-on authors:
nameplate tracking for other add-ons by unduly firing OnHide/OnShow hooks...
Instead, make its sub-frames invisible by changing their size and/or setting them to
the empty (not nil) texture. (check out how TidyPlates does)
Do not call :SetParent() on nameplates' subframes, this would prevent other
add-ons from finding and hooking nameplate elements.
Do not use SetScript() EVER. You don't need it. :SetScript() shall only
be used on frames YOU create. You can simply replace all your SetScript()
calls by HookScript().
Thanks for the reply. I'll see what I can do.
@magicwildo
Yeah, I agree. This addon pretty much ended my pvp healing. Once it came out, all the sudden healers were much bigger targets than before. It automates an aspect of pvp that used to be about skill and situational awareness.
Do you know that this add-on is 7 years old? Where did all these years go O_O
I made this add-on because it used to be difficult to click/target healers inside a pack of players... but then I've made it so it would encourage better team play by making it also useful to protect friendly healers. (check the feature list above)
Sigh, I wish people would stop making addons like this. It might look fun on paper but it's bordering on cheating. I genuinely wish Blizzard would destroy the function of this addon.
Any chance on allowing the alert sounds to be changed. Currently you are using 'AlarmClockWarning3.ogg' and 'AuctionWindowOpen.ogg'?
The alerts are okay, but choice is always better.
Thanks!
Hi !
I've been using your great addon for a few months now, I have a very annoying situation with it sometimes, mostly when I do PvP with a group (Ash'ran or BG), I use to be spam with the mention "you are not in a raid group" ... it takes all my dialogue box and I can't read all usefull info in it. I've tried to deactivate all addons I'm using and it comes that the one that spamming me is HHTD.
Do you have any idea on how to fix it ? I really want to continue to use it but I becomes harder and harder to work again with it.
Anyway, once again, congrats for your work !
If you use recount you have to uncheck the Sync button in ur settings. And if anyone else is using in recount in ur raid or group they have to do it also or else u will still get that message.
that's strange I'm not sure how HHTD could be causing this since it doesn't post to the raid channel unless you use its announce feature through a key mapping...
Have you try to leave HHTD on and deactivate all other add-ons?