Heal prediction bugged

[Alpacadude]

Everytime I join a new dungeon instance or if I die a few times in an already joined one my healing prediction is not working unless I /reload. From what I remember I used to have an addon called CombatLogFixer that made it work.
Does anyone have a working version of this addon, know if I need some other addon for this problem, or do I need to do something else?
Thank you!

[ifreecrack]

same thing for me

[jrockz]

Which addon are you guys using? I'm having the same problem with VuhDo and thought maybe it was just that specific addon.

[sakais]

has the issue with LibHeal4.0 been fixed? Heal prediction is generally bugged until you reload your UI after entering an instance, and errors keep coming with downranked spells. I know more people experience this but the forum post is 10 days old and doesnt seem to be getting anywhere. Ive tried with Healbot on/off as well as other healing addons and I seem to experience the same error always. Thanks a lot.

[wowdualboxing11]

Its actually not any specific addon causing the issues, but the file "libHealComm-4.0".

I think it has something to do with spell ranks, but i tried some various fix's, but nothing worked.

Hopefully, somebody with more experience will fix it for us :)

[LezChap1]

Healing Prediction within ElvUI mostly works...sometimes I see heals hit (HP go up) and I don't see the prediction, but it doesn't seem to be any specific person or spell (usually things are too hectic for me to track too closely)...so I'm not sure what's going on.

[renderdruid]

Hi, I have tried most of the unit frames addons: grid, grid2, shadowed unit frames frames and elvui.

Every single one has a dependency on libhealcomm4.0 which throws lua errors everytime I cast flash heal (priest).
This also breaks features like 'incoming heals' indicators which makes it very hard to not overheal while progressing ragnaros.

I've had these addons for years and used them in multiple servers and this is the first time I'm running into issues.

[jrockz]

Hi, I have tried most of the unit frames addons: grid, grid2, shadowed unit frames frames and elvui.

Every single one has a dependency on libhealcomm4.0 which throws lua errors everytime I cast flash heal (priest).
This also breaks features like 'incoming heals' indicators which makes it very hard to not overheal while progressing ragnaros.

I've had these addons for years and used them in multiple servers and this is the first time I'm running into issues.

Try this, in "LibHealComm-4.0.lua" edit the following code on line 1207:

spellPower = spellPower * ((spellData[spellName].coeff * 1.88) * (1 + talentData[EmpoweredHealing].spent * 0.04))

change it to:

spellPower = spellPower * ((spellData[spellName].coeff * 1.88) * (1 + talentData[EmpoweredHealing].current))

Make sure it's the "flash heal" conditional you're modifying.

[wowdualboxing11]

Try this, in "LibHealComm-4.0.lua" edit the following code on line 1207:

spellPower = spellPower * ((spellData[spellName].coeff * 1.88) * (1 + talentData[EmpoweredHealing].spent * 0.04))

change it to:

spellPower = spellPower * ((spellData[spellName].coeff * 1.88) * (1 + talentData[EmpoweredHealing].current))

Make sure it's the "flash heal" conditional you're modifying.

How about the other heals that gives the same error? I seem to have issues with all the "fast" heals, also on shaman. And i wonder if it will break once TBC comes along. So we need to backup before editing so we can reverse it etc?

regards.

[jrockz]

How about the other heals that gives the same error? I seem to have issues with all the "fast" heals, also on shaman. And i wonder if it will break once TBC comes along. So we need to backup before editing so we can reverse it etc?

regards.

I only have a priest but yeah, this should work on all spells that give this type of error. Basically, you want to change the ending that says ".spent * <some value>" to ".current".

You should always make backups before you start modifying your addons. I don't know how this change affects wotlk/tbc since I only play on Onyxia atm. I don't think it would break but it might display the wrong prediction value in those versions.

[Darkorange]

I only have a priest but yeah, this should work on all spells that give this type of error. Basically, you want to change the ending that says ".spent * <some value>" to ".current".

You should always make backups before you start modifying your addons. I don't know how this change affects wotlk/tbc since I only play on Onyxia atm. I don't think it would break but it might display the wrong prediction value in those versions.

This worked :D