Righteous Fury
From WoWWiki
"A Paladin's fury is a quiet, solemn thing, ever a hair before the bloodlust of a Warrior or the ferocity of a beast. But it holds his foes just the same."
| Righteous Fury | |
|---|---|
| |
| Usable by | |
| Class | Paladin |
| Properties | |
| Type | Defensive |
| School | Holy |
| Cooldown | 5 Minutes |
| Talents | |
| Improvement talents | Improved Righteous Fury |
| Other information | |
| Ranks | 1 |
| Related buff | |
| |
Increases the threat generated by all of the Paladin's Holy spells. Lasts 30 minutes.
| Rank | Level | Mana Cost | Cost |
|---|---|---|---|
| 1 | 16 | 24% Base Mana | 30
|
Talent Improvements
- Improved Righteous Fury (3 Ranks) will additionally decrease damage taken by the Paladin by 2/4/6%.
Tips & Tricks
- Righteous Fury is absolutely necessary for Paladins who are Main Tanking to ensure adequate threat generation. The 6% damage reduction from the Improved Righteous Fury also makes a significant difference.
- It is a good practice to recast it frequently even when it may still have half the duration left, and always recast it before any boss fight. This is to ensure it will not expire in the mid of the fight, which will likely resulting in the DPS pulling aggro easily.
- This increases the threat generated by all holy spells, including healing spells.
- Depending on the fight and spec, healing with Righteous Fury active can be either good or bad. Numerous higher tiered raids have large amounts of AOE damage, where the 6% damage reduction from Improved Righteous Fury can save a healer's life, and healing aggro is seldom an issue. However, many fights include aggro wipes or reductions, and 6% damage reduction is not worth pulling off the tank. Keep an eye on the threat meters and know the fights before activating Righteous Fury as a healer.
- Activating this spell with a Retribution build will deactivate the threat-reducing properties of Fanaticism while the buff is active.
Mana Usage Bug
- Previously, players would note that casting this spell drains more mana than the listed cost. This issue was resolved in Patch 2.3.2.
| |||||||||||
