WowAce

Hi, I was looking for an addon that is similar to retails heal prediction of all healers on all players.

So I found this: https://github.com/LiuCJonathan/HealCommClassic/releases

Looking for more information I got to you and read

Addons supported

Injector, Shadowed Unit Frames, Pitbull4, Vuhdo, VisualHeal, PerfectRaid, X-Perl, Grid2, BobsToolbox, Stuf Unit Frames, oUF (with oUF_HealComm4 plugin + support), HealAssign, Grid, IceHUD

I know a guild member is using Vuhdo, but between the both of us, we dont share incomming heal information.

I personally dont really like changes to the way the interface looks, thats why I stick with Blizzard Party/Raid frames, and for my own heals the prediction is working just fine. When the other is using either the "addon" I linked above then he will see heal prediction on Blizzard default frames, but as a Vuhdo user he disabled them so he wont see heal prediction. The other way round, when I activate Vuhdo we also share heal prediction, but only in Vuhdo frames and NOT on the Blizzard frames.

I thought the intent of a library like this would be to enable players to choose whichever interface they want but allow the usage of said function?

It should definitely work if both addons load LibHealComm. Seems like either Vuhdo or HealCommClassic is at fault here.

I recently released ClassicHealPrediction (https://www.curseforge.com/wow/addons/classichealprediction). It adds heal prediction to the Blizzard default frames also. Try this one out, and report back whether or not it works. This should help narrow down the problem.

The issue could be caused by Vuhdo using v1.6.9 of this library while HealCommClassic is using v1.7.2

Technically they should be compatible since the communication protocol wasn't changed. If this is indeed the cause of the problem, it would be interesting to know how this incompatibility came to be.

This issue is likely because HealCommClassic uses a globally scoped class called HealComm, which shares a class name with LibHealComm. That may be causing some weirdness with Blizzard's addon message prefix registration.

The class was renamed in the latest patch of HealCommClassic, so maybe this is the last we'll hear of the issue

Not sure if this is the problem. Issue #72 looks similar. Judging from everything I've heard, v1.6.9 doesn't seem to be compatible with newer versions, but I didn't test myself.

I just confirmed yesterday that HealCommClassic worked both ways (sending and receiving heals) with a Vuhdo user. It's possible the user manually updated their library to v1.7.3, but for now it definitely seems like the problem was a namespace issue caused by HealCommClassic.