[Shaman][Restoration] Chain Heal

[Zhyna]

WoW Freakz spell link: https://www.wow-freakz.com/spells.php?spell=1064&&name=chain-heal
Bug description: As you can see in the ss from below, Chain Heal is healing Rithz (full hp) first, Portocaltank second and Deadly third. Normally, Chain Heal is a very powerfull smart heal, the order should be: Deadly (20%HP) -> Porto (50%hP -> Rithz (or somebody with low hp, (bounce radius is 12.5 yards) ). On freakz, the chain heal is healing the closest target first and bounces to another target, but not another low HP target, instead it bounces to the second closest target. As you can see in the tooltip, ,,the most injured party members,,.
Proof: https://imgur.com/GuIj6tV

[Ein]

2 tips:
- the smart heals don't target the most injured player, only a random injured player
Proof : Patch 6.0.2 (2014-10-14): Smart heals will now randomly pick any injured target within range instead of always picking the most injured target. Priority will still be given to players over pets.
https://wow.gamepedia.com/Smart_spell
- you should try with 3 injured player and 1 full and watch if the full heal player is healed. Maybe chain heal work this way: first choose the injured player and after the order of the healing is based purely on the distance.

i hope can help you and keep it up the testing

[Zhyna]

As you can see in the chat, Chain heal healed the player which was full hp. The spell description says: ,, Heals the friendly target for... THEN JUMPS TO HEAL THE MOST INJURED NERBY (12.5 yards) party or raid MEMBERS.,, In the scenario mentioned above, I used Chain heal on me, after that, Chain heal should've jumped to deadly, because he was the lowest and was in 12,5 yards range, and normally, the first healed target receives the maximum amount of healing, after that with each jump the heal is reduced by 30%, so because of this, I wasted the huge amount from the first jump healing Rithz which was full HP and another important thing: because deadly was so low, if I first healed him, the mastery would've made my heal even more powerfull(Mastery: Deep Healing, passive). So this is why this is a major problem for the resto shaman when people aren't stacked.

Proof: ,, Chain Heal is a 'smart' heal and always jumps to the eligible target with the largest health deficit in range. The bounce radius is 12.5 yards. Since the targets are linked into a chain, targets must be within range of each other, in order of "bounce". The chain cannot jump back to heal the same target more than once. ,, (wowwiki, but you can search and find this description on different sites)

[RedCoats]

Indeed, you are correct. Chain heal is a smart heal, meaning it should always prioritize the MOST injured target within bounce range (keeping in mind that it heals targets that are missing the most health numerically rather than targets with the lowest percent health).

[Ein]

Zhyna wrote:

Proof: ,, Chain Heal is a 'smart' heal and always jumps to the eligible target with the largest health deficit in range. The bounce radius is 12.5 yards. Since the targets are linked into a chain, targets must be within range of each other, in order of "bounce". The chain cannot jump back to heal the same target more than once. ,, (wowwiki, but you can search and find this description on different sites)

my bad you are right, i think that smart heal are all directed to a random injured pg.
here say that Chain Heal is a “super smart” heal meaning it will always prioritize healing the most injured target within bounce range. When calculating the “best route” to heal, Chain Heal heals targets that are missing the most health numerically rather than targets with the lowest percent health. An example of this is if a target is missing 40k health and is at 1% but another target is missing 50k health and is at 5%, Chain Heal will heal the target missing 50k health if they are both eligible targets for a jump.

[Zhyna]

Can somebody confirm and fix this? I know that dev are working on 7.3.5, but this is a major bug for resto shaman.
@Quicksand @Shocker

[Shammybro]

Confirmed, it is a quite significant bug and should be looked into asap.