Diablo 4’s Wendigo Brand Is Still Trying to Kill Its Owner Months Later

Diablo IV contains plenty of items designed to help monsters kill you. Wendigo Brand is slightly more ambitious. Players have been reporting for more than four months that the Unique can drain enormous chunks of their Current Life when its Maximum Life stacks expire, effectively turning a defensive bonus into something that occasionally attempts to finish the job itself.

The problem was first documented at the end of April. Blizzard acknowledged the reports in July and said the team was investigating. Players then reproduced the same behaviour on the Season 15 PTR in August.

And on September 7, a new PlayStation 5 report appeared describing precisely the same symptom again.

At this point, Wendigo Brand's most impressive Unique power may be persistence.

Wendigo Brand Is Supposed to Reward Constant Killing

On paper, Wendigo Brand is an interesting all-class Unique Ring.

Its power tracks how many enemies you have killed within a recent time window. For every 15 kills, the ring increases your damage dealt by 2% and your Maximum Health by 1%. Keep murdering enemies quickly and both bonuses continue increasing.

It is exactly the sort of Diablo item that rewards momentum. Helltides, Infernal Hordes and dense dungeon content can build the effect rapidly, giving an aggressive character more damage while simultaneously increasing its health pool.

The problem begins when those temporary Maximum Life stacks start expiring.

Instead of simply reducing Maximum Life back toward its original value while preserving the character's health percentage appropriately, affected players say Wendigo Brand also begins removing large chunks of Current Life.

The ring gives you more health.

Then eventually asks for some of it back with interest.

A Fresh PS5 Report Shows the Same Problem on September 7

The newest report comes from a PlayStation player who says stacking Wendigo Brand works normally at first.

They kill monsters.

The stacks increase.

Maximum Life rises.

No problem.

But once the stacks begin dropping off, Maximum Life correctly decreases while Current Life also starts disappearing in large chunks. After a large monster pack creates many stacks and those stacks subsequently expire, the player says the effect can drain a substantial portion of the health bar.

That description is almost identical to reports players have been posting since April.

Players Reproduced It Without Enemies Attacking Them

The earlier testing is particularly useful because players managed to isolate Wendigo Brand from normal incoming damage.

One player used Warlock's demon mechanics to generate repeated kills and build the ring's effect, then watched the health behaviour once the original stacks reached their expiration window. Other testers reproduced the problem using Training Grounds conditions where ordinary monster damage could not explain the sudden loss.

One May test found that Wendigo Brand could reach around 50 stacks. Everything behaved normally while the effect was building. Once the timer associated with the older stacks expired, however, Current Life began dropping even though the character's Maximum Life remained elevated by the remaining stacks.

Another player reported going from around 32,000/32,000 Life to roughly 11,000/32,000 without an enemy attack or visible debuff responsible for the loss.

Remove Wendigo Brand from the build, and the behaviour stopped.

The Warlock Makes the Bug Much Easier to Trigger

The interaction becomes especially nasty on Warlock because the class can generate kills unusually quickly through its own demon mechanics.

A detailed Season 15 PTR bug report from August explained that sacrificing or destroying summoned demons can count toward Wendigo Brand's kill requirement. That lets a Warlock build stacks far faster than a character relying entirely on ordinary enemy kills.

Normally, that is fantastic synergy.

Warlock gets the damage.

Warlock gets the Maximum Life.

Warlock keeps feeding the ring with disposable demons.

Then 50–60 seconds later, many independently timed stacks can begin expiring in rapid succession and the health bar starts falling with them.

That is particularly relevant now because Warlock currently looks extraordinarily powerful heading into Season 15. PTR players are already building around aggressive Hellfire and demon interactions capable of producing enormous damage. Wendigo Brand theoretically fits that fast-kill environment extremely well.

Provided, of course, you enjoy equipment that occasionally mistakes you for the enemy.

A Hardcore Player Says the Ring Nearly Killed Their Character

The bug becomes considerably less amusing in Hardcore.

One player returned to the original report in July and said Wendigo Brand had almost killed their endgame Hardcore character. They only discovered the cause after noticing unexplained health loss while otherwise surviving the content comfortably.

That kind of issue is particularly dangerous because the game does not clearly communicate that your own Unique is responsible.

If a boss hits you for 90% of your health, you know where the problem came from.

If your health suddenly collapses while killing ordinary enemies, your first instinct is usually to inspect resistances, Damage Reduction, poison effects or whatever unpleasant mechanic was nearby.

Few players begin troubleshooting with:

“Perhaps my Maximum Life ring has turned hostile.”

Hardcore players already have enough invisible or poorly communicated threats to worry about. We recently covered Spawn of the Damned reports that were still apparently deleting Hardcore characters. A self-inflicted health drain from equipment adds another particularly awkward entry to that list.

Blizzard Said It Was Investigating in July

The longevity of the problem is what turns this from an ordinary item bug into today's story.

Players first reported Wendigo Brand draining Current Life on April 30.

Additional confirmations arrived through May and June.

On July 20, Blizzard community manager Marcoose responded directly to the thread and thanked players for the reports, adding that the team was looking into the issue.

That was nearly seven weeks ago.

Then the Season 15 PTR opened.

On August 6, another player submitted an extremely detailed report describing the same Maximum Life expiration behaviour, complete with reproduction steps and an explanation of why Warlock accelerates it.

Now it has surfaced again on PlayStation.

There is still no obvious documented fix for Wendigo Brand's Current Life behaviour in Blizzard's current public patch notes.

The Ring’s Description Makes the Bug Particularly Misleading

The strange thing is that nothing in Wendigo Brand's design suggests that losing Current Life should be part of the trade-off.

Some Diablo items are deliberately dangerous.

Blood-Mad Idol, for example, gives enormous offensive benefits while explicitly making the player take increased Burning damage. If that item hurts you, the tooltip has already prepared the paperwork.

Wendigo Brand is different.

Its Unique power describes increased damage and Maximum Health based on recent kills.

There is no health-drain clause.

No “lose Current Life when stacks expire.”

No warning that Maximum Life is being rented rather than granted.

That is why the player reports consistently describe the health loss as a bug rather than an intended risk mechanic.

Toughness Can’t Help If the Item Is Changing Your Health Behind the Scenes

This also illustrates the problem we discussed recently with Diablo IV's Toughness number against Lilith.

Character-sheet defenses are useful only when players understand the conditions surrounding them.

Wendigo Brand temporarily increases Maximum Life, which should make the character tougher. But if expiring stacks simultaneously remove Current Life incorrectly, the visible increase in survivability can become deeply misleading.

You may look healthier on paper while the item's internal math is quietly preparing a very different opinion.

The Safest Fix Right Now Is Unfortunately Removing the Item

There is no reliable player-side fix documented in the current reports.

The obvious workaround is simply to stop using Wendigo Brand if you notice unexplained health drops as stacks expire.

That is not especially satisfying because the Unique has a genuinely interesting design and can provide excellent damage and survivability in dense content. Warlock in particular has natural synergy with it.

But on Hardcore, or during content where sudden health loss can convert one bad second into a death screen, experimenting with the ring carries an obvious risk until Blizzard resolves the behaviour.

Players can also watch their buff stacks and Current Life carefully in a safe area if they want to determine whether their character is affected.

Just perhaps not on the Hardcore character you have spent 150 hours growing emotionally attached to.

Four Months Is a Long Time for an Item to Fight Back

Diablo IV has thousands of interactions between skills, items, seasonal powers, classes and temporary effects. Bugs are inevitable.

The more interesting question is how long a reproducible bug remains live after it has been isolated and acknowledged.

Wendigo Brand was reported in April.

Players repeatedly reproduced it.

A Hardcore character nearly died from it.

Blizzard said in July that the team was investigating.

The Season 15 PTR reproduced it again.

And on September 7, a PlayStation player is still watching their health disappear when the stacks expire.

That is an impressive survival record.

Especially for a bug attached to an item that keeps trying to reduce everyone else's.

Read More

Diablo 4’s Echoing Elites Trophy Is Still Making PS5 Players Grind Three Times Longer

Diablo IV has spent the last four months patching Lord of Hatred, adjusting drop rates, fixing classes and generally trying to stop Sanctuary's newest systems from biting one another. One PlayStation 5 problem, however, appears to have survived the entire cleanup operation: the Echoing Elites trophy still seems to count bosses while ignoring the elites explicitly mentioned in its own description.

The bug was first documented in May. The thread became active again on September 2, with another PS5 player saying the issue remains unfixed and estimating that PlayStation users may need around 50 Echoing Hatred runs compared with roughly 15 on other platforms.

That is quite a lot of additional demon murder caused by one word in a trophy description apparently not doing its job.

Echoing Elites Says Bosses and Elites Should Count

The Echoing Elites trophy asks players to kill 1,000 bosses or elites in Echoing Hatred. On paper, that should be relatively straightforward once you can consistently survive deep runs of the activity.

Echoing Hatred is one of Lord of Hatred's major endgame additions, an escalating survival challenge where increasingly unpleasant waves of enemies continue arriving until your build, concentration or graphics card finally objects. We covered how Echoing Hatred works alongside Diablo IV's wider endgame overhaul before the expansion launched.

The PS5 trophy appears to have a different interpretation of the assignment.

In the original May bug report, the player initially suspected that certain categories of elite enemy were failing to count. After eventually completing the trophy on May 17, they reached a much stranger conclusion: only boss kills appeared to be progressing it.

The player reported averaging around 21–23 boss kills per run and finally earning the trophy after approximately 44–50 runs. If ordinary elites were included as the description suggests, they estimated it should instead take roughly 15–20 runs.

Players on PC and Xbox Report Much Faster Unlocks

Another player in the same thread provided a particularly useful comparison because they play Diablo IV across PC, Xbox and PlayStation 5. According to their report, the achievement unlocked normally on PC and Xbox after roughly 15 runs, while the PS5 version remained locked after nearly 30.

Other PS5 players later reported unlocking it after roughly 35–42 runs, again describing boss kills as the only reliable source of progress.

That does not establish an exact universal number because Echoing Hatred runs can produce different numbers of bosses depending on how far a build progresses. But the pattern across the reports is remarkably consistent: PlayStation players are doing substantially more runs for the same trophy.

And as of September 2, they are apparently still doing them.

The Trophy Has Another Problem: Getting Into Echoing Hatred

Grinding 40 or 50 runs would be less irritating if Echoing Hatred were something players could simply select from a menu.

It is not.

Access depends on finding a Trace of Echoes, and that item has generated its own long-running complaints. We previously covered players reporting more than 90 hours without seeing a Trace of Echoes drop, effectively locking them out of the activity entirely.

Blizzard has since increased the drop rate for Echoing Hatred keys, which certainly helps. The current patch notes specifically list an increased key drop rate from Elites and Champions. But a better supply of keys does not fix a trophy that apparently ignores most of the enemies players kill after using them.

It merely makes the broken arithmetic more accessible.

This Has Been Reported Since May

The original PS5 report dates to May 14 and contains detailed observations about the trophy's behaviour. Additional confirmations appeared throughout May and June. A July update said it remained unfixed. Another arrived in August.

Then, on September 2, a player returned to the thread with exactly the same complaint.

They estimate that PS5 players are still looking at around 50 runs compared with approximately 15 elsewhere and argue that the combination of incorrect tracking and relatively limited Echoing Hatred access turns the trophy into an unnecessarily long grind.

There has been no indication in Blizzard's current public patch notes that the specific PS5 Echoing Elites tracking issue has been corrected. The company has certainly been fixing plenty of other Lord of Hatred problems; Patch 3.0.2 alone was an enormous cleanup pass across the expansion's systems.

This one has apparently learned to hide.

The Trophy Is Obtainable — Just Much More Annoying Than It Should Be

The important distinction is that Echoing Elites does not appear to be completely unobtainable on PS5. Multiple players have eventually earned it.

You simply may need to kill enough Echoing Hatred bosses to satisfy a counter that appears to have forgotten half of its own requirement.

For completionists, that is arguably worse than an obviously broken trophy. An impossible trophy tells you to stop.

This one smiles politely, lets you continue for another 30 runs and insists everything is perfectly normal.

Four months later, PlayStation players would probably just like the elites in Echoing Elites to count.

```

Read More

Diablo 4’s Nafain’s Bestiary Set May Not Give All Companion Upgrades

Diablo IV's Druid has spent a good portion of 2026 learning that having more animals does not necessarily make life simpler. A fresh bug report is now questioning one of the class's most interesting Talisman sets, Nafain's Bestiary, because its five-Charm bonus appears to promise more Companion upgrades than the game actually provides.

The current tooltip says the completed set lets the Druid gain an additional Bear and all other Companions of each type while also granting “all Companion Upgrades for free.” According to a report posted on August 30, however, the final upgrades at the end of the Companion skill branches are not being granted automatically. That leaves two possibilities: Nafain's Bestiary is not functioning as described, or the wording is broader than Blizzard actually intends.

There is an important wrinkle. This is not the first time players have investigated the set. A separate discussion from May suggests the intermediate Companion upgrades do work even though the skill tree does not visually show them as allocated. The final modifying upgrades, however, still require the player to spend skill points. So Nafain's Bestiary may not be completely broken. The real problem may be that “all Companion Upgrades” does not mean what most players would reasonably expect it to mean.

Nafain’s Bestiary Says You Get All Companion Upgrades for Free

The current five-Charm description is difficult to read any other way. Complete Nafain's Bestiary and the set grants additional Companions while telling the player that all Companion Upgrades are free. For a Druid building around Wolves, Ravens, Poison Creeper and the wider Companion package, that sounds enormously valuable because skill points normally spent completing those branches could theoretically be redirected elsewhere.

The new bug report specifically calls out the fact that the final upgrades are not provided. The player therefore asks whether the set is broken or simply phrased incorrectly, which is probably the most useful way to frame the issue until Blizzard clarifies the design.

If Blizzard intended every upgrade node attached to a Companion skill to become active, then part of the five-Charm bonus is missing. If Blizzard only intended the secondary or “side” upgrades to be granted, the current tooltip needs to say exactly that.

Those are very different bugs, but they create the same problem for somebody trying to build around the set: the item tells you one thing while the skill tree behaves as though the promise came with invisible fine print.

Players Already Tested This Earlier in the Year

A May discussion provides useful context because several Druid players initially believed the entire upgrade portion of Nafain's Bestiary was failing. They equipped the completed set, opened the skill tree and saw no indication that the Companion upgrade nodes had been activated. The nodes still appeared to cost skill points.

One player eventually tested the actual effects rather than relying on the interface. Their conclusion was more complicated: the side upgrades appeared to function despite not being visibly highlighted in the skill tree. They tested Poison Creeper and Ravens and found effects consistent with those secondary upgrades remaining active.

The final upgrade nodes were different.

Those apparently remained unavailable unless the player manually invested the required skill point. Another participant reached the same conclusion, explaining that Nafain's Bestiary provides the side upgrades but not the major final modifier at the end of each Companion branch.

That makes the August report particularly interesting. We are not looking at one player suddenly discovering that nothing works. Players have apparently understood for months that part of the set works invisibly while another part that appears covered by the wording does not activate at all.

The Tooltip Is the Real Problem Even If the Set Is Working as Intended

Diablo IV has a vocabulary problem here. If a tooltip says “all Companion Upgrades,” most players are going to interpret “all” as a fairly ambitious quantity.

Usually somewhere around all of them.

Blizzard may internally distinguish between normal Companion upgrades and the final skill variants, but that distinction is not obvious from the set description itself. A player should not need to visit a forum, read a three-month-old testing thread and manually verify Raven behaviour before understanding which part of their five-piece set bonus exists.

A clearer version could say something like “gain all secondary Companion upgrades for free” or explicitly state that final Companion variants are excluded. That would immediately tell players how many skill points Nafain's Bestiary actually saves and prevent them from planning a build around bonuses they were never supposed to receive.

If the final nodes are supposed to be included, of course, then the wording is fine and the implementation needs fixing.

The Skill Tree Not Showing the Free Upgrades Makes Everything Worse

The confusing tooltip would be easier to live with if Diablo IV clearly displayed which free upgrades were active. According to the earlier player testing, it does not. The side upgrades can function without being visibly allocated in the skill tree, leaving the player to determine their status through gameplay testing.

That is particularly awkward for a build-defining Talisman set. The entire point of these sets is to change how characters are assembled. If the set grants several skill effects without spending points, those effects should ideally be reflected somewhere in the interface so the player can see exactly what has changed.

Otherwise, every questionable interaction becomes a miniature laboratory experiment.

Does the upgrade work?

Equip the set. Find the correct enemy. Trigger the Companion. Watch the buff bar. Count the effect. Remove the set. Repeat.

That is useful work for theorycrafters. It probably should not be the normal onboarding process for an item tooltip.

Season 15 Is About to Make Nafain’s Bestiary Much Stronger

The timing matters because Blizzard is already buffing Nafain's Bestiary for Season 15. The official 3.2.0 PTR notes reduce the two-piece Battle Roar cooldown to five seconds, while the five-piece bonus is being expanded to provide an additional 250% multiplicative Companion damage. Blizzard is even making the Companions grow slightly in size.

In other words, this is not some forgotten leveling set Blizzard is preparing to abandon. Nafain's Bestiary is receiving direct attention in the next major balance pass.

That makes the upgrade wording worth fixing before the stronger version reaches live servers. If Season 15 pushes more Druids toward a Companion setup, substantially more players are going to complete the set and discover that “all Companion Upgrades” apparently excludes part of the Companion upgrade tree.

Blizzard is increasing the damage.

It would be a convenient time to increase the clarity as well.

This Is Another Talisman Problem Where the UI Cannot Quite Be Trusted

Nafain's Bestiary is unfortunately arriving in a system that has already given players several reasons to double-check what the interface tells them. We recently covered reports of Talisman set bonuses stopping during combat, while other players have encountered Seals that refuse to accept Charms or leave completed set bonuses greyed out.

A separate live bug thread has players reporting that some higher-quality Seals simply refuse to accept particular Set Charms at all. Others describe moving a completed five-Charm setup onto another Seal only to have its two-, three- and five-piece bonuses become inactive despite the Charms still visibly occupying the slots.

That issue is technically separate from Nafain's Bestiary, but the player experience is similar. The Talisman interface can show one configuration while the underlying bonus behaves differently.

We also recently looked at how generic Set Charms may effectively disappear from the expected loot pool once players move into Torment. Talisman power itself is interesting; understanding exactly what the system is doing has been the harder part.

The Druid Does Not Need More Invisible Build Math

Companion Druid is already full of interactions involving active and passive Companion effects, skill ranks, individual upgrade branches, multiplicative bonuses and equipment that changes how those Companions behave. Nafain's Bestiary is meant to consolidate some of that complexity by saying, in effect: complete the set and we will give you the Companion package.

Instead, players need to know that there may be three different categories hiding behind one sentence:

• Additional Companions, which appear to work.
• Intermediate Companion upgrades, which reportedly work but are not visually marked in the skill tree.
• Final Companion upgrades, which reportedly are not granted and still require skill points.

That is a lot of interpretation for six words.

It becomes more important when players are optimizing skill points. If a Druid believes Nafain's Bestiary covers an entire Companion branch, they may spend those points elsewhere and unknowingly miss a final modifier that their build guide assumes is active. Conversely, somebody who does not realize the side upgrades are being granted invisibly may waste points buying effects the set already provides.

Neither outcome is particularly satisfying.

This May Be a Wording Bug Rather Than a Mechanical Bug

The current evidence actually makes the conservative explanation quite plausible. Because the earlier testing suggests Nafain's Bestiary has behaved this way for months, Blizzard may have intentionally designed the set to grant only the side upgrades while leaving the final mutually exclusive modifiers under the player's control.

There is a reasonable gameplay argument for that approach. Final skill variants often represent meaningful build choices rather than simple passive improvements. Automatically activating every final Companion variant could create conflicting behaviour or remove choices Blizzard wants the player to make manually.

If that is the design, leaving those nodes out makes sense.

Calling the remaining benefits “all Companion Upgrades” does not.

That would turn this from a balance or functionality bug into something much easier to repair: rewrite the tooltip so it describes the mechanic that already exists.

But until Blizzard confirms that interpretation, we cannot rule out the other possibility — that the final upgrades genuinely should be granted and have simply never been applied correctly.

Blizzard Has Not Clarified the Set Yet

As of September 1, the August 30 bug report has not received an official Blizzard response. The thread is also extremely small, so this is not currently evidence of some widespread Druid failure affecting thousands of characters.

What makes it worth covering is not volume. It is reproducibility.

The set description is visible.

The final Companion upgrade nodes are visible.

Players can complete the five-Charm bonus and immediately compare what the tooltip promises with what the skill tree and abilities actually provide.

And, importantly, players were already doing exactly that in May.

This is therefore much easier to investigate than a random report that a build “feels 20% weaker.” Blizzard only needs to answer one question:

Does “all Companion Upgrades” include the final upgrades?

If yes, fix the set.

If no, fix the sentence.

Season 15 Is the Perfect Time to Clean This Up

Nafain's Bestiary could become much more attractive next season. A five-piece set that brings additional Companions, saves skill points and adds 250% multiplicative Companion damage has obvious potential for players who want the Druid fantasy to involve an entire wildlife documentary following them through Sanctuary.

That is exactly why Blizzard should clarify the current behaviour now.

Players can tolerate a complex build.

They can tolerate mutually exclusive skill choices.

They can even tolerate Wolves occasionally deciding that the safest route to an enemy involves three chairs and a staircase.

What they should not need to tolerate is the word “all” becoming a theorycrafting puzzle.

Sources

Diablo IV Forums: Nafain's Bestiary 5-Charm Bonus Either Broken or Phrased Incorrectly

Diablo IV Forums: Earlier Nafain's Bestiary Set Testing

Blizzard: Diablo IV 3.2.0 PTR Patch Notes

```

Read More

Diablo 4’s 500-Reply Memory Leak Thread Is Still Hard to Ignore

Diablo IV has received new classes, expansions, seasonal systems, endgame redesigns and enough balance patches to make a spreadsheet nervous. Yet one of the most persistent PC complaints remains remarkably familiar: players launch the game, RAM usage climbs, VRAM fills up, performance begins to stutter and eventually something gives up.

One of Blizzard's largest dedicated PC bug threads for the issue now sits at 508 replies and almost 20,000 views. The thread itself dates back to May 2025, when players documented system memory jumping to 15–20 GB within minutes, VRAM increasing with town portals and zone transitions, and crashes arriving after 15–30 minutes. Blizzard acknowledged the reports at the time and asked players to submit crash IDs. More than a year later, the same thread remains one of the most viewed topics in Diablo IV's PC Bug Report section, while fresh August 2026 posts continue describing high RAM and VRAM usage, severe stuttering and performance degradation.

That does not mean every current Diablo IV crash comes from one giant unresolved memory leak. PC performance problems can involve drivers, DirectStorage, texture settings, hardware configurations, overlays and plenty of other variables. But it does mean players have been describing the same basic pattern for an awfully long time.

The Original Report Was Extremely Specific

The major thread began with a player who had already submitted a support ticket and included a crash ID. Their measurements were not particularly subtle. System RAM reportedly climbed to 15–20 GB within minutes, even while sitting at character selection. VRAM increased after town portals and zone transitions until it reached approximately 13–14 GB. Logging out did not release the accumulated memory, and the client eventually crashed with a Fenris dialog after roughly 15–30 minutes.

Other players quickly joined in with wildly different hardware. Reports included RTX 3070, RTX 4090 and RTX 5080 systems, Radeon cards, 16 GB systems, 32 GB systems, 64 GB systems and even one player with 128 GB of DDR5 memory. Some experienced complete crashes. Others reported enormous stutters, long freezes or degrading performance without the game actually closing.

One particularly useful reproduction involved simply teleporting between locations. A player with 32 GB RAM reported starting around 10 GB of system usage and watching another 500 MB to 1 GB disappear after each zone change until the system eventually crashed. That matches the original report's suspicion that old zone assets were not being fully released when new ones were loaded.

Blizzard responded on May 6, 2025, confirming that the team was investigating and specifically asking players to provide the crash IDs generated by the Fenris reporter. A second Blizzard post explained where those IDs could be found inside the Diablo IV installation folder.

So this was not merely a community theory that Blizzard never noticed.

Blizzard knew about the reports.

508 Replies Later, the Thread Is Still One of the Biggest PC Bug Reports

As of late August 2026, Blizzard's PC Bug Report category lists the memory leak thread with 508 replies and roughly 19,700 views. Its most recent activity is dated July 8, 2026, meaning the thread itself is not receiving daily replies anymore, but it survived through multiple seasons and remained active more than a year after the original report.

That longevity matters more than the raw reply count. A short-lived patch problem can produce hundreds of comments in a weekend before disappearing with the next hotfix. This discussion instead spans changes to the game, driver revisions, major content updates and entirely different hardware generations.

Players repeatedly return to the same description: Diablo IV starts normally, memory usage rises while playing, transitions make things worse, stuttering becomes more pronounced and restarting the client temporarily restores performance.

Temporary improvement after restarting is one of the classic reasons players interpret this behaviour as a memory-management issue. It does not prove the precise technical cause, but from the player's perspective the pattern is difficult to ignore. The computer has not changed. The build has not changed. Sanctuary has simply consumed enough memory for one evening and needs to be put back in its box.

Fresh August Reports Show the Broader Performance Problem Has Not Disappeared

The old mega-thread is not the only reason the subject is relevant again. On August 23, a new Technical Support post described severe stuttering and frame-time spikes in towns and crowded areas alongside high RAM and VRAM usage. The player was using an RTX 3060 with 12 GB VRAM and 16 GB system memory and specifically asked whether upgrading to 32 GB would meaningfully help or merely delay the underlying problem.

The discussion remained active through August 25.

Another July report is even more direct. A player with 32 GB RAM measured Diablo IV beginning with total system memory usage around 22 GB before steadily climbing until essentially all 32 GB were occupied. Windows eventually reported that Diablo IV had run out of memory. The player described this behaviour as returning after large content patches and expansions.

Those newer reports are not controlled proof that precisely the same bug from the 2025 thread remains untouched. They could represent related but technically distinct problems. That distinction matters. “Diablo IV has a memory leak” is a much broader claim than “multiple players continue reporting escalating memory consumption and performance degradation.”

The second statement is the one the public evidence supports.

Blizzard Has Been Making Performance and Stability Fixes

It would also be unfair to pretend Blizzard has spent the last year doing absolutely nothing about Diablo IV's PC performance. Patch notes throughout 2025 and 2026 repeatedly mention performance and stability improvements, and Blizzard has changed specific technology when it appeared connected to problems.

One particularly relevant example came in June 2025, when Blizzard disabled DirectStorage by default while investigating performance issues. Players with supported NVMe drives could manually re-enable it through a command-line argument, but Blizzard clearly considered the feature suspicious enough to remove from the default configuration during the investigation.

Later updates continued including general performance and stability improvements. The July 14, 2026 patch again listed “various performance and stability fixes.”

The problem is that broad stability notes make it difficult for players to know whether the particular RAM/VRAM behaviour they have been reporting is considered fixed, partially fixed or still under investigation.

That communication gap is part of why the memory leak discussion refuses to die.

Players Have Found Workarounds, but None Look Like a Universal Fix

Over the life of the thread, players have suggested almost every PC troubleshooting ritual imaginable: lowering texture quality, disabling Ray Tracing, rolling back NVIDIA drivers, clearing shader caches, increasing the Windows page file, disabling overlays, repairing game files, reinstalling Diablo IV and restarting the client periodically before memory usage becomes critical.

Some players report that lowering texture quality helps significantly. Others say disabling Ray Tracing reduces crashes. Some found better stability after changing NVIDIA drivers. Several report that increasing the page file allows Diablo IV to run for longer before failing.

The common problem is that these solutions are inconsistent.

A workaround that helps one RTX 3060 system may do nothing for another machine. A driver rollback can improve performance for one GPU generation while introducing completely different problems elsewhere. Increasing virtual memory can stop Windows from immediately running out of addressable memory, but if the game's memory consumption continues growing, the player may simply be buying more time before the same degradation occurs.

That is why “just add more RAM” is not a particularly satisfying answer. One contributor to the original thread reported the problem while using 128 GB of DDR5.

If Diablo IV can eventually make 128 GB feel nervous, the solution probably is not another trip to the RAM aisle.

This Is Especially Awkward for Steam Deck and Handheld Players

Memory pressure becomes even more obvious on handheld hardware, where system RAM and graphics memory effectively compete inside a much tighter budget. Earlier this year, Steam Deck owners reported Diablo IV crashing approximately every 30 minutes, with some players explicitly connecting the behaviour to the wider memory issue.

We recently covered how Diablo IV players say Steam Deck performance has become worse rather than better, despite the game having had years to mature on the platform. Memory management is particularly unforgiving there because a desktop PC with 32 or 64 GB has enormous overhead a handheld simply does not possess.

A desktop user can sometimes tolerate a leak by restarting the game every few hours.

A handheld crashing halfway through an activity every 30 minutes is considerably harder to call a workaround.

Zone Transitions Keep Appearing in Player Reports

One detail that repeatedly appears across reports is movement between areas. Town portals, entering dungeons, leaving dungeons, visiting crowded towns and moving through different zones are frequently associated with increasing memory usage or sudden performance drops.

That does not necessarily mean zone transitions themselves contain the bug. They naturally force Diablo IV to stream large amounts of textures, geometry, player cosmetics, monsters and environmental data. If a memory-management problem exists elsewhere in the pipeline, teleporting repeatedly is simply one of the fastest ways to expose it.

It also explains why a player can stand in one area for a while without obvious problems, then begin stuttering badly after an evening of Nightmare Dungeons, Helltides, boss runs and trips back to town.

Diablo IV is a game built around constant transitions.

“Stop teleporting” would be an unusual endgame strategy.

Not Every Stutter Is a Memory Leak

This is the point where terminology becomes important. Players understandably use “memory leak” as shorthand whenever RAM or VRAM usage becomes enormous, but high memory usage by itself does not prove a true software memory leak.

Modern games aggressively cache assets because unused RAM is not inherently useful RAM. A game can occupy large amounts of system memory or VRAM without anything technically being wrong, provided it releases memory when required and performance remains stable.

The suspicious behaviour begins when usage continuously increases, old memory appears not to be released, performance degrades over time and closing the application immediately restores the system.

That is why the original thread's teleport reproduction was useful. It attempted to demonstrate a pattern rather than simply posting a screenshot showing “Diablo IV uses 18 GB.”

Likewise, not every Fenris crash is proof of a memory leak. GPU driver failures, unstable overclocks, shader problems and corrupted files can produce similar symptoms. Blizzard's PC client runs across an enormous range of hardware, which makes separating engine-level problems from individual configurations genuinely difficult.

But 500 replies across dozens of different configurations are also difficult to dismiss as one person's broken PC.

Current Patch Notes Do Not Declare the Major Memory Issue Resolved

Blizzard's current Diablo IV patch notes contain multiple references to general performance and stability work, but there is no prominent entry saying that the longstanding RAM and VRAM escalation reports from the major thread have been definitively resolved.

That does not mean Blizzard has made no progress. The experience clearly varies by system, season and patch, and some contributors have reported periods where their crashes improved significantly.

It does mean players have no simple official line they can point to saying:

“Yes, this specific problem has been fixed.”

That ambiguity matters because fresh users experiencing similar symptoms naturally find the enormous old thread through search, see hundreds of matching reports and conclude that the same issue has been running continuously for years.

Maybe technically it has.

Maybe several different problems have produced similar symptoms.

From the outside, those two possibilities look remarkably similar.

Performance Bugs Are Different From Ordinary Diablo Bugs

Diablo IV can survive a Set Charm behaving incorrectly or a War Plans point refusing to unlock. Those bugs are annoying, but the player can usually continue doing something else while waiting for a fix.

Performance degradation is different.

If the game eventually stutters into single-digit frame times, freezes for several seconds or crashes to desktop, every activity becomes affected. Boss fights, Hardcore characters, timed Pit runs and long sessions all become risky.

We have spent much of Season 14 covering small systems that appear to lose track of their own state, including Talisman bonuses reportedly switching off during combat and progression counters becoming stuck. Those are frustrating because the game stops calculating one part of the character correctly.

A performance issue is the same philosophy applied to the entire client.

The build might still work.

The computer would simply like Diablo IV to leave.

The 500-Reply Thread Is Really a Communication Problem Now

Perhaps the most useful thing Blizzard could do is not another generic line about “various performance and stability improvements.” It would be a specific update explaining the status of the memory-management investigation.

Is the original issue considered fixed?

Were several separate problems identified?

Are particular GPU configurations still affected?

Is high VRAM use considered expected behaviour while the stuttering has another cause?

Is Blizzard still collecting Fenris crash reports related to escalating RAM usage?

Players can deal with complicated answers. What creates frustration is not knowing whether the thing they are troubleshooting is something Blizzard believes it already solved twelve months ago.

The original forum response showed Blizzard was looking at the reports. The 508 replies that followed show players kept looking too.

Three Years In, Diablo IV Should Not Need a Restart Ritual

Diablo IV is now a mature live-service game. Some technical problems are inevitable when major seasons add new content, new assets and new systems. PC development is messy, and a problem affecting one particular combination of hardware and drivers can be extraordinarily difficult to reproduce internally.

But memory behaviour that repeatedly becomes a community talking point across multiple seasons deserves more than folklore.

Players should not have to memorize whether this is the season where they need medium textures, Ray Tracing disabled, an old GPU driver, a giant page file and a ceremonial client restart after every third Pit run.

Maybe Diablo IV no longer has the exact memory leak documented in May 2025.

Maybe today's reports represent something different.

But with fresh complaints about high RAM and VRAM usage still appearing in August 2026, Blizzard has not yet reached the most important technical milestone:

making players stop asking.

Sources

Diablo IV Forums: Major Memory Leak — RAM + VRAM Escalation

Diablo IV Forums: Severe Stuttering and High RAM/VRAM Usage — August 2026

Diablo IV Forums: Memory Leak on PC — July 2026 Report

Blizzard: Current Diablo IV Patch Notes

Blizzard: Diablo IV Patch 2.2 — DirectStorage Performance Investigation

```

Read More

Diablo 4 Player Tests Hallowed Ground — Two of Its Bonuses Appear Broken

Diablo IV has plenty of build interactions that are difficult to test properly. Multipliers stack on top of multipliers, Paragon nodes quietly join the calculation, equipment adds half a dozen conditional bonuses and eventually the Training Dummy is being hit by mathematics rather than a Paladin.

One player has taken a much simpler approach to a suspected Consecration problem: remove almost everything.

A fresh Diablo IV bug report posted on August 30 contains a controlled test of the Paladin's Hallowed Ground upgrade for Consecration. The player stripped the character down to a white Ancestral weapon, removed Paragon entirely, used only rank-one skills and disabled damage variance on the Training Dummy. Under those conditions, Hallowed Ground's increased Consecration area appears to work normally. Two of the upgrade's other advertised benefits do not.

Holy Bolt does exactly the same damage inside Consecration as outside it, while Divine Lance consumes exactly the same amount of Faith.

Blizzard has not yet confirmed the issue, and this is currently one player's controlled reproduction rather than a widespread confirmed Paladin bug. But unlike the usual “my damage feels lower” report, this one comes with numbers that are remarkably difficult to misunderstand.

Holy Bolt Was Supposed to Go From 310 Damage to Around 332

The tester deliberately removed as many variables as possible. The setup used rank-one Consecration with Hallowed Ground, rank-one Holy Bolt and rank-one Divine Lance. There were no additional skills, no Paragon Boards, only 79 Strength and nothing equipped except a white Ancestral Cleaver.

With damage variance disabled, Holy Bolt consistently dealt 310 damage to the Training Dummy. The player also calculated that number independently using the weapon damage, Holy Bolt multiplier, Strength bonus and the Training Dummy's damage reduction, producing the same expected result.

That established a clean baseline.

The Paladin then stepped into Consecration with Hallowed Ground active.

Expected damage: approximately 332.

Actual damage: 310.

The number did not move.

That is important because random damage rolls have been removed from the experiment. There is no question of the player simply getting an unlucky low hit inside Consecration and a high hit outside it. The same controlled Holy Bolt hit remains at 310 in both situations.

Divine Lance Still Costs 25 Faith

The second test examined resource cost rather than damage. Divine Lance normally consumed 25 Faith. With the Hallowed Ground benefit active, the player expected the cost to fall to roughly 21 Faith.

Again, nothing changed.

The displayed resource cost remained 25, and more importantly, the actual amount of Faith removed when casting Divine Lance also remained 25. That second part matters because Diablo IV tooltips do occasionally fail to update correctly even when the underlying mechanic works. Here, according to the test, both the interface and the actual resource consumption agree.

Hallowed Ground simply does not appear to be reducing the cost.

So we have two different systems producing the same uncomfortable result: one offensive bonus and one resource bonus both appear absent while standing inside Consecration.

The Area Increase Does Work

This is where the report becomes more interesting than Hallowed Ground simply being completely disabled. The player explicitly notes that the upgrade's increased Consecration size works correctly.

That means the game recognizes Hallowed Ground.

The node is selected. Consecration changes. At least one part of the upgrade activates normally. Yet the tested damage and Faith benefits appear not to be applied.

That makes a simple “the upgrade isn't active” explanation less convincing. The more likely possibilities include individual effects failing to register, an incorrect conditional check for standing inside Consecration or a disconnect between the upgrade's functional effects and what its current tooltip says they should provide.

Exactly which explanation is correct requires Blizzard's internal data. The test only tells us what happens at the Training Dummy.

A Separate Consecration Resource Upgrade Also Looks Suspicious

The tester went one step further and checked Consecration's separate Resource Generation upgrade. That test was less conclusive, but they report that taking the upgrade produced no visible change to Resource Generation on the character sheet.

By comparison, equipping gear with a Resource Generation affix does change the displayed value.

That does not prove the Consecration upgrade is broken. Some Diablo IV bonuses are conditional and therefore do not appear as permanent changes on the stat screen. But combined with the failed Hallowed Ground Faith test, it gives Paladin players another interaction worth examining under controlled conditions.

The important distinction is that the Holy Bolt and Divine Lance tests provide actual gameplay results. The Resource Generation observation currently provides a suspicious UI result. Those are not equally strong pieces of evidence.

Consecration Has Had Other Reported Problems Before

This would not be the first time players have questioned whether every part of Consecration is doing what its tooltip claims. Back in December 2025, Paladin players reported that Hallowed Ground could correctly apply its larger area and longer duration while apparently failing to apply a separate Weakened interaction. Another detailed report earlier this year examined discrepancies between Consecration's displayed duration and the actual duration created by different upgrades.

Those older reports do not prove the new damage and Faith issue shares the same cause. Diablo IV has received many patches since then, and skill behaviour changes over time. They do, however, make the current test worth taking seriously rather than dismissing it as somebody misunderstanding how Consecration works.

There is also a broader Paladin pattern this season where a build can appear correctly configured while an important effect simply fails underneath it. We recently covered how Light's Epiphany can reportedly lose its enormous 500% damage bonus after zone transitions. Players have been able to restore that effect by changing Oaths and switching back, suggesting some Paladin bonuses can become detached from the game state without the equipment itself changing.

That does not mean Light's Epiphany and Hallowed Ground are connected technically. It does mean Paladin players currently have more than one reason to distrust a perfectly normal-looking tooltip.

This Is Why Controlled Dummy Tests Matter

Diablo IV bug reports are often incredibly difficult to evaluate because normal gameplay contains too many variables. A player kills one boss quickly, kills the next slowly and assumes a skill stopped working. Maybe it did. Maybe the second boss had different modifiers. Maybe Vulnerable expired. Maybe a conditional multiplier dropped. Maybe a Talisman interaction changed. Maybe one of Diablo IV's approximately seventeen thousand invisible arithmetic goblins went for lunch.

This test removes most of that noise.

No Paragon.

No legendary equipment.

No complicated rotation.

No damage variance.

One white weapon.

One Holy Bolt.

The result outside Consecration is 310.

The result inside Hallowed Ground is still 310.

That is exactly the sort of reproduction Blizzard can potentially verify very quickly.

The Faith Test May Matter More Than the Raw Damage Loss

A modest missing damage bonus is frustrating, but depending on the build it may not completely change how a Paladin plays. The resource-cost component can be more disruptive because players build rotations around how many abilities they can cast before Faith runs dry.

If Divine Lance is expected to become cheaper while the Paladin remains inside Consecration, players can reasonably build around staying inside that holy area and converting the resource efficiency into additional casts. If the cost remains 25 instead of falling toward the expected value, the entire rotation consumes Faith faster than the skill tree implies.

The player may then compensate elsewhere with additional Resource Generation or resource-cost reduction, sacrificing an affix or passive that should not have been necessary in the first place.

That is the particularly annoying kind of ARPG bug because the character still works.

It is merely worse than the character sheet promised.

Paladin Already Has Enough Build Math to Worry About

The timing is also awkward because Blizzard is still adjusting Paladin balance heading toward Season 15. The recent PTR targeted several underperforming builds, including major improvements to Judgement. We covered how Blizzard doubled Judgement's single-target bonus under the right conditions, while players continued debating whether the class's boss damage had actually improved enough.

Those balance conversations assume the underlying skill bonuses work.

If an upgrade says standing in Consecration improves damage and resource efficiency, theorycrafters naturally put those benefits into their calculations. Build planners compare expected output. Players farm gear to support the resulting rotation. A missing modifier therefore does more than reduce one number; it makes the information used to design the build unreliable.

Diablo IV has also had a particularly busy season for effects that disappear or behave differently from their description. Talisman set bonuses have been reported simply stopping during combat, while generic Set Charms may have their own unusual progression restrictions once players reach Torment. None of these necessarily share a technical cause, but collectively they create the same player problem: it becomes increasingly difficult to know whether a disappointing build is actually weak or whether one of its bonuses quietly failed to show up for work.

Blizzard Has Not Confirmed the Hallowed Ground Bug Yet

As of August 31, the new Hallowed Ground thread has not received an official Blizzard response. It is also extremely fresh, having been posted on August 30, and there is not yet a large group of independent testers posting identical results.

That matters.

The controlled setup makes the report compelling, but one reproduction should still be described as one reproduction. There may be another mechanic affecting how Hallowed Ground is calculated. The tooltip could be misleading rather than the underlying effect being broken. There could be an interaction specific to the Training Dummy.

All of those possibilities remain open until Blizzard or more players test the same setup.

Fortunately, this is unusually easy to reproduce. Any Paladin with access to Consecration, Hallowed Ground, Holy Bolt and Divine Lance can strip away additional modifiers, turn damage variance off and repeat essentially the same experiment.

If You Use Hallowed Ground, Check the Numbers Yourself

For Paladin players currently using Hallowed Ground, the safest advice is not to immediately rebuild the character. Instead, visit the Training Dummy and test it.

Record a repeatable attack outside Consecration.

Stand inside Consecration.

Repeat the attack.

Then compare the Faith consumption of a resource spender inside and outside the area.

If more players consistently reproduce 310 becoming 310 and 25 Faith remaining 25, Blizzard will have a remarkably clean bug report to work with.

Because Sanctuary's holy ground should probably do more than make the circle slightly bigger.

At the moment, that may be the one part we can prove is working.

Sources

Diablo IV Forums: Consecration — Hallowed Ground Does Not Apply Damage Bonus or Cost Reduction

Diablo IV Forums: Earlier Hallowed Ground Weakened Report

Diablo IV Forums: Consecration Duration and Upgrade Testing

```

Read More

Diablo 4 Cataclysm Druid Bug Can Make Bosses Effectively Immune

A Diablo IV Druid player is reporting a particularly ugly endgame bug where a Cataclysm build can begin a boss fight by deleting enormous chunks of health, then suddenly stop dealing meaningful damage altogether. According to the August 30 report, the character can take a boss from full health to roughly 50% in only two hits before the damage calculation appears to freeze. From that point, the player says they can continue attacking for as long as ten minutes without visibly moving the boss's health bar.

The strangest part is that the problem may not be limited to offense. During the same frozen state, the player says Armor and Toughness also stop updating on the character sheet, Fortify generation appears to break and the Druid becomes dramatically easier to kill. In The Pit, the only reliable recovery reported so far is waiting until the Guardian teleports or transitions to another part of the arena, at which point the build's scaling suddenly returns and the boss can once again lose huge chunks of health. Blizzard has not yet confirmed the bug or its cause, so this remains one detailed player reproduction rather than evidence that every Cataclysm Druid is affected.

The Build Goes From Massive Damage to Almost Nothing

The report comes from a player running Cataclysm with Harlequin Crest, Mjölnic Ring, Locran's Talisman and a ZanEom Rune setup. At the beginning of a boss fight, everything apparently behaves normally. Damage ramps exactly as expected and the boss can lose around half its health almost immediately. Then something changes. The player describes a state where attacks continue connecting but damage falls so low that the boss effectively behaves as if it has become immune.

This is not simply a complaint that an endgame boss has too much health. The player reports an abrupt before-and-after transition inside the same encounter: enormous damage followed by virtually none, then enormous damage again after the boss undergoes a hard phase transition. That makes the behaviour considerably more suspicious than a build merely running into scaling it cannot overcome.

The Pit Guardian Can Start Taking Damage Again After Teleporting

The clearest reproduction reportedly happens against Pit Guardians. Once the boss falls below a certain health threshold, Cataclysm damage can apparently collapse. The player can continue fighting without making meaningful progress until the Guardian teleports or respawns into another section of the arena. Immediately after that transition, the character's scaling returns and the Druid may once again one- or two-shot large portions of the remaining health bar.

That phase-reset behaviour is important because it suggests the problem may involve a temporary character state rather than the boss gaining a legitimate defensive modifier. The player believes Cataclysm's damage snapshot or another part of the build's scaling becomes desynchronized during the encounter, although that explanation is their interpretation rather than a diagnosis from Blizzard.

We have seen other Season 14 bugs where important Talisman bonuses can stop functioning until something forces the character state to refresh. That does not mean the two bugs share the same cause, but the similarity is hard to miss: the gear remains equipped, the UI may still suggest the build is intact, yet part of the underlying character calculation appears to stop behaving normally.

Armor and Toughness Apparently Freeze at the Same Time

The player's later update makes the report much more interesting. When the damage failure occurs on Torment 10, they say the character sheet's Toughness and Armor values stop updating as well. During that state, the Druid becomes unusually fragile and begins taking sudden lethal hits that do not happen while the build is functioning correctly.

The player also believes background damage reduction and Fortify generation are no longer being applied correctly during the freeze. Again, those specific mechanisms have not been independently verified, but the character-sheet behaviour gives players something more concrete to reproduce than “my damage feels low.” If offense and defense both stop recalculating during the same phase, the problem may sit deeper than one broken Cataclysm multiplier.

That also connects awkwardly with the wider Diablo IV discussion around sudden one-shots and the difficulty of understanding why a character died. A legitimate endgame hit is one thing. Becoming dramatically more vulnerable because part of the character's defensive state silently stopped updating would be something else entirely.

Locked Endgame Activities Make the Bug Harder to Work Around

The player says the issue is particularly disruptive in The Pit and Kurast Undercity, where equipment changes can be restricted. Normally, one of the first community troubleshooting methods for a broken item interaction is to unequip and re-equip the relevant piece, forcing the game to recalculate the character. If the activity prevents gear swapping, that option disappears.

According to the report, the Druid can therefore become trapped in the broken state until the boss itself triggers a sufficiently large transition, the player dies or the instance state is otherwise refreshed. That turns what might have been an irritating equipment bug in the open world into a genuine endgame blocker. A Pit run is timed; spending several minutes attacking a boss whose health bar refuses to move is not merely inconvenient.

Mjölnic Ring Makes Cataclysm an Especially Complicated Skill to Debug

Cataclysm already interacts with several layers of modern Druid scaling. Mjölnic Ring is particularly important because its Unique power grants unlimited Spirit while Cataclysm is active and provides a large multiplicative damage bonus. Blizzard has repeatedly adjusted the Ring and Cataclysm itself over Diablo IV's lifetime, including increasing Mjölnic Ring's damage range and changing how frequently Cataclysm lightning can strike the same target.

Cataclysm has also received multiple technical fixes. Blizzard previously corrected an issue where its Severe Storm Variant could be interrupted by crowd control, while older patches changed its strike frequency and single-target behaviour. None of the current official patch notes identify a bug where Cataclysm loses all scaling during boss phases, but the skill has enough interacting systems that a snapshot or state-refresh problem is at least plausible.

That does not establish Mjölnic Ring, Locran's Talisman or Cataclysm itself as the culprit. The current report only tells us which pieces were present when the problem occurred.

This Is Still One Detailed Report, Not a Confirmed Widespread Bug

The most important limitation is sample size. As of August 31, the Blizzard bug thread has only the original detailed report and no large collection of players independently confirming the same reproduction. That is very different from long-running issues such as the War Plans 9/10 progression bug, where multiple players across several months have described essentially identical states.

So we should not tell every Cataclysm Druid that their build is broken. The correct conclusion is narrower: one player has documented a repeatable-looking failure in which Cataclysm damage collapses during boss encounters, defensive stats appear to freeze at the same time, and a boss phase transition restores the build.

That is specific enough to deserve investigation. It is not yet broad enough to declare a class-wide problem.

A Controlled Test Could Narrow the Cause Quickly

If more Cataclysm players want to reproduce the issue, the useful approach is fairly straightforward. Record Armor, Toughness, Fortify state and damage before the boss reaches the suspected threshold. When damage collapses, check whether those values stop changing. Note whether Cataclysm is active, whether Mjölnic Ring's buff remains visible, whether Locran's Talisman is contributing normally and exactly what event restores the character.

Testing the same build with one major component removed would help even more. If the failure disappears without Locran's Talisman, that points in one direction. If it only happens while Mjölnic Ring and Cataclysm overlap, that points somewhere else. If entirely different Cataclysm setups can trigger the same stat freeze, Blizzard suddenly has a much stronger case to investigate at the skill or character-state level.

Right now the most valuable detail is the reported recovery after a boss transition. Bugs that disappear when the game is forced to rebuild an encounter or character state tend to leave much better breadcrumbs than bugs that simply happen randomly.

If the Character Sheet Freezes, This Is Bigger Than a Damage Bug

The damage loss is what makes the report immediately noticeable, but the frozen defensive values are potentially more serious. A Cataclysm build dealing no damage is frustrating. A character simultaneously losing or failing to update Armor, Toughness, Fortify and damage reduction can die without the player understanding what changed.

That combination also explains why the original reporter describes the issue as ruining endgame progression rather than merely weakening the build. The Druid can apparently begin the encounter massively overqualified for the boss, become almost powerless midway through it and then return to full strength after a phase reset. Build power has not actually changed. The game state has.

At least, that is what the current evidence suggests.

For Now, Cataclysm Druids Should Watch Their Stats During Boss Fights

Until Blizzard responds or more players reproduce the issue, there is no universal fix to recommend. If a Cataclysm Druid suddenly stops damaging a Pit Guardian, however, it may be worth checking Armor and Toughness rather than assuming the boss has simply become much tankier. If those values also appear frozen, the current report suggests waiting for a boss phase transition may restore the character. In content where that never happens, dying or otherwise forcing an instance refresh may be the only available workaround.

Ideally, none of this should be necessary. Cataclysm is supposed to summon a massive storm that destroys everything around the Druid.

It probably should not include a hidden second phase where the storm files for administrative leave.

Sources

Diablo IV Forums: Cataclysm Druid Stops Dealing Damage

Blizzard: Current Diablo IV Patch Notes

Blizzard: Mjölnic Ring and Cataclysm Changes

```

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 Player Says Boss Loot Is Going Straight to the Stash

Diablo IV has spent years teaching players a very simple ritual: kill boss, watch loot explode across the floor, inspect glowing items and discover that most of them are not quite as exciting as the beam suggested. Now one player is reporting a considerably stranger variation. In several endgame activities, the boss appears to die normally, but some of the expected loot never appears on the ground at all. Instead, the game's Lost Items notification appears on the Stash immediately after the kill, suggesting the rewards may be getting routed directly into storage before the player ever has a chance to pick them up.

The report is extremely fresh — posted late on August 28 — and currently has very little independent confirmation, so this is not something we can describe as a widespread Season 14 bug. But the player says they have seen the same behaviour in multiple activities, including Kurast Undercity, Lair Bosses and The Pit, and specifically notes that no loot filters were enabled. If reproducible, it would be a very odd inversion of Diablo IV's normal Lost Items system. That system is supposed to rescue important loot you failed to collect. It is not normally supposed to intercept the drop before you see it.

The Stash Notification Appeared the Moment the Boss Died

The clearest example comes from Kurast Undercity. According to the report, the player killed the boss and immediately noticed the familiar exclamation mark appearing on the nearby Stash. That notification normally means the Lost Items tab has recovered something valuable left behind elsewhere in Sanctuary. The unusual part is that the player says the expected boss loot had never appeared on the floor in the first place.

They report seeing similar behaviour after Lair Bosses and Pit encounters, which makes the issue more interesting than one strange Undercity reward event. There is still a large gap between “one player reproduced this in several places” and “Diablo IV is automatically mailing boss loot to everyone,” but the multi-activity pattern is exactly the sort of thing worth documenting while more reports either confirm or contradict it.

A second forum user immediately asked the obvious diagnostic question: does everything disappear, leaving nothing visible on the ground as though a loot filter had hidden it? That distinction matters because Diablo IV's filtering systems can intentionally suppress large amounts of visible loot. The original report explicitly says loot filters were turned off, which is why the Lost Items notification became suspicious.

The Lost Items Stash Is Supposed to Catch Loot You Miss

Blizzard has supported automatic recovery for important equipment since launch. Legendary items left behind — including loot missed because of a disconnect — can be sent to a special Lost Items section in the player's Stash. Later patches expanded the concept to other valuable drops such as Scattered Prisms, Resplendent Sparks and Scrolls of Escape.

The purpose is obvious and useful. Diablo produces a lot of loot, and players should not permanently lose an important Legendary because it landed behind scenery or because the game disconnected two seconds after the boss died. The Lost Items tab acts as insurance.

But insurance normally requires something to have gone wrong first.

The current report suggests the game may sometimes be deciding that loot has been “missed” almost instantly, before the normal ground-drop interaction has occurred. If that is what is happening, the system designed to prevent missing loot could itself be hiding the loot.

This Could Be a Display Problem Rather Than a Reward Problem

There are several possible explanations, and right now none of them is confirmed. The safest interpretation is not that bosses are failing to generate rewards entirely. If the items truly appear in Lost Items, then the reward may still have been created correctly. The bug could instead sit somewhere between the server deciding what dropped and the client deciding what should appear on the ground.

That would make this more of a presentation or loot-routing bug than a traditional “boss dropped nothing” problem. The distinction matters. Receiving a Mythic directly in the Stash is much less serious than never receiving the Mythic at all. It is still confusing, particularly when players rely on the visible loot explosion to understand what an activity rewarded.

There have been separate Season 14 reports where bosses genuinely appear to provide too little or no loot, including Ultimate Nemesis encounters. Those should not automatically be merged with this new report. One issue may involve missing rewards. The other may involve rewards being generated but routed somewhere unexpected.

Diablo 4 Has Already Had Some Very Strange Loot Problems This Season

Season 14 has produced an unusual amount of discussion around the relationship between loot and the activities that award it. We recently covered how Nemesis portals can still disappear while players are dealing with the loot from the boss they just killed. In that situation, the game effectively creates the opposite problem: the loot is definitely on the ground, but spending too long inspecting it can cost you access to the next encounter.

This new report would be almost comically convenient by comparison. No need to spend 90 seconds comparing boots. Blizzard has apparently already taken them home.

That joke only works if the Lost Items system reliably preserves everything important, though. The Stash recovery tab has limited capacity, and players are used to emptying it precisely because they do not want new recovered items competing with old ones. A hidden system routing more boss rewards there than intended could therefore create problems of its own.

It Would Also Undermine the Actual Loot Moment

Even if every item arrives safely, there is a less technical problem. Diablo is built around seeing things drop. The color beam, the sound, the item name and that tiny pause before checking whether the thing is useful are part of the reward. Blizzard has spent years tuning loot rarity and reward presentation precisely because the moment an item hits the ground matters.

That is especially relevant during the current debate over whether Diablo IV still has enough genuinely exciting chase loot. As we discussed in our article about players asking for truly rare items beyond the increasingly accessible Mythic system, one of the community's recurring concerns is that loot should occasionally create a moment of surprise rather than simply appear as another progression resource.

A truly rare item materializing silently in the Stash would technically solve the inventory problem while completely murdering the celebration.

Imagine finally getting the drop you wanted after 200 boss kills and discovering it later between two forgotten Legendaries because a small exclamation mark appeared in town.

Efficient.

Not especially Diablo.

Loot Filters Are the First Thing Blizzard Would Need to Rule Out

The report's explicit claim that no filters were active is important because Diablo IV's increasingly sophisticated loot filtering can make large categories of equipment disappear from normal view. A misconfigured filter could easily create the impression that nothing dropped while the game continued tracking valuable filtered items through other systems.

If Blizzard investigates the report, reproduction would therefore need to start with every filter disabled and an empty Lost Items tab. Kill a known boss. Record the expected loot. Check whether the Stash notification appears immediately. Then repeat across Undercity, Pit and Lair Boss encounters.

If items consistently skip the ground under those conditions, the behaviour becomes much harder to dismiss as a filter issue. If it only occurs with particular filter configurations, the bug may lie in how the new loot presentation interacts with Lost Items.

Torment Difficulty Already Converts Some Loot Automatically

There is another system that can make Diablo IV's drops look different from earlier versions of the game. At Torment difficulty, lower-quality items that would have dropped can instead be automatically converted into crafting materials. Blizzard introduced that change specifically to reduce screen clutter and keep irrelevant Normal, Magic and Rare items from filling the ground at endgame.

That is intended behaviour, but it should not explain important Legendary, Unique or Mythic rewards being routed directly into Lost Items. Those are exactly the items the recovery system was built to preserve.

The current report does not specify every item rarity that appeared in the Stash afterward, so we should be careful not to infer more than the player actually observed. The important evidence is the immediate Lost Items notification combined with the absence of expected visible boss loot.

There Is Not Enough Evidence Yet to Call This Widespread

This is one of those stories where the date matters almost as much as the report. The thread was created at 11:49 p.m. on August 28. As of the morning of August 29, it consists of the original report and an early follow-up question. There is no large pile of “same here” replies yet, and Blizzard has not publicly acknowledged the behaviour.

That means the headline needs to remain exactly what it is: a Diablo IV player says this is happening. Not “Diablo IV now sends boss loot directly to your Stash.” Not “Season 14 broke boss drops.” We simply do not have enough evidence for either claim.

But fresh bug reports are worth watching when they describe something this specific. Undercity is particularly useful because the Stash can be visible in the boss area, making the notification timing easy to observe. If more players reproduce the same thing today, the report could become much more significant very quickly.

For Now, Check Lost Items If a Boss Seems Suspiciously Empty

Until the behaviour is better understood, there is at least one useful takeaway. If a Pit, Undercity or Lair Boss suddenly looks unusually stingy, check your Stash before assuming the rewards disappeared entirely. The Lost Items tab may contain something the floor never showed you.

That is hardly an ideal workaround because the whole point of killing the boss is normally to receive the loot where the boss died. But it is much better than concluding the game deleted the reward and walking away.

And perhaps tomorrow another player will confirm the entire thing was an obscure filter interaction. That would be fine too. Bugs are considerably more enjoyable when they stop being bugs.

For now, though, Diablo IV may have discovered a very modern solution to loot clutter:

Don't drop the loot.

Send it home.

Sources

Diablo IV Forums: Loot Going Straight to Stash Without Dropping

Blizzard: Diablo IV Lost Items Stash Explained

Blizzard: Additional Lost Items Stash Changes

Diablo IV Forums: Separate Ultimate Nemesis Lair Loot Reports

```

Read More