If you’ve rolled into the Azmodan world boss fight on your Necromancer and suddenly found yourself starved for Essence, you’re not imagining things — and no, your build didn’t magically break overnight.
Everything might feel fine leading up to the fight, your rotation works as expected, and then suddenly your resource bar refuses to cooperate when it matters most.
Right now, Reap isn’t generating Essence during the Azmodan world boss encounter, even though it works perfectly fine everywhere else in the game. The skill still hits, animations play normally, and nothing looks obviously wrong on the surface, which makes the issue even more confusing.
It’s a frustrating bug, and it’s been catching a lot of players off guard, especially those who rely on Reap as a core part of their Essence generation.
Let’s break down what’s going on, who it affects, why it only seems to happen in this specific fight, and what you can realistically do about it for now while waiting on an official fix.
What’s Actually Happening?
In short, Reap just stops giving Essence when you fight the world boss version of Azmodan. There’s no warning, no error message, and nothing obvious on screen to suggest the skill isn’t functioning as intended — it simply stops fueling your resource bar when the fight begins.
The skill itself still appears to work normally. Reap continues to hit enemies, damage numbers show up as expected, and the animation plays every time you swing. From a visual and mechanical standpoint, everything looks fine.
But the part that actually matters for your rotation — Essence generation — never triggers. The result is a completely stalled resource flow, especially noticeable in longer phases of the fight.
What makes this extra confusing is that Reap behaves perfectly everywhere else. It works on regular enemies, it works inside dungeons, and it even works on the Azmodan you can encounter out in the fields. The problem only shows up during the public world boss fight, which strongly points to a world boss–specific issue rather than anything tied to your gear, talents, or build choices.
Read also: Purified Horn of Duriel Drop Rate – Is It Bugged or Are You Just Unlucky?
Who This Bug Affects
This issue mostly hits a very specific group of players, which is part of why it’s been so confusing to pin down at first. At the center of it are Necromancer players, particularly those running builds where Reap is a primary or reliable source of Essence generation.
If your rotation depends on Reap to keep skills flowing, the problem becomes obvious almost immediately once the fight starts.
So far, the majority of reports are coming from PC players, though that may simply be because PC users are more active on forums and bug report channels. The bug also appears to be tied specifically to Azmodan as a world boss, not to Azmodan encounters found elsewhere in the game.
If Reap is a core part of your setup, this issue can completely throw off your damage output, disrupt your pacing, and force awkward pauses in what should otherwise be a smooth rotation during the fight.
Is This a Known Bug?
Yep — and you’re definitely not alone here. This issue has been popping up in player reports for months now, with multiple Necromancer players describing the exact same behavior: Reap works fine everywhere in the game except during the Azmodan world boss fight, where Essence generation suddenly stops altogether.
The consistency of these reports makes it clear that this isn’t an isolated glitch or a one-off setup problem.
The bug is also easy to reproduce, which usually helps speed things along, but so far there’s no confirmed fix. Blizzard hasn’t directly acknowledged the issue in patch notes, and there hasn’t been a hotfix that specifically mentions Reap or Essence regeneration during world boss encounters.
Because of that, it currently sits in that frustrating category of “known but unfixed” Diablo 4 problems — the kind that players just have to work around for now while waiting for an official solution.
Read also: Diablo 4 Torment Difficulty Not Unlocking?
Why This Might Be Happening
Blizzard hasn’t shared an official explanation for the issue yet, but based on how Diablo 4 handles large-scale encounters, there are a few likely reasons this bug keeps showing up during the Azmodan world boss fight.
One possibility is that world bosses operate under different combat rules than standard enemies or dungeon bosses. Those special rules may be unintentionally blocking Reap’s Essence-on-hit effect from triggering at all.
Another likely cause is server-side optimization. World boss fights involve a lot of players, effects, and calculations happening at once, so the game may simplify or override certain per-hit mechanics to keep performance stable. In doing so, it may be skipping Reap’s resource regeneration entirely.
There’s also potential damage attribution weirdness, especially when summons, adds, or phase-based mechanics are involved, which could prevent the game from correctly crediting your Reap hits.
Whatever the exact cause, the end result is the same: Reap works everywhere except where you probably need it most.
Can You Work Around It?
Sort of — but unfortunately, there’s no perfect fix for this issue right now. Since the problem appears to be tied directly to the Azmodan world boss encounter, there isn’t anything you can toggle or tweak to make Reap suddenly start generating Essence again during the fight.
Until Blizzard patches it, your best options are mostly about damage control. Swapping to other Essence generation tools specifically for world boss fights can help keep your rotation moving. You can also lean more heavily on Essence per second effects or passive resource gains, which aren’t affected by the bug in the same way.
It’s also a good idea to avoid builds that depend entirely on Reap when Azmodan is active, even if that means making a temporary adjustment. It’s not ideal, but adjusting your setup just for world bosses can keep your build from completely stalling mid-fight.
Should You Report It?
Definitely — and it’s worth taking a few extra minutes to do it properly. Even though this bug has been around for a while, clear and consistent reports are still one of the best ways to push it higher on Blizzard’s priority list. The more detailed the report, the easier it is for the developers to reproduce the issue on their end.
When you submit a report, make sure you clearly mention that Reap works normally outside of the world boss fight, but fails specifically during the Azmodan world boss encounter.
Include your platform, region, and the time the fight took place, since those details can matter for server-side issues. If you’re able to grab video proof, that helps a lot by showing the Essence bar not moving despite successful hits.
Clear, repeatable reports give this a much better chance of landing on Blizzard’s radar.
Read also: Corrupted Tongue of Azmodan Chest Not Spawning?
Quick FAQ
Does Reap generate Essence on the Azmodan world boss?
No. At the moment, Reap does not generate any Essence during the Azmodan world boss fight. Even though the skill hits normally and looks like it’s functioning, the Essence gain simply doesn’t trigger in this specific encounter.
Is this a Necromancer nerf?
No — this isn’t a balance change or a stealth nerf. There’s no indication in patch notes or developer comments that Reap was intentionally changed. Everything points to this being a bug tied directly to the world boss encounter itself.
Does Reap still work elsewhere?
Yes. Outside of the world boss version of Azmodan, Reap behaves exactly as expected. It generates Essence properly against regular enemies, in dungeons, and during other Azmodan encounters.
Is there a fix coming?
Nothing has been confirmed yet. As of now, the issue remains unresolved, and players are still waiting for an official fix or acknowledgement.
Final Thoughts
The Azmodan world boss Essence bug is one of those issues that feels especially bad because it breaks a core skill without any warning or clear explanation.
When a key part of your build suddenly stops working mid-fight, it can make your Necromancer feel clunky or even unusable, especially in a long, high-pressure world boss encounter. If that happens to you, it’s important to know it’s not a mistake on your end — the game simply isn’t playing by its own rules right now.
Until Blizzard sorts it out, the best approach is to tweak your setup specifically for world boss fights, rely on alternative Essence generation where possible, and take a moment to send in a detailed bug report. It’s not ideal, but it can help prevent the issue from completely ruining the run.
If you want this trimmed for a forum post, Reddit thread, or a quick bug report format, I can do that too.