CATA PREPATCH: Boosted DK is unable to obtain benefits of blood mastery shield

Bug: Boosted DK is unable to obtain benefits of blood mastery shield

  • Boost DK and login

  • Spec Blood and train mastery

  • Attack an enemy with Death Strike

  • Expected Result:

    • Mastery adds a shield for a partial amount healed by death strike
  • Actual Result:

    • Shield buff does not activate, nor does a “hidden” buff activate (I.E. damage is not absorbed anyway and hp is immediately lost

I am having the same issue as this post in the eu forums. they confirmed It is not an issue on their leveled DK:

3 Likes

Might also add the DK is a worgen, if that might matter

2 Likes

I have the exact same problem here. Level 80 boost, Worgen DK. Blood shield mastery is not working, doesnt show on Details or any weakauras/addons.

2 Likes

To add to this, I also boosted a DK (Last night) and it also does not get the shield. It is a Dwarf so it is not a Worgen issue.

1 Like

I’m experiencing the exact same issue on a boosted Goblin Death Knight. The Blood DK mastery, Blood Shield, does not activate under any circumstances.

After running several dungeons, it also seems as though Death Strike is only healing for the base amount, regardless of how much damage you’ve taken within the last 5 seconds.

1 Like

The talent improved death strike doesnt increase the amount healed, the base 7% healing or the 20% of the damage taken are not affected by the 45% extra from talents.

The problem with Death Strike healing on my character is that the damage I’ve taken within the last 5 seconds is not being accounted for when it comes to the Death Strike heal. Death Strike is always healing for exactly 7% of my hp regardless of how much damage I take.

Besides the Death Strike issue and the Blood Shield mastery not working, my character is also affected by the Improved Blood Presence talent not working correctly. Instead of reducing chance to be crit by 6%, it’s increasing the chance I take a critical strike.

The Blood Presence bug is already on the official Known Issues list, so hopefully that and these other problems are fixed after Tuesday maintenance.

confirmed after reset today this has been fixed - thanks blizz team for getting that through quickly