Runeblade of Baron Rivendare
We’re unsure if this is a bug or intended such as Windsors haste buff or the infinite stacking of DMT buffs. However, in this video you can see how you can utilize the Unholy Aura from the weapon to “snapshot” your current +healing gear, switch out to a different set of gear, but maintain the Healing per 5 seconds from your +healing.
Additionally, you can also notice that the Unholy Aura (https://classic.wowhead.com/spell=17625/unholy-aura) scales at a 1:1 ratio with healing gear. This will ultimately allow Paladin, Warrior, and Hunter to stack a massive amount of healing gear, collect the snapshot, then swap to their DPS gear while maintaining unheard of regeneration. Which, yes, as you can see in the video works while in combat.
Indicated lists suggest the following MAX +healing by P6:
- Paladin: +1762 Healing
- Warrior: +1730 Healing
- Hunter: +1730 Healing
This is effectively a max roll of a Major Healing Potion every 5 seconds.
Some items and auras may have been missed, such as Priest’s Atiesh Aura. Additionally, we have not tested whether Power Infusion effects the “snapshot” of the aura its self or the actual gear.
If we assume PI does add to the snapshot:
- Paladin: +2114 Healing
- Warrior: +2076 Healing
- Hunter: +2076 Healing
Before everyone loses their mind. This does not open up the possibility of a single Paladin, Warrior, or Hunter being able to solo every raid boss. Even raid bosses such as Ragnaros pump out ~5000 damage every 5 seconds through FR. It would allow for some interesting shenanigans though.
Confirmation on Unholy Aura would be desirable from Blizzard.
Hi All,
I wanted to take a second and clear up any misconceptions about the nature of this bug fix. The Runeblade of Baron Rivendare neither scaled with +healing nor snapshotted any +healing effects in Original WoW or the 1.12 Reference client. This behavior was a bug that was introduced into WoW Classic. As such, the fix that went into 1.13.3 that removed the +healing benefit and snapshotting restored this item to it’s original 1.12 state.
As this bug is now resolved we will be closing this thread now. As always, thank you for your reports and analysis!
Fuente