Classes
Vengeance Gets Three Defensive Buffs September 1. Rebuild the Cooldown Map
Vengeance receives three different defensive improvements on September 1. Map the universal, Frailty-dependent, and recovery layers before changing a proven tank route.
Vengeance Demon Hunter is scheduled to receive three defensive buffs on September 1, and each one solves a different part of the damage problem.
Demonic Wards will reduce all damage by 15% instead of 12%. Void Reaver will make enemies affected by Frailty deal 6% less damage to the Demon Hunter instead of 5%. Fel Devastation's healing will increase by 25%.
Blizzard's explanation is direct: Vengeance has been performing below expectations defensively, while Fel Devastation's recovery has fallen behind as maximum health increased.
The tempting response is to delete a cooldown from the route and pull bigger. That would treat a passive layer, a target-dependent layer, and an active channel as if they were one blanket buff.
They are not. The safe Week 2 adjustment is to map where each change exists, then test whether an old overlap is genuinely redundant.
Demonic Wards improves every damage event, but not by 25%
Demonic Wards is the cleanest change. Its all-damage reduction rises by three percentage points, from 12% to 15%, without asking the player to tag a target or channel an ability.
The percentage wording makes the buff easy to overstate. Before the change, 88% of an affected hit remains after this isolated layer. After the change, 85% remains. Divide 85 by 88 and the same incoming damage is about 3.4% smaller through that layer. Do not simply add that result to another reduction without confirming how the live effects stack.
That is valuable because it is universal. It helps on a melee swing, a magic hit, a bleed, a missed stop, and damage that arrives while the Demon Hunter is moving between targets. It also helps when the player's active plan is imperfect.
It does not make the spec 25% tougher. “Twelve to fifteen” is a 25% increase in the number printed for that one reduction, not a 25% reduction in total damage taken. Armor, other mitigation, enemy debuffs, absorbs, and encounter effects still determine the final result.
The practical effect is a slightly higher floor. A health trough that barely forced an emergency button may become manageable. A lethal event will not necessarily stop being lethal.
Void Reaver only exists where Frailty exists
The Void Reaver change is smaller and conditional. An enemy affected by Frailty will deal 6% less damage to the Demon Hunter instead of 5%.
For damage from that qualifying enemy, the isolated layer changes from letting 95% through to letting 94% through—about 1.05% less damage through that layer. That number is not the whole value of Frailty or the talent package. It is the size of this announced change when the condition is met.
The condition is the important part.
If the dangerous caster, boss add, or newly joined enemy is not affected by Frailty, Void Reaver is not covering its damage. A pull with coverage on every enemy hitting the tank is different from a pull where a priority source spends its lethal window outside the debuff.
For each dangerous pull, ask:
- Which enemy supplies the largest tank hit or unavoidable event?
- Is that source consistently affected by Frailty before the event?
- Does a late spawn, forced swap, or movement create a coverage gap?
- Is the current talent package actually using Void Reaver?
A sheet that says “Frailty active” is too vague. The question is whether the right source is affected at the right second.
Pull entry is still the dangerous transition
Fresh player feedback repeatedly points to the gather as the moment Vengeance feels least settled. Tanks describe losing globals while moving, turning their backs to enemies, waiting for resource and Frailty coverage, or discovering that a ranged tag did not create enough threat. Healers describe Demon Hunters arriving before their defensive engine is running.
Those reports conflict on the perfect opener, and builds differ. The useful lesson is not a universal first-three-global script. It is to map the transition from “mobs are moving” to “the pull is established.”
For each large gather, record:
| Entry question | Why the September 1 buffs do not answer it alone |
|---|---|
| What faces the tank first? | Universal mitigation helps, but being hit from behind still changes the danger |
| When does the dangerous source receive Frailty? | Void Reaver has no value from that source before coverage |
| What creates immediate threat? | None of the three announced changes directly buffs snap threat |
| Which button covers the first health drop? | Fel Devastation heals during its channel; it is not pre-hit armor |
| What happens if the gather takes longer? | Movement and lost rotational globals can delay souls, Fury, and recovery |
This is the best place to spend the new passive margin carefully. If a pull was failing before the engine started, measure that transition before adding another pack.
Fel Devastation has a job, not one universal timestamp
Fel Devastation's healing is scheduled to rise by 25%. Under the same talents, stats, target access, and completed channel, that means 1.25 times its previous healing—not a heal for 25% of maximum health.
It costs Fury, channels, damages enemies in front of the Demon Hunter, and heals during that window. It is a recovery tool, not pre-hit mitigation, so its effective value depends on conditions a passive reduction does not care about.
The tank needs enough resource to press it. Targets need to remain in front. Movement, crowd control, an interrupted channel, or healing that lands into an already full health bar can reduce the practical gain. The ability also contributes damage, threat, and rotational value, so holding it indefinitely can carry a cost.
This is where current advice genuinely splits. Some players save Fel Devastation for a heavy damage window. Others use it early to help establish threat, generate value, and stabilize the pull. Current specialist writing describes it as more niche after Demonic's removal.
Do not settle that disagreement with a slogan. Give the button a job on each marked pull:
- Entry: press while targets are connected to help establish the pull, accepting possible overheal.
- Sustain: place it inside a known intake window where most of the channel can heal effectively.
- Recovery: use it after a survivable hit, provided the tank lives long enough to channel.
Then check the log or combat record. If most healing overhealed, it was not acting as recovery. If the tank died before the first tick mattered, it was not valid coverage for that event. If holding it caused a threat or rotational problem, that cost belongs in the result.
Do not erase the red boxes before the reset
Reliable tank routes already contain red boxes: the tankbuster that always gets a named defensive, the double pack that receives Fiery Brand, the corridor where active coverage cannot lapse, or the pull where an external is called before health starts moving.
Leave those boxes in place for the first post-tuning run.
Experienced players disagree with a simple “never overlap defensives” rule because random Metamorphosis procs, resource flow, and pull length change the available sequence. That is exactly why the map should describe jobs rather than enforce a tidy rotation that the dungeon will not follow.
Mark the moments that were already survivable but expensive:
- A defensive overlap that prevented a useful recovery window
- An emergency healthstone or potion used on most attempts
- A healer external requested for a non-lethal pack
- A Fel Devastation channel that consistently recovered too little
- A pull where the dangerous enemy briefly escaped Frailty coverage
Those are candidates for testing. The lethal tankbuster is not the first experiment.
Run a fixed-route A/B test
The cleanest post-reset comparison uses a route the group has already completed. Keep the key level, talents, pull size, and planned cooldowns as close as the available keys allow. Run the old map once before moving anything.
Record outcomes that matter to survival rather than overall damage ranking:
1. Lowest health reached on the marked pulls 2. Whether a planned external or consumable was still required 3. Fel Devastation's effective healing, overheal, and channel completion 4. Whether the dangerous source had Frailty at the relevant event 5. Whether a death occurred before recovery was possible
On the second comparable run, move one piece. Perhaps an external shifts to the next pull. Perhaps Fel Devastation replaces an overlap during sustained damage. Perhaps nothing moves because the healer plan already uses the margin elsewhere.
One change gives the result meaning. Pulling two extra packs, swapping talents, changing the defensive order, and removing an external at once does not test the buff; it creates a new route.
What these three buffs do not directly fix
Vengeance players responding to the notes also asked for a shorter Last Resort cooldown, stronger snap threat, different talent access, and restored utility. Those concerns may be valid, but they are not effects hidden inside the three announced numbers. The August 25 Mastery buff is also a separate live change; it should not be folded into the September 1 package to manufacture one larger defensive percentage.
Demonic Wards does not change Last Resort's cooldown. Void Reaver does not apply Frailty for you. Fel Devastation's healing increase does not directly improve a ranged tag's threat. None removes the random timing of Apex-driven Metamorphosis procs that current guides identify as part of high-key survival.
That boundary matters in both directions. The notes should improve defense even if they do not answer every class-design complaint. They also do not justify telling a player that every adjacent problem is solved or that Vengeance has become the automatic meta tank.
The healer should know what changed
Passive mitigation can make a tank look smoother without making the timing obvious to the healer. A larger Fel Devastation heal can also resemble an unexpected health spike if the group has not discussed the plan.
Before the first post-reset key, tell the healer which pulls remain unchanged and which recovery window is being tested. If an external is moving, name its new job. If Fel Devastation is expected to carry a sustained section, identify what happens if the channel is interrupted or the tank has to leave the targets.
Vengeance is a mobile, active tank whose health can move quickly. The value of a stronger self-heal is partly the healing the group can redirect elsewhere, but only when the healer trusts that the tank's next button is available.
A defensive buff is permission to measure
The September 1 notes should make Vengeance sturdier. The passive floor rises, Frailty-covered sources lose a little more damage, and Fel Devastation gains recovery. None of that requires pessimism.
It does require precision.
Treat Demonic Wards as universal margin. Treat Void Reaver as coverage you can verify on the dangerous target. Treat Fel Devastation as a button whose job depends on resource, targets, timing, and effective healing. Then use the first post-reset route to find where those layers turn an old overlap into excess.
The best outcome is not proving that the spec can survive a larger pull on patch-note math. It is arriving at the next key with a cooldown map that shows exactly why it can.