Can't Heal You will automatically whisper people who you try to heal or buff, but who move out of your range or aren't in line of sight. That way, they know you're trying, and can possibly move to help you heal them.
It works automatically -- you just cast your healing spells and buffs the way you already do, even if that's through Healbot, Grid+Clique, or whatever. It also only whispers people who are in your raid, party, or guild, so you don't whisper random strangers you decide to try to buff.
Message: Interface\AddOns\CantHealYou\CantHealYou.lua:328: attempt to call global 'UnitGroupRolesAssigned' (a nil value)
Time: Tue Oct 13 20:40:03 2020
Count: 7
Stack: Interface\AddOns\CantHealYou\CantHealYou.lua:328: attempt to call global 'UnitGroupRolesAssigned' (a nil value)
...Ons\TradeSkillMaster\LibTSM\Service\ErrorHandler.lua:758: in function <...Ons\TradeSkillMaster\LibTSM\Service\ErrorHandler.lua:717>
[C]: in function `UnitGroupRolesAssigned'
Interface\AddOns\CantHealYou\CantHealYou.lua:328: in function <Interface\AddOns\CantHealYou\CantHealYou.lua:216>
Locals: errMsg = "Interface\AddOns\CantHealYou\CantHealYou.lua:328: attempt to call global 'UnitGroupRolesAssigned' (a nil value)"
isBugGrabber = nil
tsmErrMsg = nil
oldModule = nil
private = <table> {
globalNameTranslation = <table> {
}
FormatErrorMessageSection = <function> defined @Interface\AddOns\TradeSkillMaster\LibTSM\Service\ErrorHandler.lua:517
ErrorHandler = <function> defined @Interface\AddOns\TradeSkillMaster\LibTSM\Service\ErrorHandler.lua:134
origErrorHandler = <function> defined @Interface\SharedXML\SharedBasicControls.lua:295
hitInternalError = false
CreateErrorFrame = <function> defined @Interface\AddOns\TradeSkillMaster\LibTSM\Service\ErrorHandler.lua:536
num = 0
SanitizeString = <function> defined @Interface\AddOns\TradeSkillMaster\LibTSM\Service\ErrorHandler.lua:510
AddonBlockedHandler = <function> defined @Interface\AddOns\TradeSkillMaster\LibTSM\Service\ErrorHandler.lua:502
GetStackLevelInfo = <function> defined @Interface\AddOns\TradeSkillMaster\LibTSM\Service\ErrorHandler.lua:344
ParseLocals = <function> defined @Interface\AddOns\TradeSkillMaster\LibTSM\Service\ErrorHandler.lua:396
ignoreErrors = false
errorReports = <table> {
}
IsTSMAddon = <function> defined @Interface\AddOns\TradeSkillMaster\LibTSM\Service\ErrorHandler.lua:478
localLinesTemp = <table> {
}
GetStackInfo = <function> defined @Interface\AddOns\TradeSkillMaster\LibTSM\Service\ErrorHandler.lua:313
}
MAX_STACK_DEPTH = 50
OLD_TSM_MODULES = <table> {
1 = "TradeSkillMaster_Accounting"
2 = "TradeSkillMaster_AuctionDB"
3 = "TradeSkillMaster_Auctioning"
4 = "TradeSkillMaster_Crafting"
5 = "TradeSkillMaster_Destroying"
6 = "TradeSkillMaster_Mailing"
7 = "TradeSkillMaster_Shopping"
8 = "TradeSkillMaster_Vendoring"
9 = "TradeSkillMaster_Warehousing"
}
I wanted to let you know about a bug.
When I use Crackling Jade Lightning on an enemy, when the enemy is out of range, this addon will randomly whisper someone in my party or raid telling them I tried to heal them and they were out of range. It randomly chooses one of my healing spells to send them as something I tried to use. I have no idea why.
Any chance for updates on this in 2020?
Unfortunately, when WoW sends addons a message that the target is out of range, it doesn't give any helpful information such as which spell the message is about, who the target was, or anything like that. Thus, Can't Heal You has to save these things each time you cast a spell, and then use the saved information when it gets an ERR_OUT_OF_RANGE event. Since WoW can drop events, though, it's possible that you can cast a spell, CHY sees it and memorizes the information, but then you cast a different spell and CHY doesn't get notified of it. If that second spell gets ERR_OUT_OF_RANGE, since that error (unlike some of the other spell errors) doesn't include information about which spell and what target, CHY whispers the target of the previous spell, using the outdated information.
I'll see what I can do to improve it, but I can't guarantee that I'll be able to fix it 100%.
In reply to efindel:
I love this addon, but I'm having an issue where after I heal someone if I try to help DPS, it whispers the last person healed that they are out of range. Is there any fix for this or anything I can do?
In reply to meltedrose:
I have the same issue. Not so bad as a paladin since you heal tank 99% of the time, but when I change target and its out of range/los, the whisper goes to the tank (previous target).
Is there a built-in cooldown on whispers? Just so I don't accidentally spam the hell out of someone for whatever reason.
In reply to Col_Hathi:
Yes! You can configure the cool down between whispers in the configuration panel.
Any chance of this getting ported to Classic?
As a healer this is a major pet peeve of mine and I cannot find another addon that does the same.
In reply to Rjje:
It should work fine in Classic -- just turn on the option to load "out of date" addons. That will let you load addons "from the future" (i.e., with game versions higher than the current one) as well.
I absolutely love this addon. I have experienced a problem though and I haven't figured out how to fix it. I use both the VuhDo and Clique addons and as a MistWeaver Monk, I DPS a bit also. Whenever I've healed through VuhDo or Clique, then go to DPS using Blizzard keybound bindings, I've had this addon whisper my last target that it can't cast the spell used.
Any help will be greatly appreciated. It's not a big issue, but it has been annoying.
I've had several players not only thank me for this addon but apologize for going to fast or not realizing for LOS.
I thank you!
Thanks for the 7.3 update
In understand that it may be a good idea to choose if we like to use say, or party, or raid instead of whispers.
But this addon is a bit old and I think in some point I'll change the whole configuration to work as an Ace AddOn, but that required some rework, eventually I'll get it done.
I was not able to reproduce the error about saving the messages with the config as-is.
same problem as Barovian
I tried to edit the message but it wasnt saved, anyone knows how to fix that?
If anyone is still working on this addon, first a big thank you! I came looking for an addon like that cos healing Eye of Azshara can be a pain in the second boss fight due how often the DPS go LoS and this is a huge help. Tho I think some more options would make the addon perfect, if this can be done would be great. If you dont mind a suggestion , would be great if you could add an option to convert the whisper to player to a /say mentioning the player name. Thing is during combat many people ignore the whispers received, cos clicking in the tab to read it could complicate things, and I think many would find less spammy if said, since they are used to see warning on screen by DBM/etc. I tried to edit the message but it wasnt saved, anyone knows how to fix that?
Got RAGE attacked for this addon in a dungeon I was running for how "annoying it was". Shortly afterwatds he out of LoS and died because I couldn't get a heal on him.
Poetic justice.
Oh! Thanks for your addon! Don't know english enough to say more. Thanks! Thanks! Thanks!!!!
upd. And thank you for update. I'm afraid that's not gonna happen
Truly my greatest addon!
This addon gets more comments & questions from party members than all of my ~50 other addons, combined. This addon has saved lives many times.
Also interesting is how players respond to it. Wise players appreciate it and ask me for this addon's name. Paranoid players think I am a bot. Foolish players get annoyed. I especially like "trying" one last heal on a foolish prima donna who has run out of range and died. Those who comment get a macro I made that explains this addon's purpose: no-fault insurance :).