Showing posts with label PC bug. Show all posts
Showing posts with label PC bug. Show all posts

Tuesday, 28 July 2026

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

```

Sunday, 26 July 2026

Diablo 4’s Invisible Ground Effects Are Turning Hardcore Into Russian Roulette


Diablo 4’s Hardcore mode is supposed to punish bad decisions.

Standing inside an elite explosion is usually one of them.

That principle becomes slightly less useful when the explosion is invisible.

A new player report claims that several important visual effects can suddenly disappear during gameplay, including damaging ground circles, elite death explosions, seasonal mechanics and experience orbs.

The missing effects reportedly remain invisible until the player logs out and returns.

For an ordinary character, that can mean an irritating death and a repair bill.

For Hardcore, it can mean losing an entire character to an attack the player was never given a chance to see.

Sanctuary has apparently introduced minesweeper with permadeath.

Several Types Of Effects Can Reportedly Disappear

The report was posted on Diablo 4’s official PC Bug Report forum on July 26, 2026.

The player described multiple effects disappearing over the previous few weeks.

The examples included fire explosions from elite monsters, seasonal circles, Dark Prison circles and experience orbs.

The player summarised the issue as ground effects, area-of-effect indicators and circles becoming invisible until the game is restarted.

That list covers both cosmetic information and effects directly connected to survival.

An invisible experience orb is inconvenient.

An invisible elite explosion is an assassination attempt by the graphics settings.

Elite Death Explosions Need Clear Warnings

Diablo 4 frequently places dangerous effects beneath enemies during chaotic fights.

Elite monsters can leave explosions, pools and other hazards behind when they die.

The player is expected to recognise the visual indicator and move away before the damage occurs.

This is a normal action RPG mechanic.

The attack can be extremely dangerous because it is telegraphed.

Remove the telegraph and the mechanic stops testing awareness.

The player may kill an elite, move toward the dropped loot and die to an explosion that exists only inside the game’s calculations.

From the player’s perspective, a safe piece of floor suddenly becomes lethal without warning.

That is not difficulty.

It is invisible paperwork from Hell.

Hardcore Players Cannot Simply Try Again

Hardcore changes the seriousness of every technical issue.

A normal character respawns after dying.

The player may lose time, durability and progress within the current activity.

A Hardcore character is permanently lost.

Equipment, Paragon progression and hours of character development can disappear because of one death.

Hardcore players accept that risk when the death results from combat, positioning or a bad decision.

They cannot reasonably prepare for an area-of-effect attack that the client has stopped displaying.

A character can have maximum resistances, defensive layers and a carefully planned escape route.

None of those systems teach the player where an invisible circle ends.

The Report Also Mentions Hardcore Streams

The forum report claims that similar disappearing effects have occurred during Wudijo’s Hardcore streams.

Wudijo is known for playing Diablo’s most difficult content and for approaching Hardcore with extensive preparation.

The forum post does not link a specific clip or timestamp, so that part of the report should be treated as the player’s observation rather than independent confirmation.

It still highlights why the issue deserves attention.

If experienced Hardcore players are encountering missing visual warnings, the problem cannot be dismissed as someone failing to recognise a mechanic.

Knowing exactly what should appear does not help when the game decides not to draw it.

Dark Prison Circles Are Particularly Dangerous

The player specifically mentioned Dark Prison circles among the missing effects.

These types of zones rely entirely on clear visual communication.

The player needs to know where the dangerous area begins, how large it is and which direction offers a safe exit.

When the circle disappears, the mechanic becomes guesswork.

A character may continue taking damage without any visible explanation.

The player can move randomly and hope to escape.

That approach is less effective when enemies, walls and other hazards already occupy the battlefield.

Hardcore combat should require quick decisions.

It should not require paranormal investigation.

Busy Encounters Make The Problem Harder To Identify

Diablo 4 battles can fill the screen with monsters, spell effects, damage numbers, summons and loot labels.

During that chaos, a player may not immediately realise that one category of effects has stopped appearing.

The first warning may be unexpected damage.

The player might assume an enemy projectile landed, resistance dropped or an unfamiliar modifier activated.

They may continue playing without knowing that other dangerous effects are also invisible.

This makes the problem more serious than one missing animation.

Once the visual state breaks, the player cannot know which future attacks will still be communicated correctly.

Every piece of empty ground becomes suspicious.

Relogging Is A Workaround, Not A Solution

According to the report, the missing effects return after relogging.

That suggests the issue may involve the client’s visual state rather than the underlying mechanics disappearing entirely.

The damaging effects continue working.

The game simply stops showing them.

Relogging may restore the visuals, but the player first needs to recognise that something is missing.

There is no warning stating that ground effects failed to load.

A Hardcore player may discover the problem through a fatal damage spike before receiving an opportunity to restart.

“Log out before the invisible explosion kills you” is useful only when the invisible explosion sends an appointment request.

Seasonal Circles Can Affect More Than Survival

Not every missing circle necessarily causes direct damage.

Seasonal mechanics may use visual zones to show objectives, safe areas or effect ranges.

If those indicators disappear, the player can lose progress even without dying.

They may stand outside an objective while believing they are inside it.

They may miss a reward trigger or fail to understand why a mechanic is not advancing.

Visual feedback is part of the rules.

When it disappears, the player is not merely losing presentation quality.

They are losing access to the information needed to participate in the activity correctly.

Missing Experience Orbs Suggest A Broader Rendering Failure

The inclusion of experience orbs is also interesting.

Experience orbs are not dangerous enemy attacks.

If they disappear alongside combat circles and explosions, the issue may affect a broader category of temporary world effects.

That could explain why several unrelated mechanics become invisible at the same time.

The forum report does not provide technical logs or reproduction steps, so the exact cause remains unknown.

It could involve long play sessions, specific activities, performance conditions or a particular graphics configuration.

What matters to the player is simpler.

Important objects remain active while becoming visually absent.

Blizzard Needs Reproduction Information

The current report does not identify a consistent trigger.

The player says the issue has happened repeatedly over several weeks but does not specify whether it begins after a particular dungeon, boss or graphics event.

That makes investigation more difficult.

Affected players can help by recording several details when it happens.

These include the activity being played, character class, graphics settings, session length and whether changing zones restores the missing effects.

Video evidence would be especially useful because it can show damage occurring without the expected visual warning.

Hardware information and graphics-driver versions may also help determine whether the bug is limited to certain configurations.

The fewer clues a hazard provides on the floor, the more clues Blizzard needs in the bug report.

The Game Should Detect Missing Critical Effects

Diablo 4 should treat major combat telegraphs as essential gameplay elements rather than optional visual decoration.

If a critical effect fails to render, the game could attempt to reload the associated visual assets automatically.

At minimum, important enemy attacks should have more than one warning method.

A ground circle could be supported by an audio cue.

An elite death explosion could use a clear sound and enemy status indicator.

Dangerous zones could receive stronger outlines that remain visible at lower effect settings.

Redundant communication would improve both reliability and accessibility.

The player should not need perfect particle rendering to understand that the ground is about to become hostile.

Accessibility Settings Could Offer A Temporary Safety Net

Blizzard could also expand accessibility options for dangerous ground effects.

Players could select a high-contrast outline for harmful zones.

Opacity and brightness controls could make telegraphs easier to distinguish from spell clutter.

An optional warning icon could appear when the character stands inside a lethal area.

These features would not fix effects that fail to render entirely.

A separate interface warning might still remain available even when the world animation disappears.

This would help players with visual impairments while providing a useful backup against rendering bugs.

It would also reduce the number of deaths caused by red circles placed on top of slightly different red floors.

Hardcore Needs Stronger Protection From Technical Deaths

Every online Hardcore game faces the same uncomfortable question.

What happens when a character dies because of a bug, disconnect or server problem?

Diablo 4 generally treats the death as permanent.

That prevents players from falsely claiming technical problems whenever a legitimate death occurs.

It also means genuine technical failures can permanently erase characters.

Invisible attacks fall directly into this problem.

Automatic character restoration would be difficult to administer fairly.

Blizzard still needs to prioritise bugs capable of causing unavoidable Hardcore deaths.

A missing cosmetic can wait for a routine patch.

A missing lethal telegraph should not.

An Emergency Hardcore Warning Would Help

If Blizzard confirms the issue before a fix is ready, the developer should warn Hardcore players directly.

A notice could explain the known symptoms and recommend relogging when any temporary effects disappear.

The game launcher, forum and in-game message system could all carry the warning.

This would not eliminate the risk.

It would help players recognise early signs such as invisible experience orbs before the missing effect becomes an elite explosion.

A harmless visual disappearance could act as the canary in Sanctuary’s coal mine.

When the experience orbs vanish, stop playing before the floor joins them.

Players Can Reduce The Risk For Now

Until Blizzard confirms the cause, players should pay attention to any missing temporary visuals.

If experience orbs, seasonal circles or familiar skill effects stop appearing, relogging immediately may restore the correct state.

Hardcore players should avoid continuing into high-level dungeons or boss encounters after noticing a missing effect.

Recording the incident can also help provide Blizzard with more detailed evidence.

Lowering graphics settings may be worth testing if the problem appears during visually intense encounters, although there is currently no confirmed evidence that this prevents it.

Players should not need to perform defensive graphics maintenance between demon fights.

For now, caution is better than donating another Hardcore character to an invisible puddle.

This Is Still An Unconfirmed Player Report

It is important to keep the scale of the evidence clear.

The current story begins with one new public bug report.

The thread had not yet collected a large number of independent confirmations when published.

Blizzard has not publicly acknowledged a widespread issue involving disappearing ground effects.

The report may represent a specific hardware problem, a limited client bug or a broader issue that other players have not yet documented.

That uncertainty does not make the symptoms harmless.

It means more reports and technical evidence are needed before the scope can be established.

The Current Patch Notes Do Not List A Specific Fix

Blizzard’s current Diablo 4 patch notes contain numerous fixes for visual, gameplay and stability problems.

They do not currently list a specific correction for damaging circles and other effects disappearing until relogging.

The issue may therefore remain active for affected players.

Blizzard could already be investigating it without having added anything publicly.

Until an acknowledgement appears, players should treat the forum report as an early warning rather than a confirmed universal bug.

For Hardcore characters, an early warning is still worth taking seriously.

Invisible Damage Is Not Legitimate Difficulty

Diablo 4 can be brutal.

Hardcore should be even more brutal.

Enemies can hit harder, bosses can punish mistakes and one poor decision can end a character permanently.

Those risks work only when the player receives the information needed to respond.

A visible explosion tests positioning.

An invisible explosion tests whether the rendering system currently likes you.

Blizzard needs to investigate why temporary effects can reportedly disappear and ensure that dangerous telegraphs remain visible throughout a session.

Hardcore players signed up to fight Hell.

They did not sign up to fight invisible circles with permanent consequences.

For more coverage of Hardcore deaths, visual bugs and Season 14 problems, visit our Diablo 4 archive.

Sources

```

Monday, 20 April 2026

 

Diablo 4’s bug boards are full of blunt, ugly headlines. Missing loot. Broken rewards. Pets that will not unlock. Then there is one of the stranger fresh entries in Blizzard’s latest PC bug listings: “Of pests and Pestilence.” That title sounds less like a technical report and more like somebody walked out of a plague-ridden side quest muttering at the sky. Which, in Diablo 4, is usually a sign that something specific and annoying went sideways.

The problem is that the public side of this one is still thin. Blizzard’s latest Diablo IV PC bug index shows “Of pests and Pestilence” as a fresh topic active on April 20, 2026, but the listing itself does not expose much more detail from the category page. That means nobody should pretend we have a fully documented breakdown of the issue yet. What we do have is a live current report attached to what sounds very much like a quest, event, or progression step that has gone rotten in some interesting way.

The title alone points toward a quest or objective problem

Even with limited public details, there is a grounded way to read this. “Of Pests and Pestilence” sounds like the name of a questline, objective, or event step rather than a random system bug. If that reading is right, then the likely category here is progression friction: an objective not updating, an enemy not counting, an interact point failing, or the game simply refusing to acknowledge that the player did the thing it asked for.

That matters because these are some of the most quietly infuriating Diablo 4 bugs. A flashy crash is obvious. A quest or objective that half-breaks is worse in a slower, nastier way. It leaves players stuck in the middle of content, wondering if they missed something, misunderstood something, or just got unlucky enough to hit one more rotten little seam in the game.

Diablo 4 already has a habit of making normal progression feel weirdly fragile

This fresh report also lands in a game that has already been collecting too many “basic loop broke again” stories. We recently covered how players said Ashava’s world boss cache gave no loot, how some monsters were allegedly becoming unkillable, and how wardrobe and transmog issues were still lingering. Different systems, same mood: Diablo 4 keeps producing little moments where players stop trusting whether a normal activity will actually behave normally.

That broader pattern is what gives even a vague report like this some editorial value. In a calmer week, a mysterious quest-sounding bug title might just sit there unnoticed. In Diablo 4’s current climate, it immediately reads like one more possible case of a supposedly simple piece of content turning into avoidable friction.

Thin details do not make it worthless, just early

To be fair, this is still an early watchlist story, not a slam-dunk confirmed outbreak. The public bug index shows the topic is live, but without a visible full write-up from the category page, the responsible read is that something tied to “Of Pests and Pestilence” appears to have gone wrong for at least one player, and the fuller nature of the issue may become clearer once the thread develops.

Sometimes that means the problem turns out to be tiny. Sometimes it becomes one of those quest bugs that keeps resurfacing for weeks because it blocks exactly the wrong piece of content. Right now, this one is interesting precisely because it sits in that uncomfortable middle ground.

For now, it is one to watch

Diablo 4 does not need every bug report to explode into a giant story for it to matter. Sometimes a weird title in the bug index is enough to flag where the next annoying little fire might start. And with a name like Of Pests and Pestilence, this one already sounds like it came preloaded with a bad attitude.

Wednesday, 15 April 2026

Diablo 4 on macOS via CrossOver Still Looks Broken After Season 12, and That Is a Pretty Miserable Place to Be

 


Diablo 4 has plenty of problems this season, but Mac players using CrossOver are dealing with a much meaner one than bad loot luck or another annoying UI gremlin. For some of them, the game simply launches into nothing. Battle.net says it is running, Activity Monitor shows the process chewing on CPU, and the actual game window never appears. That is not a rough session. That is a digital séance.

The core complaint is laid out in a still-active post on the official Diablo IV bug report forum, where a player says the issue started right after the Season 12 update. According to that report, the exact same CrossOver version, macOS version, and bottle setup had worked before patch 2.6.0, then suddenly stopped producing a visible game window after the update.

When “Running” does not mean running

That detail matters, because this does not sound like a vague compatibility complaint from someone trying to make unsupported hardware do circus tricks. The whole point of the bug report is that the setup was working, then Season 12 landed, and Diablo 4 basically turned into a ghost process. You click play, Battle.net insists everything is fine, and your desktop sits there like it has never heard of Sanctuary.

The issue also does not look buried. Blizzard’s latest Diablo IV PC bug listings still show the CrossOver Mac thread active on April 14, which is usually a decent sign that the problem has not simply evaporated. Over on the CodeWeavers support forums, players have been describing the same basic behavior: Diablo 4 says it is starting, then fails to open properly after the new season update.

There is at least one ugly workaround, and it is not exactly elegant

One particularly telling sign that this is not just user error is that some CrossOver users are already experimenting with ugly workaround territory. On the CodeWeavers compatibility forum, one player says they only got Diablo 4 to launch again by moving to a newer macOS beta and using a preview CrossOver build. That is less “fix” and more “ritual sacrifice with extra steps.”

For Mac players, that matters because CrossOver is already the compromise solution. People using it know they are not in the golden path Blizzard supports first. But there is still a big difference between “unsupported edge case” and “the game worked yesterday and now it opens into the void.” Season updates are supposed to break builds in-game, not erase the game window from reality.

The unsupported crowd still notices when things get worse

This is also one of those stories Blizzard can easily ignore because it sits in a niche lane. Diablo 4 on macOS through CrossOver is not the main player base. Nobody is pretending otherwise. But niche problems still matter when they are directly tied to a major patch and show up across both the official bug forum and the CrossOver community.

And honestly, Diablo 4 does not need more stories where players press play and get some fresh new variation of nothing. It already has enough of those.

Sunday, 5 April 2026

Diablo Immortal Players Say Repeated Crashes Are Still Wrecking Sessions

 


One of the most basic problems in any live-service game is still showing up the hard way

Diablo Immortal has a fresh crash complaint on the forums, and it is not the polite kind. A new April 5 General Discussion post says the player has been dealing with crashes for around two months, with the game closing completely while Battle.net stays open, sometimes in bursts of four to six crashes in a row before things calm down again for a while.

That alone would be enough for a service piece. What makes it more interesting is the effort the player says they already put in trying to fix it. According to the post, they reinstalled the game multiple times, checked GPU drivers, reinstalled Windows, and even tested the same Battle.net account on a different PC, only to see the same pattern there too. If that account is accurate, this stops looking like one cranky machine and starts looking a lot more like a deeper game-side or account-side problem.

What the player is actually reporting

The report says the crashes can happen across a wide spread of activities, including TR, dungeons, towers, vault, and more. The player also notes that there is no lag warning beforehand, no obvious slowdown, and no clear trigger beyond the fact that the crashes keep returning in clusters. That kind of randomness is part of what makes crash bugs so maddening. A performance problem you can reproduce is annoying. A performance problem that appears to roll dice first is much worse.

The same post adds a useful detail: the player says Blizzard support directed them to the forums and suggested a developer might need to look at it, with the player even wondering whether their character might be bugged. That is not proof of an account-specific issue, but it does show the complaint is not just “my PC is old, please help.” The player had already gone through the usual support loop before posting publicly.

Why this one is worth covering

This is not yet a giant multi-page meltdown thread, so it is fair to keep expectations in check. But it is fresh enough to matter. Blizzard’s Diablo Immortal forums show “Crash spamming me!” as an active April 5 discussion topic, and the general forum page places it among the latest live threads right now. That gives it enough immediacy to count as current bug chatter rather than some dead complaint from weeks ago.

It also lands in a broader environment where Diablo Immortal’s bug-report board is still active with multiple current technical and gameplay complaints, including interaction bugs, server-load issues, tracker problems, and update-related glitches. That does not prove all of those are connected to this crash issue, but it does reinforce that the game is not exactly having a quiet, spotless technical week.

A crash bug does not need to be flashy to be destructive

That is probably the cleanest angle here. Diablo Immortal can survive a weird tooltip, a messy tracker, or one confused event toggle. Repeated hard crashes are different. If players are getting dumped out of the game four to six times in a row across multiple activities, the real problem is not class balance or event timing. It is whether the session can stay alive long enough to matter. And that is a much uglier story than most patch-note bugs ever become.