Diablo 4’s Tree of Whispers Is Broken and Can Block All Further Progress

Diablo IV Season 15 has somehow managed to make the Tree of Whispers considerably more generous and completely useless at the same time. Players across PC and consoles are reporting that after reaching 10 Grim Favors, the usual Choose Your Reward screen opens with no caches inside it. The reward slots are blank, the Accept button cannot be used, and closing the window leaves the character sitting above the normal Grim Favor limit. Worse, once that happens, additional Whispers can become unavailable entirely.

This is not simply a visual problem where the cache icons forgot to load while the reward secretly exists somewhere behind the interface. Players are reporting characters stuck at values such as 11/10 and 13/10 Grim Favors, unable to complete the turn-in and therefore unable to properly reset the Whisper cycle. Blizzard has now officially acknowledged the problem, saying it is investigating an issue that prevents completed Whispers from being turned in at either Ravens or the Tree of Whispers.

Season 15 has already had several launch problems.

This one is particularly nasty because it can shut down an entire endgame activity.

The Tree of Whispers Reward Screen Is Completely Empty

The problem itself is easy to recognize.

You complete enough Whisper objectives to reach the required 10 Grim Favors. The map tells you it is time to collect your reward. You interact with a Raven of the Tree or travel all the way back to the physical Tree of Whispers in Hawezar.

The familiar reward window opens.

And there is nothing in it.

No cache names.

No icons.

No selectable reward.

The Accept button remains disabled.

Only Close works.

One of the larger reports on Blizzard's bug forum describes exactly that sequence, with the player reaching 10+ Favors and seeing a completely black reward area where the cache choices should normally appear. Other players quickly confirmed the same behavior across different difficulties and characters.

The issue has also been reported on PlayStation and Xbox, so this does not appear to be confined to one PC installation, one launcher or one especially cursed graphics driver.

It Can Block Every New Whisper Afterward

The bigger problem starts after the failed turn-in.

Normally, handing in 10 Grim Favors clears the required amount and allows the Whisper cycle to continue. Diablo IV also supports overflow. If you are sitting at 9/10 and complete a five-Favor activity, you can temporarily reach 14/10, with the extra progress carrying forward after the reward is collected.

That system has existed for multiple seasons.

With the current bug, however, the reward cannot be collected.

The character remains above the threshold.

Several players then report that additional Whisper activities on the map become greyed out or explicitly show Whispers as unavailable. One player described reaching 13/10 and being unable to do anything else because the game never completed the existing reward cycle.

So this is not simply:

"I lost one cache."

It can become:

"My character cannot continue using the Tree of Whispers at all."

Blizzard Has Officially Acknowledged the Problem

The good news is that this one is no longer sitting entirely inside community bug reports.

Blizzard added an official update to the Hotfix 2 discussion, confirming that the team is investigating an issue preventing players from turning in completed Whispers at both Ravens and the Tree of Whispers.

A later update said the investigation was continuing and that Blizzard was aiming to have a fix ready soon, while warning that the timing could still change.

That is important because it means players do not need to spend the afternoon reinstalling Diablo IV under the assumption that their local files have personally offended the Tree.

The problem is known.

Blizzard is working on it.

There is not yet a confirmed live fix.

Restarting the Game Does Not Reliably Fix It

Unfortunately, the usual first round of troubleshooting does not appear to help consistently.

Players have reported trying:

• logging out and back in
• completely restarting Diablo IV
• restarting Battle.net
• changing difficulty or Torment level
• returning to the physical Tree of Whispers
• using a Raven instead of the Tree
• leaving the area and returning
• turning cross-play off
• repairing the game installation
• in at least one case, completely reinstalling the game

The reward screen remained empty for many of them.

There are isolated reports of relogging helping earlier instances of the problem, but the current wave appears considerably more persistent. One player specifically noted that an earlier occurrence could be cleared by logging out, while later attempts became completely stuck.

That makes this different from several of the Warlock quest problems we covered yesterday, where changing difficulty or disabling cross-play can sometimes push the quest state forward.

With Whispers, there is currently no broadly reliable community workaround.

The Physical Tree Does Not Save You

One obvious idea is that the new Season 15 Ravens might be the problem.

They are not a reliable escape route.

Players who encounter the blank reward screen at a Raven have traveled back to the Tree of Whispers itself and received the same empty interface. Others who first discovered the problem at the Tree tried Ravens afterward with identical results.

Blizzard's own acknowledgement specifically mentions both locations.

That strongly suggests the problem is connected to the Whisper reward state rather than one particular NPC interaction.

The messenger is not broken.

The message apparently arrived without the loot attached.

Season 15 Made Whispers Much More Valuable

The timing is particularly unfortunate because Season 15 just gave players several good reasons to care about Whispers again.

We covered the changes in our look at Season 15's major Torment, XP and cache buffs. Whisper rewards received some of the biggest improvements in the entire progression update.

Gold Caches now provide substantially more Gold, with Blizzard using Torment XII as an example where a cache rises from roughly 35 million to around 100 million Gold.

Gem Caches provide roughly twice as many fragments.

Cube Material Caches provide around two to three times as many materials.

Salvage Caches receive similar increases.

Key Caches provide twice as many random Tributes and five times as much Sigil Dust, while also gaining a small chance to contain rare access items connected to Mephisto and Echoing Hatred.

Whisper turn-ins also provide more Experience Orbs.

In other words, Blizzard spent part of Season 15 making the Tree worth visiting again.

The Tree has responded by refusing to open the box.

All Three Splinters of Evil Also Interact With Whispers

The bug cuts into the seasonal system itself too.

As we explained in our Diablo, Baal and Mephisto Splinter guide, all three Prime Evil paths modify the Tree of Whispers.

Diablo primarily changes Helltides and Infernal Hordes.

Baal focuses on The Undercity and Lair Bosses.

Mephisto changes The Pit and Nightmare Dungeons.

But Whispers are shared across all three.

That makes them one of Season 15's universal progression activities rather than something relevant only to one chosen Prime Evil.

A bug that blocks Whisper turn-ins therefore reaches across all three seasonal paths.

This Can Also Interfere With Seasonal Objectives

There is another consequence beyond losing caches and activity access.

Season 15 contains seasonal objectives involving Whisper progression and turn-ins. Players stuck at the reward screen are therefore not simply missing one ordinary endgame loop. They can also find themselves unable to complete related seasonal progression until the problem is resolved.

That becomes more annoying because Season 15's new Rank structure contains 125 objectives spread across nine ranks, with the later rewards including Skill Points, Paragon Points, Resplendent Sparks and Mythic caches.

Not every objective has to be completed.

But losing access to an entire category is still something most players would rather avoid.

The Bug Does Not Appear to Require Whisper Overflow

Some early discussion focused on players reaching values such as 11/10 or 13/10 Grim Favors.

That led to speculation that the normal overflow system itself might be causing the problem.

There is currently no solid evidence for that.

Players correctly pointed out that Grim Favor overflow has worked for multiple seasons. Going above 10/10 is not inherently unusual.

More importantly, reports also exist from players who encountered the empty reward screen on what they described as their first normal 10-Favor turn-in.

So while overflow may be visible once the bug occurs, we should not confuse correlation with a confirmed trigger.

Blizzard has not published the root cause.

It Is Happening Across Different Difficulties

The reports also span a wide range of difficulty levels.

Players have reproduced the issue in normal leveling content as well as Torment difficulties ranging into the upper endgame.

One report came from a Torment VI Rogue.

Another from a Torment X character sitting at 11/10 Favors.

Console players have reported the same blank reward window on lower difficulty characters.

Several users specifically tried moving between Torment levels to force the reward list to refresh.

It did not reliably help.

That makes a difficulty-specific reward table failure look less likely from the outside, although only Blizzard can confirm the actual cause.

This Is Not the Same Problem as Solo Self Found

Because Blizzard mentioned the Whisper issue in the same broader communication surrounding Solo Self Found, some players initially assumed the two problems were connected.

Blizzard explicitly described the Whisper problem as a separate issue.

The current Tree problem affects the normal game too. Players in ordinary Seasonal play have reported it across PC and consoles.

SSF remains its own Season 15 problem.

Whispers have simply decided the week needed another one.

Do Not Waste Resources Trying to Reinstall Everything

For players already stuck, the practical advice right now is unpleasantly simple.

Wait for Blizzard's fix.

You can certainly try a relog or restart. They are quick and harmless.

But repeated difficulty swapping, traveling between every Raven in Sanctuary or reinstalling the entire game does not have a demonstrated success rate high enough to justify treating any of those steps as a solution.

One player reported repairing the installation and then performing a full reinstall without changing the result.

That is a great deal of data transfer to rediscover that the Tree still has no prizes.

Other Endgame Activities Still Work

The bug blocks Whisper progression on affected characters, but it does not mean the entire Season 15 endgame has stopped functioning.

Players can still run Helltides, Nightmare Dungeons, The Pit, Lair Bosses, Infernal Hordes, Waking Nightmares and the season's other systems.

The problem is that some of those activities normally overlap beautifully with Whispers.

You kill what you were already going to kill.

You collect Grim Favors in the background.

You eventually cash everything in at the Tree.

When that final step breaks, one of Diablo IV's cleanest multi-purpose progression loops becomes dead weight.

This Is Exactly the Kind of Bug Season 15 Did Not Need

Season of Hell's Legacy has had a rough opening.

Launch-day login problems became serious enough that Season 15 itself had to be temporarily delayed.

Players then reported old Paragon, Gold and materials appearing on fresh seasonal characters.

Solo Self Found remained unavailable.

Warlock class quests began getting stuck.

Old Eternal Mythics ran into new Crafted restrictions.

And now one of the game's oldest endgame systems can simply stop paying out.

That does not make Season 15 a bad season. Underneath the technical problems, the actual content contains some excellent ideas, including the hidden Diablo II Runewords players discovered inside the Horadric Cube.

But the first few days have asked for a remarkable amount of patience.

Blizzard Says a Fix Is Being Worked On

The most important thing now is that Blizzard has acknowledged the issue quickly.

The team says it is continuing to investigate and is aiming to have a fix ready soon, although timing remains subject to change.

Until that fix lands, affected characters may remain unable to turn in their completed Grim Favors or begin another proper Whisper cycle.

So if your Choose Your Reward screen contains absolutely no rewards, you are not missing a hidden button.

You are not at the wrong Raven.

You did not anger the Tree by choosing Mephisto.

And reinstalling Diablo IV probably will not convince it to negotiate.

The Tree of Whispers currently has exactly one thing to offer some players.

Silence.

Read More

Diablo 4 Players Are Still Getting Stuck at War Plans Rank 9/10

Diablo IV's War Plans are supposed to reward players for mastering the game's endgame activities. Complete Pit runs, Helltides, Nightmare Dungeons, Infernal Hordes, Lair Bosses, Kurast Undercity and Whispers, gradually improve the individual activity trees and eventually finish the entire system. For some players, however, the final step has become impossible. They have every activity marked 7/7 and Completed, yet the overall War Plans progression remains permanently stuck at Rank 9/10 with 7/8 Activity Skill Points.

The problem has now been reported repeatedly across Season 14, with similar complaints stretching back into Season 13. Restarting the game does not appear to solve it. Completing more War Plans after every activity is already maxed does not reliably solve it. Some players have spent huge amounts of Gold refunding and reallocating their War Plan points without success. The especially frustrating part is that the UI itself provides no remaining objective to complete. The game says everything is finished on one side of the screen while simultaneously insisting that one more point exists somewhere in Sanctuary.

Every Activity Can Be 7/7 While War Plans Still Says 9/10

The clearest reports all describe almost exactly the same state. Every War Plan activity tree displays its green completion mark and the maximum 7/7 progression, but the main War Plans rank remains at 9/10. The rank-up requirement shows 7/8 Activity Skill Points, leaving the player one point short with no unfinished activity available to provide it.

One July bug report lists Whispers, Nightmare Dungeons, Helltides, Undercity, Lair Bosses, Infernal Hordes and The Pit as fully completed. The player continued running additional War Plans and logged out and back in, but the missing point never appeared. Another player reported reaching the same state after weeks of progression and spending roughly a billion Gold experimenting with refunds and point redistribution. Others have confirmed that refunding the activity trees does not repair the missing rank.

This is not simply players misunderstanding that War Plans begins at Rank 0. Other characters and players have demonstrably reached 10/10, and the stuck accounts continue displaying an explicit requirement for an eighth point. The system itself believes another rank exists. It simply has no remaining progression available to award it.

Players Think Double-Ranking an Activity May Be the Trigger

The most interesting community theory is that the bug may happen before the player reaches Rank 9. Several affected players suspect that completing enough activity XP to gain two activity ranks during the same turn-in can cause one of those ranks to fail to count toward the overall War Plans total. Everything appears normal at the time because the individual activity progresses correctly. The problem only becomes visible weeks later, when every tree reaches 7/7 and the overall counter is still missing one point.

One player who encountered the issue described it as a likely calculation error when a double activity rank occurs close to an overall War Plans rank-up. Another specifically remembered taking their final two activities to 7/7 during the same turn-in and wondered whether that was the moment the progression broke. A June report suggested something similar could happen when multiple Nightmare or Helltide objectives rank simultaneously.

None of that has been confirmed by Blizzard, so it remains a reproduction theory rather than an established technical explanation. But it would explain why the problem is so difficult to detect early. The player does not necessarily do anything unusual or receive an error message. One counter quietly fails to increment, and the consequences only become obvious when there are no more ranks left to earn.

The Bug Is Especially Cruel Because War Plans Take Time to Finish

This is not an objective players accidentally complete during their first evening in Torment. War Plans were introduced with Lord of Hatred as one of Diablo IV's major permanent endgame systems, allowing players to construct activity chains and gradually specialize the individual activities through their own progression trees. Blizzard later expanded the system in Season 14 with party synchronization, additional Helltide and Nightmare Escalation options, improved Infernal Horde progression and better XP scaling at high Torment levels.

That means reaching the final War Plans ranks can represent weeks of normal endgame play. Several affected players explicitly describe spending weeks maxing every activity only to discover the final rank is mathematically unavailable. One Hardcore player says they finally completed all of their War Plans after struggling across two seasons, only to land at 7/8 and 9/10 again.

The system already has a broader friction problem for players who enjoy creating multiple characters. We previously looked at the debate over whether War Plans progression should be shared more broadly across alts, because repeating a large endgame progression tree on multiple characters can feel more administrative than meaningful. Losing the final rank because one hidden counter failed somewhere along the way makes that grind considerably harder to defend.

There Does Not Appear to Be a Reliable Workaround

The forum reports are full of the usual troubleshooting attempts. Restart Diablo IV. Restart Battle.net. Verify files. Relog. Complete more activities. Refund the War Plan tree. Reassign all the points. Run several additional plans after reaching 7/7 everywhere. None has emerged as a reliable fix.

One player considered deleting and restoring the affected character in the hope that the progression state might recalculate, then quite sensibly decided that experimenting with character deletion was perhaps a little ambitious for an endgame UI bug. Another spent 50 million Gold per refund attempt before discovering that moving points around does not magically manufacture the missing activity rank.

That leaves affected players in an awkward state where continuing to play the relevant activities produces XP and loot but cannot apparently repair the actual progression counter. Once every activity is maxed, there is nowhere else for the missing point to come from unless Blizzard corrects the stored value or provides another way to trigger it.

This Looks More Serious Than a Cosmetic UI Error

There is always a possibility with progression bugs that the underlying account has actually completed the requirement and only the interface is displaying the wrong number. The reports here suggest something more substantial. Players say they cannot complete the final War Plans rank or access the progression associated with reaching it, and some specifically mention failing to receive the expected completion state even though every activity is marked finished.

That makes the bug materially different from seeing 9/10 while everything behind the scenes works correctly. If the missing counter prevents the rank-up itself, the player has genuinely lost progression rather than merely suffering an ugly number on the screen.

Diablo IV has already dealt with another awkward final-rank progression issue this season. Players continued reporting problems with Rank IX seasonal rewards failing to unlock correctly even after Blizzard patched related objective-tracking problems. The War Plans bug is technically separate, but the experience is painfully similar: complete what the UI asks for, then discover that one internal counter has a different opinion.

Reports Go Back Months

The current War Plans complaint is not one isolated August thread. One detailed bug report dates to May 19, when a player had every activity at 7/7 but remained at 9/10 overall. Additional reports appeared throughout June and July, including players on different regions and platforms. By mid-July, one larger thread contained multiple affected Barbarians and at least one console player reporting the same 7/8 state.

Another August thread was created specifically because affected players felt earlier reports had not received a public Blizzard response. Its author says the problem has been reported multiple times and asks less for an immediate fix than for confirmation that Blizzard is aware of it. That thread resurfaced among the active Diablo IV bug reports again on August 29.

Blizzard's recent patch notes include several War Plans improvements, including synchronized party boards and revised activity XP, but the published fixes do not currently identify a correction for characters stuck at Rank 9/10. That does not prove Blizzard is not investigating it internally. It does mean affected players still have no documented fix to point toward.

The Suspected Cause Would Explain Why Some Characters Are Fine

Not everyone gets stuck. Many players reach Rank 10 normally, which makes the bug frustratingly inconsistent. If the community's double-rank theory is correct, that inconsistency makes sense. The problem would depend on exactly how activity progression was awarded during one particular completion rather than something universal about War Plans.

There are also reports of different characters on the same account behaving differently. One player said their Barbarian was affected while their Warlock was not. That makes a purely account-wide failure less likely and suggests the corrupted progression value may sit on the individual character's War Plans state.

Again, that is inference from community reproduction attempts, not a Blizzard diagnosis. But it gives affected players at least one useful warning while the bug remains unresolved: if an activity gains multiple ranks at once, it may be worth checking whether the overall War Plans counter increases by the expected amount. Discovering the mismatch early probably does not fix it, but at least you know when Sanctuary lost the paperwork.

Season 14 Actually Made War Plans More Important

The timing is unfortunate because Blizzard has spent Season 14 making War Plans easier to use rather than moving away from the system. Patch 3.1 added party synchronization so a group can generate a shared board with synchronized objectives and progression. Activity XP scaling was increased at Torment VIII and above, Infernal Hordes received better base XP, and Blizzard added additional War Plan options for longer Helltides and Nightmare Dungeon Escalation Sigils.

Those are sensible improvements to a system intended to become part of Diablo IV's permanent endgame. War Plans are not a temporary seasonal gimmick scheduled to disappear in several weeks. That makes a persistent progression-blocking bug more important than a minor issue inside content that is about to rotate out.

If Blizzard wants players to think of War Plans as their customizable endgame framework, the framework needs to trust its own arithmetic.

A Recalculation Button Could Provide a Safety Net

Even if Blizzard finds the underlying trigger, there is a second problem: already affected characters need a way back. Preventing future double-rank miscounts would not automatically restore the point that existing characters never received.

The cleanest solution may be a server-side recalculation. The game already knows the current rank of every individual activity. If all seven relevant trees are complete, the overall War Plans rank should be derivable from those completed states rather than relying exclusively on a historical counter that may have missed an increment months earlier.

That kind of validation could also protect the system from similar problems in future patches. When the player logs in, resets a board or reaches a major progression milestone, Diablo IV could compare the expected overall rank with the actual stored value and repair obvious mismatches.

At minimum, customer support or an automated tool needs some way to award the missing state without asking players to create another character and repeat weeks of endgame progression. “Do everything again and hope the counter notices this time” is not much of a troubleshooting strategy.

War Plans Have a Simple Math Problem With a Very Expensive Answer

The strange part is how uncomplicated the bug looks from the player's side. Every activity says 7/7. Every tree says Completed. The overall system says 7/8.

Somewhere between those numbers, Diablo IV has misplaced one point.

For the game, that may represent an obscure state-management problem involving simultaneous progression events, character data and activity counters. For the player, it represents several weeks of grinding ending one square before the finish line.

That is why the War Plans 9/10 bug deserves more attention than its small UI counter suggests. Endgame progression only works when players trust that completing the requirement will actually complete the requirement. If one activity rank can silently disappear and only reveal itself after there is nothing left to level, players cannot realistically protect themselves from it.

They can keep playing.

They can refund the points.

They can spend another 50 million Gold.

They can restart the game.

But seven out of eight remains seven out of eight.

And when every available activity already says seven out of seven, that eighth point is going to need some help from Blizzard.

Sources

Diablo IV Forums: War Plans Progression Bug Still Unresolved After Multiple Reports

Diablo IV Forums: War Plans Stuck at Rank 9/10 With 7/8 Activity Skill Points

Diablo IV Forums: War Plans Still Stuck at 9/10

Blizzard: Diablo IV Patch Notes and Season 14 War Plans Updates

Blizzard: War Plans Endgame System Overview

```

Read More

Diablo 4 Says These Eternal Characters Are in Endgame — But War Plans Are Still Locked

Diablo 4 has found an impressively philosophical way to define the word “Endgame.”

Some Eternal characters are being displayed as Lord of Hatred (Endgame) on the Character Select screen.

There is just one problem.

They still cannot access parts of the endgame.

Players have been reporting the issue since shortly after Lord of Hatred launched, with older Eternal characters sometimes failing to inherit the correct campaign-completion state even after Lord of Hatred has been completed elsewhere on the account.

In one particularly clear example, a player says their Eternal characters have already skipped the campaign and Character Select explicitly shows them as being in Lord of Hatred's Endgame state.

Yet War Plans are unavailable.

Tyrael is missing from the War Plans table in Temis.

Several waypoints remain locked.

Endgame, apparently, is now more of a state of mind.

The Character Select Screen Says Everything Is Fine

The current problem is closely related to the Eternal campaign skip problem we recently covered, but this particular version is even stranger.

The affected characters are not simply being told to complete the campaign again.

According to the player report, Diablo 4 already recognizes them as being in:

Lord of Hatred (Endgame)

That should be the destination.

Blizzard's own Lord of Hatred documentation describes “Story Complete: Endgame” as the option available after completing the expansion campaign. Once unlocked, existing characters can also skip the campaign from Character Select instead of replaying the story.

The problem is that the label and the actual character state do not always appear to agree.

War Plans Simply Aren’t There

The most obvious symptom is War Plans.

War Plans are one of Lord of Hatred's central endgame systems. Once properly unlocked, players travel to Temis, use the Command Table and build chains of activities including Nightmare Dungeons, Helltides, Infernal Hordes, the Pit, Undercity and boss content.

For the affected Eternal characters, that onboarding appears to be missing.

The player says Tyrael is not standing beside the War Plans table.

The table is effectively dead.

That creates a particularly nasty progression problem because War Plans are not just another optional side activity. They feed directly into Diablo 4's current endgame structure and Activity Trees.

And even when War Plans do unlock correctly, they have their own problems. We recently covered players completing every activity only to find their War Plan progression stuck at 9/10.

Some players cannot finish the board.

Others apparently cannot get the board in the first place.

Efficiency.

The Horadric Cube Has Been Caught in Similar Progression Problems

This is not the first time old Eternal characters have struggled to inherit Lord of Hatred unlocks correctly.

Back in May, players reported completing Lord of Hatred on one character and then discovering that older level 60 Eternal characters still could not use the campaign skip.

One PlayStation player specifically said they had completed Lord of Hatred on an Eternal Sorcerer but could not skip the campaign on two other Eternal characters.

The reason they cared was simple:

They wanted access to the Horadric Cube and War Plans without replaying the entire expansion campaign.

Another player in the same discussion reported that some Eternal characters received the Character Select campaign-sync option while others did not, despite all of them predating Lord of Hatred and being the same level.

That suggests this is not simply someone missing an obvious quest marker.

Finishing Lord of Hatred Is Supposed to Unlock the Skip

Blizzard's intended behavior is fairly clear.

Once Lord of Hatred has been completed, players can create a character using the Story Complete: Endgame starting state.

Blizzard also specifically says that previously created characters can skip the campaign directly from Character Select.

That matters because the affected characters are doing exactly what Blizzard's interface tells them to do.

The campaign is marked as skipped.

The game calls them Endgame characters.

And yet the world state appears to remain partially trapped somewhere before that point.

This Looks Like a Character-State Problem

Blizzard has not publicly confirmed the precise cause, so anything beyond the visible symptoms remains speculation.

But the reports look remarkably like Diablo 4 is failing to synchronize several different progression flags.

One flag tells Character Select:

This character is in Endgame.

Another apparently tells Temis:

Absolutely not.

That would also explain why players report a mixture of symptoms rather than one simple missing button.

Some cannot select the campaign skip.

Some can select it but still lack War Plans.

Some find waypoints locked.

Some do not see the expected endgame NPCs.

And some Eternal characters on the same account apparently work perfectly normally.

The Latest Patch Notes Don’t Mention a Fix

Diablo 4's latest listed live patch is 3.1.3 from August 12.

It includes several War Plans fixes, including a problem where teleporting to Infernal Hordes could fail on lower difficulties.

But Blizzard's patch notes do not mention repairing campaign-state synchronization for older Eternal characters.

That is important because these reports have now survived well beyond the immediate Lord of Hatred launch period.

This is not simply expansion-launch confusion from the first afternoon.

Players were reporting campaign-skip problems in May.

The “Endgame but no War Plans” report arrived in July.

And there is still no specifically documented fix in the current live notes.

Eternal Characters Are Exactly Where This Should Work Best

There is an extra irony here.

Eternal Realm exists partly so players can keep old characters alive indefinitely.

These are the characters people have spent seasons building, adjusting and preserving.

They are precisely the characters most likely to predate Lord of Hatred.

Forcing those characters into broken or inconsistent progression states defeats much of the point.

It is also why this problem is more serious than a missing quest icon.

Lord of Hatred made the Horadric Cube and War Plans fundamental parts of Diablo 4's modern endgame. If an old character cannot correctly transition into that state, a substantial portion of the expansion effectively disappears.

For Now, “Endgame” Doesn’t Necessarily Mean Endgame

There are community-suggested workarounds floating around, including changing difficulty, relogging and looking for missing onboarding quests.

We would not treat any of those as a confirmed fix.

The underlying issue appears inconsistent between characters, and Blizzard has not published an official workaround for this particular progression state.

So the safest description remains straightforward:

Some Diablo 4 Eternal characters are being marked as Lord of Hatred (Endgame) while still missing the systems that designation is supposed to unlock.

When the game's own Character Select screen says you have reached the endgame, expecting to find the endgame seems reasonably fair.

Sanctuary apparently requires additional paperwork.

Sources

Diablo IV Forums: Eternal characters with no War Plan

Diablo IV Forums: Can't skip campaign after completion

Blizzard: Prepare for the Reckoning — Lord of Hatred Draws Near

Blizzard: Diablo IV Patch Notes

Read More

Diablo 4 Players Are Finishing Their Entire War Plan — Then Getting Stuck at 9/10

Diablo 4's War Plans are supposed to reward you for completing endgame activities.

Some players have discovered a slightly less satisfying final objective.

Finish everything.

Then stare at 9/10 forever.

A long-running Diablo IV bug report describes War Plans becoming permanently stuck one level short of completion even after every available activity on the board has been maxed out.

The problem was first reported in June and is still receiving fresh reports on August 19.

For affected players, the missing rank means they cannot unlock the final War Plan reward despite apparently having nothing left to complete.

Every Activity Is Finished, But the War Plan Still Wants One More

The original report came from a Barbarian player on the Asia servers.

They completed every activity shown on the right side of the War Plan tree.

The activities were done.

The points were spent.

But the overall War Plan remained at Rank 9/10.

The interface still said another activity or skill point was required to reach the final rank.

There was only one minor problem.

There were no activities left.

The player tried restarting Diablo 4, restarting Battle.net, verifying the game files and logging out and back in.

Nothing changed.

Yes, War Plans Really Can Reach 10/10

One of the first questions in the bug thread was whether 9/10 might simply be the intended maximum because War Plans begin at Rank 0.

Other players quickly ruled that out.

War Plans can reach 10/10, and the UI continues showing unfinished progression after Rank 9 for affected players.

Later reports are even more explicit.

One player finished the entire War Plan and received the associated completion achievement, but the board itself remained at 9/10.

Another reported every activity sitting at 7/7 while the War Plan remained one rank short.

Achievement complete.

Activities complete.

War Plan apparently unconvinced.

Players Think Double Rank-Ups May Be Losing a Point

The most interesting community theory appeared after players began comparing how their War Plans progressed.

Several suspect the bug happens when an activity gains two ranks at once around the same time the overall War Plan should gain a level.

One player suggested that doing two Nightmare Dungeon Escalations or two Greater Helltide upgrades together may cause the system to count only one of the activity ranks.

A later player described what appears to be the same problem in more detail.

According to their testing, if an activity double-ranks while the War Plan itself is close to leveling, one activity rank may fail to count toward the overall total.

Nothing looks obviously broken at the time.

The problem only becomes unavoidable weeks later, when every activity is maxed and the missing point can no longer be earned.

That explanation has not been confirmed by Blizzard.

But it would explain why the bug feels like it appears at the end even though the actual mistake may have happened much earlier.

Another Theory Points to the First Activity Rank

There is not complete agreement on the cause.

Another player testing a fresh character noticed that the first rank gained in one activity tree appeared not to contribute an expected point.

So the community currently has at least two possible explanations:

• A double activity rank-up causes one point to be skipped.
• An early activity rank sometimes fails to count correctly.

Neither theory has received official confirmation.

What players do agree on is the outcome.

Eventually the board reaches a state where everything is finished but the numbers no longer add up.

The Bug Is Still Happening on August 19

The original thread did not disappear after June.

Players reported the same problem throughout July and August.

On August 3, one player said they had finally maxed their War Plan after several weeks of progression and ended up permanently one point short.

More reports followed on August 11.

And early on August 19, another Barbarian player confirmed the same issue again.

Interestingly, that player said their Warlock did not have the problem.

They wondered whether the difference might relate to one character starting Seasonal while the Barbarian began on Eternal.

That is only speculation, but it adds another variable worth investigating.

War Plans Have Already Needed Plenty of Fixes

This is not Diablo 4's first argument with the War Plan system.

Blizzard has already fixed multiple problems involving War Plan progression, boss spawns, activity tracking and rewards since Lord of Hatred launched.

We previously covered an Infernal Hordes War Plan bug that could completely block progression, which Blizzard later addressed.

We have also been following the Ultimate Nemesis party loot problem, where groups report completing the final encounter only for some players to receive no proper reward.

Blizzard's official patch notes include numerous War Plan fixes, from Nemesis Lairs failing to trigger to activity icons displaying incorrectly and campaign states being evaluated inconsistently between party members.

The system is clearly complicated.

Unfortunately, Rank 9 apparently still knows how to count to ten about as well as a Fallen.

This Is Another Progression Bug With No Way Forward

The reason this one matters is not simply that the UI displays the wrong number.

The final rewards remain locked.

There is no additional activity to grind.

Reassigning points reportedly does not solve it.

Restarting does not solve it.

And because every activity is already at maximum rank, the player has no obvious way to generate another progression event and force the missing point to appear.

That puts it in the same unpleasant category as several progression issues we have covered recently.

Some Eternal characters still cannot access the campaign skip they should have unlocked.

Players can become soft-locked during the Secret Cow Level quest despite completing the required steps.

And even 65/65 Skovos exploration can leave the Amazonian Charge mount locked for some accounts.

The common theme is particularly frustrating:

The player has already done the work.

The game just has not finished counting it.

Blizzard Has Not Announced a Specific Fix Yet

Blizzard's current patch notes contain plenty of War Plan fixes, but we have not found a published correction specifically addressing the 9/10 progression issue.

The main bug thread is also still active today.

That does not mean Blizzard is not investigating it.

Bug reports can be tracked internally without receiving a public developer response.

But from the player's perspective, there is currently no confirmed fix or reliable workaround.

Weeks of Grinding Should Probably Add Up to Ten

War Plans were introduced with Lord of Hatred as a way to give Diablo 4's endgame more structure, allowing players to customize and progress through chains of activities after finishing the expansion campaign.

That structure only works if the progression system remembers all the progression.

Players reporting this bug are not asking for free levels.

They are not asking Blizzard to reduce the grind.

They have already finished the grind.

They would simply like:

Seven out of seven.

Plus seven out of seven.

Plus everything else completed.

To eventually equal ten out of ten.

Sanctuary has more complicated mathematics than that.

This should not be one of them.

Sources

Diablo IV Forums: War Plans Level Stuck at 9/10 — Missing Skill Point After Completing All Activities

Blizzard Entertainment: Prepare for the Reckoning — Lord of Hatred Draws Near

Blizzard Entertainment: Diablo IV Patch Notes

Read More

Diablo 4’s War Plans Can Trap Leveling Characters Outside Infernal Hordes

Diablo 4’s War Plans are supposed to guide players through a sequence of endgame activities.

Unfortunately, some leveling characters are being assigned an activity they cannot actually enter.

Players report receiving Infernal Hordes objectives before reaching Torment difficulty, leaving the War Plan stuck behind content that remains unavailable.

The plan has been generated.

The portal has not.

Sanctuary has apparently discovered the traditional workplace problem of assigning tasks without providing access.

War Plans Can Select Infernal Hordes Too Early

War Plans create a route through activities such as Nightmare Dungeons, Helltides, The Pit, Kurast Undercity and Infernal Hordes.

Completing each activity advances the board toward its final rewards.

The problem appears when a low-level character receives Infernal Hordes before the activity is properly available.

Players can see the objective on the War Plan.

They may also see the button intended to teleport them directly into the activity.

Pressing it does not reliably open the encounter.

The character remains outside.

The War Plan remains deeply impressed with its own scheduling.

The Character May Need To Reach Torment First

Several player reports connect the problem to characters leveling below Torment difficulty.

Infernal Hordes are not normally available through the same progression route at those lower difficulties.

This means the War Plan can demand an activity before the character satisfies the conditions needed to start it.

The player cannot complete the objective.

They also cannot simply move to the next node.

War Plans require the listed activities to be completed in sequence.

One impossible objective can therefore block the entire board.

Re-Rolling Is Not Always Available

War Plans can be reset or rerolled, but that requires the appropriate currency or remaining reroll attempts.

A player who has already spent those options may have no immediate way to remove the Infernal Hordes objective.

They are left with two unattractive choices.

Continue leveling until Torment becomes available.

Or abandon War Plan progression on that character for the time being.

The feature designed to structure leveling instead becomes something waiting at the end of leveling.

Similar Access Problems Have Appeared Before

This is not the first time players have reported War Plans selecting inaccessible content.

Earlier party-synchronisation reports described lower-level characters receiving Pit objectives despite not meeting the required level.

Other players have encountered Infernal Hordes teleport buttons that highlight the activity without actually moving the character.

Some War Plans have also failed to recognise completed activities, leaving boards stuck even after the required dungeon or boss was cleared.

The individual causes may differ.

The shared problem is that War Plans do not always verify whether a character can start and complete the activity being assigned.

Patch 3.1.2 Fixed A Different Infernal Hordes Problem

Patch 3.1.2 corrected an issue where the Whisper icon could obscure the option used to teleport into Infernal Hordes.

That fix may help players whose destination was available but hidden behind the interface.

It does not appear to solve War Plans assigning Infernal Hordes to characters below the required progression threshold.

Blizzard’s current patch notes do not list a fix that prevents inaccessible activities from being selected for low-level War Plans.

The button is easier to see.

The destination may still reject the applicant.

A New Character May Provide Emergency Rerolls

Some players have reported a strange workaround for stuck War Plans.

They created a new level-one character, completed a full War Plan on that character and then received additional reset opportunities that could be used on the affected main character.

This is a player-discovered workaround rather than an official solution.

It may not work for every account or every version of the bug.

It also asks the player to complete another War Plan in order to repair the first War Plan.

Diablo 4 has turned troubleshooting into repeatable content.

Reaching Torment Can Also Clear The Block

For characters already close to the necessary progression, the simplest workaround may be to ignore the board temporarily and continue leveling.

Once the character reaches Torment and can access Infernal Hordes normally, the objective may become completable.

This does not make the original assignment reasonable.

War Plans are available while players are still developing their characters.

The activities selected should match the character’s current level, difficulty and unlocked content.

A plan should describe what the player can do now.

Not what they might become qualified to do after several more hours.

Hardcore Characters Can Be Hit Especially Hard

Hardcore players often level more carefully and may remain below Torment longer while improving equipment and survivability.

A War Plan locked behind Infernal Hordes can therefore remain unusable for an extended period.

Starting another character to generate reset currency is also a larger commitment when every character carries permanent death risk.

The bug does not directly kill the character.

It simply removes a progression system until the player agrees to meet its unexplained promotion requirements.

War Plans Need Eligibility Checks

The clean solution is straightforward.

Before generating a board, Diablo 4 should check the character’s level, difficulty and unlocked activities.

Infernal Hordes should not appear unless the character can actually enter them.

The Pit should not be assigned before the required level.

Expansion activities should not appear for players who cannot access them.

If a character loses access after a board is generated, the affected node should receive a free automatic reroll.

The system already knows what content exists.

It also needs to know whether the person receiving the assignment is allowed through the door.

Every Board Should Have A Free Escape Route

War Plans would also benefit from one guaranteed free reset whenever progression becomes impossible.

This could activate if the same objective remains incomplete for an extended period or if the game detects that its requirements cannot be met.

Players should not need spare currency to escape a board created by faulty eligibility logic.

Reroll costs make sense when someone simply dislikes the selected activity.

They make less sense when the activity cannot be launched.

The Plan Should Never Be Harder Than The Activity

War Plans are one of Diablo 4’s useful progression systems when the board works correctly.

They encourage variety, connect activities and provide clear short-term goals.

That structure collapses when the next objective exists behind a difficulty wall.

Blizzard needs to prevent inaccessible activities from appearing, provide automatic recovery for impossible nodes and make rerolls available when the system fails.

Leveling characters already have monsters, gear checks and difficulty transitions to manage.

They should not also be trapped by a planner that scheduled Infernal Hordes before the venue opened.

For more coverage of War Plans, progression bugs and Diablo 4’s current endgame systems, visit our Diablo 4 archive.

Sources

• Diablo IV Forums: War Plan stuck on an inaccessible Infernal Hordes objective
• Diablo IV Forums: War Plans assigning inaccessible activities to lower-level characters
• Diablo IV Forums: Season 14 War Plan progression reports and player workaround
• Blizzard: Current Diablo IV patch notes

```

Read More

Diablo 4’s Cosmic Archives Could Break If You Skipped An Objective

Diablo 4 rewards players for moving quickly.

Strong builds delete enemies, mobility skills skip empty corridors and experienced players learn to ignore anything that looks optional.

Cosmic Archives Stronghold apparently had a different philosophy.

Before Patch 3.1.2, skipping an objective could prevent the Stronghold from progressing entirely.

The player moved ahead.

The quest script remained behind, quietly holding the keys.

Skipping An Objective Could Block The Stronghold

Blizzard confirmed the progression problem in the Patch 3.1.2 notes released on July 28, 2026.

The developer says an issue could prevent progress in Cosmic Archives Stronghold when the player skipped an objective.

The patch note does not specify exactly which objective caused the failure or how players were able to bypass it.

However, the result was serious.

Once the expected step had been missed, later parts of the Stronghold could stop activating correctly.

Enemies might be dead.

The route forward might be clear.

The objective tracker could still refuse to acknowledge that the adventure had continued without written permission.

Archivist Rhene Could Cause A Separate Softlock

Patch 3.1.2 also fixed another Cosmic Archives progression problem involving Archivist Rhene.

If players did not interact with Rhene at the expected time, the Stronghold could become blocked.

That suggests the encounter relied on a narrow sequence of scripted triggers.

The player needed to reach a particular point, speak with the correct character and complete events in the intended order.

Missing one interaction could leave the later objectives waiting for a flag that had never been activated.

Rhene was not merely an archivist.

Rhene was apparently the entire Stronghold’s power switch.

Fast Builds Can Outrun Fragile Quest Scripts

Modern Diablo 4 characters can cross areas and destroy enemy groups extremely quickly.

Movement abilities allow players to leap, teleport or charge past parts of an encounter before every objective has updated.

Large damage bursts can also remove required enemies before dialogue, animations or quest markers have finished appearing.

That creates a recurring conflict between character power and scripted content.

The game encourages efficiency.

The quest quietly expects everyone to walk behind the tour guide.

This Was Not Cosmic Archives’ First Progression Problem

Blizzard had already repaired two other Cosmic Archives softlocks in Patch 3.0.4.

Progression could previously become blocked when enemies were killed too far away from the location where the encounter began.

The Stronghold could also break when a player left and did not return for an extended period.

Combined with the new fixes, Cosmic Archives has now struggled with:

• Objectives being skipped.
• Archivist Rhene being ignored at the wrong time.
• Enemies dying too far from their expected location.
• Players leaving the Stronghold for too long.

The archive contained ancient knowledge.

Unfortunately, several pages of its instruction manual were missing.

Softlocks Are Worse Than Ordinary Combat Bugs

A broken damage bonus may reduce a build’s performance.

A visual bug may make an effect difficult to see.

A progression softlock can stop the player from completing the activity at all.

Once Cosmic Archives entered a broken state, players could be forced to leave, reset the Stronghold and repeat completed sections.

There was no reward for diagnosing the exact objective the script had missed.

The player simply lost time because the encounter could no longer reach its next state.

The Game Needs Better Objective Failsafes

A Stronghold should regularly check whether the conditions for its next stage have already been met.

If a player reaches a later area without completing an earlier interaction, the game could reactivate that objective or direct the player back toward it.

If the required enemies are already dead, the objective should complete automatically.

If Archivist Rhene needs to be contacted, the NPC should remain available and clearly marked until the interaction occurs.

The encounter should recover from unexpected player behaviour instead of becoming permanently confused by it.

Objectives Should Not Depend On Perfect Timing

Dialogue and scripted interactions can help Strongholds feel more like story events than ordinary dungeons.

They should not create one narrow moment where progression is allowed to continue.

If a player misses an interaction because enemies are attacking, another party member moves ahead or the marker appears too late, the opportunity should remain available.

Required steps need persistent triggers.

The game should recognise what still needs to happen and offer another chance to make it happen.

A missed conversation should not condemn the entire Stronghold to administrative limbo.

Party Play Can Make These Problems Harder To Avoid

Multiplayer groups rarely move through content in perfect formation.

One player may speak with an NPC while another enters the next area.

A fast character may kill an enemy before slower party members reach the encounter.

Someone may teleport away to clear inventory and return after the objective state has changed.

Strongholds must account for every eligible player and synchronise progression across the group.

A script designed around one careful solo player can quickly collapse when four people treat the area like a race.

Patch 3.1.2 Should Make The Stronghold More Reliable

Both newly documented Cosmic Archives fixes are now live on PC, Xbox and PlayStation.

Players should be able to progress even when an objective is skipped.

Failing to interact with Archivist Rhene at one exact moment should also no longer block the Stronghold.

Blizzard did not provide a detailed explanation of how the recovery system now works.

The important result is that the encounter should stop demanding one flawless sequence from every player.

Powerful Players Should Not Need To Pretend They Are Slow

Diablo 4 is built around making characters faster and stronger.

Players should not need to reduce damage, avoid mobility skills or wait beside every NPC because the quest might collapse if they move too efficiently.

Cosmic Archives has now received several repairs aimed at making its progression more resilient.

That is good.

The Stronghold should respond to what the player has accomplished, not punish them for accomplishing it in the wrong order.

Sanctuary already has demons, corruption and cosmic horrors.

It does not also need unskippable bureaucracy.

For more coverage of Stronghold bugs, progression problems and Diablo 4’s latest fixes, visit our Diablo 4 archive.

Sources

• Blizzard: Diablo IV Patch 3.1.2 notes
• Blizzard: Earlier Cosmic Archives progression fixes in Patch 3.0.4

```

Read More

Diablo 4’s Soul Eater Could Freeze And Stop The Entire Dungeon

Freezing enemies is generally considered useful in Diablo 4.

They stop moving.

They stop attacking.

And, until Patch 3.1.2, one particular frozen enemy could apparently convince the entire dungeon to stop working as well.

Blizzard has fixed an issue where killing the Soul Eater while it was frozen could prevent additional monsters from spawning inside a Deathtoll Chamber.

The crowd control was so effective that it reached the encounter script.

Killing The Soul Eater While Frozen Could Break Progression

The Soul Eater appears during Deathtoll Chamber encounters in Diablo 4’s Season of Death Awakening.

Players are expected to defeat it while clearing waves of enemies and completing the chamber’s objectives.

Before the latest fix, killing the Soul Eater during a Frozen state could stop the remaining monsters from appearing.

Without those enemies, the player could no longer progress through the encounter normally.

The Soul Eater was dead.

The next wave had apparently called in sick.

Cold Builds Were Punished For Working Correctly

The bug was particularly awkward because Frozen is not some obscure exploit.

Several builds regularly apply Chill and Frozen through ordinary skills, equipment and seasonal bonuses.

A player could therefore trigger the problem simply by using their build exactly as intended.

There was no obvious warning that the Soul Eater needed to die at room temperature.

The encounter only revealed the hidden rule after the next group of monsters failed to arrive.

The Chamber Could Also Complete Too Early

Patch 3.1.2 fixed a second issue involving the same encounter.

Blizzard says the Deathtoll Chamber could sometimes be marked as completed before the Soul Eater had actually been slain.

That created the opposite problem.

One bug prevented the dungeon from progressing after the Soul Eater died.

Another could declare victory while it was still alive.

The chamber was struggling with the basic administrative question of whether its boss existed.

A Broken Spawn Can Waste The Entire Run

When a required monster wave does not appear, players have few useful options.

They can search the arena for enemies hiding outside the objective zone.

They can wait and hope the script catches up.

They can leave the dungeon and lose the progress already made.

Restarting the activity may solve the immediate problem, but it does not return the time spent reaching the broken encounter.

Deathtoll Chambers have already received previous fixes for blocked exits, missing rewards and incorrect teleportation.

The seasonal activity has been collecting technical problems almost as efficiently as players collect keys.

The Fix Is Now Live On All Platforms

Blizzard included both Soul Eater corrections in Patch 3.1.2, released for PC, Xbox and PlayStation on July 28, 2026.

Players should now be able to kill the enemy while it is Frozen without preventing later monsters from spawning.

The chamber should also wait until the Soul Eater is genuinely dead before announcing completion.

That sounds like a low bar.

Diablo 4’s dungeon scripts have occasionally treated low bars as aspirational goals.

Frozen Enemies Should Not Freeze The Event

Diablo 4 encourages players to combine crowd control, burst damage and status effects.

Encounter scripts need to survive those systems regardless of how quickly or dramatically an enemy dies.

A required death trigger should fire whether the target is burning, poisoned, stunned, frozen or reduced to mist by one oversized critical hit.

Patch 3.1.2 appears to have repaired this particular failure.

Players can once again freeze the Soul Eater without also freezing the entire dungeon’s work schedule.

For more coverage of seasonal bugs, dungeon problems and Diablo 4’s latest fixes, visit our Diablo 4 archive.

Sources

• Blizzard: Diablo IV Patch 3.1.2 notes

```

Read More

Diablo 4’s War Plans Can Ignore Completed Escalation Dungeons

Diablo 4’s War Plans are supposed to guide players through a chain of endgame activities.

Apparently, completing those activities is only a suggestion.

Players continue to report that the “Conquer Escalation Dungeon” objective can remain incomplete even after they activate an Escalation, clear every floor and defeat the final boss.

The dungeon acknowledges the victory.

The loot appears.

The War Plan table responds with the administrative equivalent of “never happened.”

The Latest Player Has Been Stuck For Weeks

A new report was posted on Diablo 4’s official PC Bug Report forum on July 28, 2026.

The player says their War Plan requires them to activate an Escalation Dungeon.

They have completed multiple Escalations and killed the associated bosses, but the objective refuses to advance.

The problem has reportedly lasted several weeks.

That means this is not one dungeon taking a few seconds to update.

The player has repeated the required activity several times and received the same result.

War Plans have successfully created a long-term plan.

It consists entirely of doing the same thing while the game denies receiving it.

Another Player Cleared All Three Floors And Astaroth

A more detailed report from July describes the same basic failure.

The affected player selected “Conquer Escalation Dungeon” in the War Plan system, activated an Escalation Sigil and completed all three dungeon floors.

They defeated Astaroth and collected the boss loot.

Instead of receiving War Plan completion, the player was removed from the boss room while some items reportedly remained on the floor.

The portals closed.

The activity remained incomplete.

The player then tried two different approaches.

They entered using an Escalation Sigil manually from the map.

They also used the War Plan teleport option to ensure the correct objective was active.

Neither method worked.

The game had several opportunities to recognise the victory.

It remained committed to the bit.

War Plans Depend On Activities Registering Correctly

War Plans allow players to arrange several endgame activities into a connected route.

Completing one node advances the plan toward the next objective and its eventual rewards.

This structure only works when every activity reports completion reliably.

A broken node does not merely withhold one checkmark.

It can block the entire chain behind it.

The player may have other activities prepared, but the War Plan cannot reach them because the current Escalation objective remains active.

One failed completion signal turns the planning table into expensive furniture.

Escalation Dungeons Are Not Cheap Little Objectives

An Escalation Dungeon is more demanding than completing one ordinary event.

Players move through multiple connected Nightmare Dungeon floors with increasing difficulty and rewards.

They must clear objectives, defeat bosses and continue through portals toward the final stage.

A full successful run represents a meaningful investment of time.

Depending on how the activity was started, it may also consume an Escalation Sigil or another limited opportunity.

When the War Plan fails to register that run, the player cannot simply click a nearby chest and try again immediately.

They must repeat a multi-floor endgame activity and hope the database develops object permanence.

The Final Boss Can Die Without Completing The Objective

The clearest sign of a broken progression trigger is that the final boss can be defeated normally.

Astaroth dies.

The loot drops.

The dungeon reaches its ending.

The War Plan still does not advance.

This suggests that ordinary dungeon completion and War Plan completion are handled by separate systems.

The Escalation knows that the player won.

The War Plan may be waiting for a different trigger that never arrives.

That trigger could be tied to the entry method, final portal, boss-room state or completion event.

Whatever the cause, the player has already completed the only part they can reasonably control.

Using The War Plan Teleport Does Not Always Help

One obvious troubleshooting step is launching the activity directly through the War Plan interface.

That should ensure the correct objective is selected and tracked before the dungeon begins.

The detailed report says this did not solve the problem.

The player used the War Plan teleport and completed the Escalation again.

The objective remained unchanged.

This matters because it weakens the idea that players are simply entering the wrong type of dungeon.

The game itself sends them to the activity.

The game itself then refuses to accept the completed assignment.

Manual Escalation Sigils Can Also Fail

Entering through a manually activated Escalation Sigil reportedly produced the same result.

This means both obvious routes can fail.

The player cannot reliably bypass the problem by choosing a different entrance.

War Plan objectives should ideally recognise any qualifying Escalation completion while the node is active.

Whether the player entered through the table, map or inventory should not change whether Astaroth counts as dead.

The boss is unlikely to care which menu opened the dungeon.

Earlier Reports Show Several Related Failures

The current bug sits inside a wider collection of Escalation and War Plan problems.

Players have reported Escalation Dungeons failing to open the portal to the next stage when a Nightmare Dungeon War Plan is active.

In those cases, the current dungeon can show as completed while the War Plan remains unfinished and the next Escalation floor never appears.

Other reports describe progression breaking after an Escalation run becomes stuck and the player restarts the game.

Later War Plan activities can then stop registering as well.

The exact symptoms vary.

The common theme is that Escalation state and War Plan state can disagree about what the player has completed.

Restarting The Game May Temporarily Help Some Players

One earlier discussion includes a player who says fully restarting Diablo 4 temporarily restored the expected behaviour.

That suggests stale session data may contribute to at least some versions of the problem.

A complete restart is therefore worth attempting before consuming another Escalation opportunity.

Players should close the game entirely rather than relying on suspended sessions or Quick Resume.

This is not a confirmed universal fix.

The newest player has reportedly been stuck for weeks and completed numerous dungeons without success.

Turning the game off and on remains the ancient ritual of technical support.

It should not be the most advanced tool available for repairing seasonal progression.

Starting Another War Plan May Reset The State

Players may also be able to abandon or replace the current War Plan and create a new route.

Doing so could force the system to rebuild the active objective state.

This carries obvious drawbacks.

The player may lose progress already made through the current plan.

The desired rewards or activity sequence may disappear.

There is also no guarantee the new Escalation node will behave differently.

Resetting the plan is therefore less a solution and more a controlled demolition of the existing problem.

The Bug Can Waste Escalation Sigils

Escalation Sigils provide access to one of Diablo 4’s longer dungeon chains.

Using one for a War Plan objective creates a reasonable expectation that a successful clear will count.

If the objective fails, the Sigil has still been consumed.

The player loses the key, the time and the progression.

They may receive ordinary dungeon loot, but the specific reason for launching the run remains unresolved.

Diablo’s loot can be random.

Whether a completed objective counts should not join the same system.

Some War Plans Should Launch Escalations Without A Key

Players have also debated whether a War Plan Escalation objective should require an Escalation Sigil at all.

The War Plan interface can provide a teleport directly into the required content.

Some players report that this route launches an Escalating Nightmare without consuming a separate key.

Others have become stuck because they believed the plan required a Sigil they did not possess.

The interface needs to make the rule explicit.

If the War Plan supplies the activity, the player should not need to guess whether another item is required.

If a key is required, the plan should provide a reliable way to earn one.

The current system asks players to solve the entry requirements before discovering that completion may not count anyway.

Escalation Portals Have Their Own History Of Disappearing

War Plan progression is not the only fragile part of Escalation Dungeons.

Players have reported the portal to the next floor failing to appear after a boss dies.

Others have been thrown into the open world or an unfinished Stronghold instead of continuing the Escalation.

Returning to town can sometimes reset the dungeon into an ordinary Nightmare Dungeon and erase the remaining Escalation stages.

These failures can prevent players from reaching the final boss required by the War Plan.

The new reports go one step further.

Even reaching and defeating that boss may not be enough.

Unfinished Strongholds Can Break Escalation Runs

Several older reports identify unfinished Strongholds as another source of Escalation trouble.

If a dungeon selected for a later Escalation stage belongs to a Stronghold the player has not completed, the game can reportedly remove the player from the run after a boss dies.

The next portal does not appear.

The Escalation ends.

Players preparing to troubleshoot the War Plan objective should therefore clear their remaining Strongholds first.

This may reduce the risk of an unrelated failure before the final stage.

It does not repair the completion-registration bug itself.

It simply removes one additional trap from a dungeon system already carrying several.

War Plan Objectives Need To Track The Final Boss Kill

The most reliable completion trigger should be simple.

If the relevant War Plan node is active and the player defeats the final boss of a valid Escalation Dungeon, the objective should complete.

The system should not depend on which button opened the activity.

It should not require the player to stand in the boss room for a hidden amount of time.

It should not fail because loot remains on the floor or a portal closes early.

Astaroth’s death is a clear, verifiable event.

Use it.

The System Should Validate Completion More Than Once

Blizzard could add several checks to prevent the objective from being lost.

The first check could occur when the final boss dies.

Another could run when the reward chest or loot event appears.

A third could verify completion when the player leaves the final floor.

If any one of those confirms a successful Escalation, the War Plan should advance.

Essential progression should not depend on one fragile message being delivered during a chaotic boss-room transition.

The game can afford to ask more than once whether the enormous demon is still alive.

Completed Escalations Should Be Recorded On The Account

Diablo 4 could also store recent Escalation completions independently from the War Plan.

If the node fails to update immediately, the table could check the account’s activity history when reopened.

A qualifying completion performed while the objective was active would then receive credit retroactively.

This would protect players from disconnects, delayed server responses and broken boss-room transitions.

The game already records loot, achievements and many other activity results.

War Plans should not develop amnesia the moment the player approaches the table.

Failed Recognition Should Refund The Activity

If Blizzard cannot reliably award retroactive completion, it should at least refund the Escalation opportunity.

A player who clears all three stages and receives no War Plan progress could receive a replacement Sigil automatically.

The game might also preserve the active node while granting partial plan experience.

This would not make the bug acceptable.

It would prevent a technical failure from consuming every part of the player’s investment.

The Escalation was completed.

The refund should not require the player to prove it through a forum thread several weeks later.

The War Plan Interface Needs A Progress Log

A visible activity log would make these failures easier to understand.

The table could show:

• The active objective.
• The activity entered.
• The Escalation tier.
• The highest floor completed.
• The final boss result.
• The reason credit was or was not granted.

This would help players identify whether they launched the wrong activity or encountered a bug.

It would also provide Blizzard with clearer evidence.

At the moment, players can defeat Astaroth and receive nothing but a node that still looks disappointed in them.

Partial Escalation Clears Should Be Explained Clearly

Some confusion may come from what “Conquer Escalation Dungeon” actually requires.

Does the objective demand all three floors?

Does completing one stage count?

Must the final boss be defeated through a War Plan-generated Escalation rather than a normal Sigil?

The wording should state the exact requirement.

The reports discussed here include players who completed all three floors and the final boss, so unclear wording does not explain every failure.

Better wording would still remove ambiguity from legitimate unsuccessful attempts.

War Plans Already Require Significant Experience

Advancing the War Plan table can require substantial activity experience.

Every broken objective therefore delays access to later nodes and rewards.

The player is not merely missing one completion bonus.

They may be unable to unlock modifiers designed to improve other endgame activities.

A stalled Escalation objective can hold an entire seasonal progression system hostage.

The table is supposed to reward planning.

It currently rewards avoiding whichever node may stop counting.

Group Play Could Create Additional State Problems

Party members may not always share identical War Plan objectives.

One player may have “Conquer Escalation Dungeon” active while another launched the Sigil.

The system then needs to determine which accounts receive credit.

Players should receive completion if they participated in the full qualifying activity while the node was active.

Credit should not depend solely on who opened the dungeon or who landed the final hit.

The current reports do not clearly establish whether party ownership contributes to the bug.

Blizzard should test host, guest and mixed-objective groups separately.

Solo Players Are Reporting The Failure Too

The detailed July report does not rely on a complicated party scenario.

The player used the War Plan teleport and completed the activity directly.

This indicates that group synchronisation cannot explain every case.

The core completion trigger itself appears capable of failing.

That makes the issue harder to dismiss as ordinary multiplayer confusion.

The player followed the table, entered the dungeon, cleared every floor and killed the boss.

There are not many additional instructions left to obey.

Patch 3.1.2 Does Not List A Fix

Blizzard released Patch 3.1.2 on July 28 with several important bug fixes.

The notes address Rogue damage, Mythic recycling and other gameplay problems.

They do not list a specific fix for Escalation Dungeon completions failing to advance War Plans.

The new report was posted the same day, suggesting that the issue may remain active under the latest version.

Blizzard could already be investigating without having acknowledged it publicly.

For affected players, the result remains unchanged.

The current patch can recycle a Mythic.

It may still struggle to recycle a completed dungeon into one checkmark.

Players Can Try A Few Workarounds

There is currently no confirmed universal solution.

Affected players can still try several lower-risk steps before consuming another Escalation opportunity.

Fully restart Diablo 4.

Confirm the correct War Plan node is active.

Use the War Plan teleport rather than manually opening an unrelated dungeon.

Complete unfinished Strongholds to reduce the risk of later Escalation stages breaking.

Avoid returning to town during the Escalation.

Complete every floor and remain in the final room until all loot and completion messages appear.

These steps may help avoid related bugs.

They cannot guarantee that the War Plan will recognise the result.

Record The Entire Final Floor

Players experiencing the bug should capture video beginning before the final boss dies.

The recording should show the active War Plan objective, Escalation tier, boss kill, loot and unchanged table afterward.

Include whether the dungeon was launched through the War Plan teleport or a Sigil.

Platform, class, party status and completed Strongholds may also be relevant.

A report containing the full sequence gives Blizzard more useful evidence than a screenshot of the unfinished node alone.

The table may deny the clear.

The recording does not need to participate in the denial.

Blizzard Should Grant Retroactive Credit

The strongest solution is retroactive validation.

Players who completed a qualifying Escalation while the War Plan objective was active should receive credit automatically.

Blizzard’s logs may contain the final boss kill, dungeon tier and completion timestamp.

If those records can be matched with the active node, affected accounts should not need to repeat the activity.

This is especially important for players who have remained stuck for weeks.

Their problem is not a shortage of effort.

It is that the system keeps rejecting completed work.

War Plans Need To Trust The Dungeon

Escalation Dungeons already know when their bosses die and their floors are complete.

War Plans should use that information reliably.

The current reports describe players completing every visible requirement and receiving no progression.

That can waste Sigils, block later nodes and leave an entire seasonal system unusable.

Blizzard needs to strengthen the completion trigger, add retroactive checks and refund activities when recognition fails.

Players are willing to plan their route through Sanctuary.

They should not need to schedule the same Escalation every evening until the table finally believes them.

For more coverage of War Plans, Escalation Dungeons and Diablo 4’s current progression bugs, visit our Diablo 4 archive.

Sources

• Diablo IV Forums: Player reports War Plan failing to advance after repeated Escalation clears
• Diablo IV Forums: All three Escalation floors and Astaroth completed without War Plan credit
• Diablo IV Forums: Escalation portals and War Plan completion failing together
• Diablo IV Forums: Wider War Plan progression failure after an Escalation bug
• Blizzard: Current Diablo IV patch notes

```

Read More

One Diablo 4 Monster Stuck In A Wall Can Delete An Entire Escalation Run

Diablo 4’s Escalation Dungeons are filled with demons, elites and increasingly dangerous objectives.

None of them are as powerful as one ordinary monster standing slightly inside a wall.

Players continue to report that “Slay All Enemies” objectives can become impossible when a single creature spawns behind a locked door, inside the scenery or somewhere attacks cannot reliably reach.

The dungeon does not care that every other enemy is dead.

The door remains locked.

The objective remains incomplete.

The entire Escalation run can be lost because one demon has discovered architecture.

The Latest Report Arrived On July 27

A player added a new report to Diablo 4’s official bug forum on July 27, 2026.

The problem appeared near the beginning of an Escalation Dungeon and affected the player’s only available run.

The player recorded video evidence on Steam Deck in case it could help Blizzard investigate.

This was not the first report in the thread.

Other players have described monsters becoming trapped during the third and final stage of Escalation Dungeons, where abandoning the objective means losing all the time invested in the earlier levels.

The latest report confirms that the bug is still capable of ending runs almost a year after the discussion began.

“Slay All Enemies” Leaves No Alternative

Many dungeon objectives offer some flexibility.

A player may need to activate objects, defeat specific elites or collect items scattered across the map.

“Slay All Enemies” is less negotiable.

Every monster attached to the objective must die before the game opens the path forward.

If the counter believes one enemy remains, the dungeon stops.

The player cannot skip the creature.

They cannot open the locked door.

They cannot convince the objective that 99 out of 100 demons represents a strong performance.

One inaccessible monster has complete veto power over progression.

Enemies Can Spawn Behind Doors That Require Their Death

One player described reaching the third stage of an Escalation Dungeon and finding exactly one enemy trapped behind a closed door.

The door would only open after every enemy had been defeated.

The enemy required for that condition was standing on the other side.

This creates a perfect Diablo deadlock.

Kill the monster to open the door.

Open the door to reach the monster.

The player receives no third option beyond abandoning the run.

The demon has not defeated the character through combat.

It has defeated the quest logic through superior positioning.

Walls And Rocky Maps Make The Bug More Common

Players in the discussion say the problem appears more frequently in crowded or irregular dungeon layouts.

Rocky terrain, narrow corridors and complicated “spaghetti” maps can push enemies into unusual locations.

Dense groups may also interfere with spawn positions or movement.

Seasonal portals and additional enemy spawns could increase the risk by placing creatures in areas not designed for normal objective monsters.

One report suggests that portal mechanics may move an enemy’s spawn point into a wall.

The exact cause has not been confirmed.

The repeated result is familiar.

The minimap shows one final enemy.

The player reaches the marker.

The wall proudly claims custody.

Area Damage Can Sometimes Reach The Monster

Some affected players have escaped the bug by using attacks that pass through walls or automatically seek enemies.

Large area-of-effect skills may damage a creature positioned close enough to the accessible side of the scenery.

Minions or projectiles with unusual targeting behaviour can occasionally find the trapped enemy.

This is not a reliable solution.

The required skill may not be part of the player’s build.

Some monsters spawn too far inside the geometry to be reached at all.

Locked doors can also block attacks more effectively than thin walls.

A dungeon objective should not require the player to carry an emergency wall-penetration build.

Escalation Dungeons Make The Failure More Expensive

A broken ordinary Nightmare Dungeon wastes one Sigil and part of a run.

A broken Escalation Dungeon can waste several connected stages.

Players progress through increasingly difficult levels, collecting rewards and working toward the final encounter.

Reaching stage three represents a larger investment than entering a single dungeon.

If the final objective becomes impossible, the earlier progress cannot compensate for losing the completion.

The player may have already defeated multiple bosses and cleared hundreds of enemies.

One trapped creature can invalidate the entire chain.

Escalation has achieved its name.

The frustration increases with every floor.

The Bug Can Consume A Player’s Only Available Run

Escalation access is not always unlimited.

Players may have only one relevant Sigil or reward available at that moment.

The July 27 report specifically mentions that the failed Escalation Dungeon was the player’s only one.

That means the bug does not merely delay progression by a few minutes.

It can remove access to the activity until another key or opportunity appears.

The game asks the player to earn entry.

The dungeon then assigns progression authority to a monster embedded in masonry.

This Problem Reportedly Dates Back To Beta

Players in the forum thread describe “Slay All Enemies” failures as an old Diablo 4 problem.

The original poster argued in August 2025 that the bug had existed since beta.

Later reports continued through October 2025, February 2026, July 4 and July 27.

That does not prove every occurrence has the same technical cause.

Enemies can become inaccessible through several different spawn, movement or door failures.

The objective-level result has remained unchanged.

One living enemy prevents completion.

After several years, the monster may now qualify for permanent residency.

The Objective Needs A Failsafe

Blizzard may not be able to prevent every creature from entering invalid geometry.

Procedurally assembled dungeons, dense combat and large numbers of movement effects create many opportunities for unusual positioning.

The objective still needs protection against those failures.

If an enemy remains unreachable for a certain period, the game could move it to a valid location.

If relocation fails, the creature could be killed automatically or removed from the objective counter.

The system should verify that every required enemy can be reached.

Players should not lose an entire dungeon because the navigation mesh and the quest tracker stopped speaking.

Teleporting The Last Enemy Would Be The Cleanest Fix

Diablo 4 already uses mechanics that move enemies toward players during some “Slay All” objectives.

When only a small number of monsters remain, the dungeon can bring them closer to reduce backtracking.

That system could become a stronger failsafe.

If the final enemy has not moved or taken damage for several seconds, it could teleport directly into the player’s room.

The game would preserve the requirement to kill every monster without leaving progression dependent on a broken spawn location.

The demon would receive a brief relocation.

The player would receive the dungeon they already earned.

Removing The Enemy From The Counter Could Also Work

If an enemy is located outside the accessible dungeon boundaries, Diablo 4 could simply stop counting it.

The objective system should know which rooms are currently reachable.

A required monster behind a permanently locked door or inside invalid geometry should fail that validation.

The dungeon could mark it as defeated for objective purposes while leaving the actual creature untouched.

This may sound generous.

The player has already defeated everything the game allowed them to fight.

The wall should not receive a vote.

The Dungeon Could Open Doors When One Enemy Remains

Locked-door deadlocks need a separate safeguard.

If only one enemy remains and it is located behind a progression door, that door should open automatically.

The player could then enter and finish the objective normally.

This would preserve the fight rather than deleting the monster.

It would also address cases where the enemy is standing in a valid room that became inaccessible because the door logic triggered too early.

The game currently demands the enemy’s death as the price of entry.

It can temporarily accept the player’s promise to handle it.

“Slay All Enemies” Could Be Removed From Escalation Dungeons

Several players have suggested a more direct solution.

Disable “Slay All Enemies” inside Escalation Dungeons until the spawning problem is reliably fixed.

Other objectives may still bug, but they are less vulnerable to one inaccessible ordinary monster.

Blizzard could use elite-kill requirements, progress bars or structure-based objectives instead.

A percentage-based kill meter would allow the dungeon to tolerate one misplaced creature without making the objective meaningless.

Escalation runs are too expensive to depend on perfect placement of every goatman in the building.

A Percentage Requirement Would Be More Forgiving

The objective could require players to kill 95% or 98% of the dungeon’s enemies.

That would preserve the intended full-clear experience while protecting against rare spawn failures.

The remaining percentage could account for enemies trapped inside walls, left behind inaccessible doors or generated by optional mechanics.

Players would still need to search most of the dungeon.

They would not need to conduct an archaeological excavation for one red dot.

Absolute objectives work only when the spawning system is absolutely reliable.

Players Need A Manual Reset Option

Diablo 4 could also provide a “Reset Remaining Enemies” command after an objective has stalled.

The option might appear only when one or two monsters remain and no objective progress has occurred for several minutes.

Using it could respawn those enemies near the player.

This would prevent abuse while offering a way to rescue broken runs.

The command would not grant free completion.

It would simply place the required combat somewhere combat can happen.

At present, the available reset option is abandoning everything.

The Enemy Marker Can Make The Failure More Annoying

In many cases, the minimap clearly shows the location of the missing monster.

The player knows exactly where the enemy is.

They can stand beside the wall, attack it and watch the marker remain safely on the other side.

This removes any mystery while preserving all of the frustration.

The player is not failing to explore the dungeon.

The game is openly displaying the creature that prevents completion and refusing to provide access.

The minimap becomes a diagram of why the evening has ended.

Backtracking Does Not Always Solve It

“Slay All Enemies” objectives sometimes teleport remaining monsters toward the player after enough of the dungeon has been cleared.

Players may therefore backtrack through every room hoping to trigger the relocation.

This can work when an enemy was merely overlooked.

It often fails when the creature is trapped behind a door or inside the environment.

The player can spend several additional minutes walking through an empty dungeon before accepting that the objective cannot be completed.

The run is already broken.

It demands a farewell tour before admitting it.

Leaving And Returning Usually Risks The Instance

Players may attempt to teleport to town and return, hoping the dungeon reloads the enemy correctly.

That approach is risky.

Changing zones can reset parts of an activity, remove access or create other progression issues.

There is no confirmed guarantee that the trapped monster will move.

Escalation Dungeons involve connected stages, making any attempt to force an instance refresh especially dangerous.

The player can remain inside with a broken objective or leave and potentially lose the dungeon anyway.

Technical troubleshooting has become another dungeon modifier.

Party Members May Have Different Ways To Reach It

Grouped players may occasionally rescue a run if another class has a larger area attack, minions or a skill that reaches through the obstruction.

Party members can spread across the map and test whether approaching the enemy from another direction changes its position.

This still depends on luck and group composition.

Solo players have no backup toolset.

The dungeon objective should function for every legal build, not only parties carrying several varieties of architectural damage.

Hardcore Players Face Additional Risk

A stalled objective can also create danger for Hardcore characters.

Players may spend extra time searching through the dungeon, pulling additional enemies or attempting unusual movement tricks near inaccessible terrain.

Some may change skills or equipment while standing in an active area.

The original run is already lost if the enemy cannot be reached.

The search for a workaround can place the character at further risk.

Hardcore teaches players not to make desperate decisions.

A broken Escalation run is very good at encouraging them.

Mobility Skills Should Not Push Enemies Into Invalid Terrain

The underlying issue may sometimes involve knockback, pulls or rapid movement.

Enemy abilities and player skills can move creatures across the battlefield.

The game should prevent those movements from crossing into invalid geometry.

If an enemy reaches a location outside the navigation area, it should immediately return to the nearest valid point.

This protection would help with objectives, loot drops and monsters that continue attacking from inside scenery.

A demon may be supernatural.

Its collision detection should remain mortal.

Portal Spawns Need Additional Validation

Seasonal portals and reinforcement mechanics deserve particular attention.

New enemies can appear after the dungeon layout has already been generated and progression doors have been placed.

The spawn system needs to confirm that the selected location is reachable from the player’s current area.

It should also avoid placing objective monsters in rooms that have already become locked.

Random spawns add variety.

Randomly assigning the final required enemy to a private room adds something else.

Blizzard Should Preserve Escalation Progress After A Failed Objective

If an Escalation Dungeon becomes impossible, the game could preserve the player’s completed stages.

The player might receive a replacement Sigil beginning at the failed tier or a partial refund of the entry material.

This would not make the bug acceptable.

It would reduce the damage caused by it.

A player who completed two stages should not lose every part of the reward because stage three generated an inaccessible creature.

The dungeon failed validation.

The player did not fail the dungeon.

Video Evidence Could Help Identify The Trigger

The newest player says they recorded the incident on Steam Deck.

Video evidence can show the dungeon layout, remaining-enemy marker, objective state and exact location of the trapped creature.

Affected players should include their class, skills, Escalation tier and any portals or seasonal events active near the spawn.

Details about whether the monster was created normally or moved into the wall during combat may help separate different causes.

“Enemy stuck” describes the result.

Blizzard needs enough evidence to learn how the monster achieved home ownership.

The Current Reports Do Not Confirm A Universal Bug

Not every Escalation Dungeon or “Slay All Enemies” objective will fail.

Many players complete them normally.

The reports describe a recurring but inconsistent problem tied to specific layouts and spawn conditions.

Blizzard has not publicly confirmed that every occurrence shares one cause.

The long history of reports still makes the objective’s lack of a failsafe difficult to defend.

Rare failures are enough to damage trust when they can erase a multi-stage run.

One Monster Should Not Control The Entire Dungeon

Diablo 4 can keep “Slay All Enemies” objectives.

It needs to recognise when the final enemy is impossible to slay.

Teleport trapped monsters toward the player.

Open deadlocked doors.

Remove unreachable enemies from the objective counter.

Or temporarily disable the objective inside Escalation Dungeons until those safeguards work.

Players are willing to defeat every monster the dungeon places in front of them.

They cannot defeat the one it placed inside the building.

For more coverage of Escalation Dungeons, endgame bugs and Diablo 4’s current progression problems, visit our Diablo 4 archive.

Sources

• Diablo IV Forums: Players report inaccessible enemies blocking Escalation Dungeons
• Blizzard: Current Diablo IV patch notes

```

Read More