Diablo 4’s Generic Set Charms May Stop Dropping Once You Reach Torment

Diablo IV's Talisman system has a strange little progres
sion problem hiding inside it. The game's generic, class-less Set Charms are supposed to provide useful combinations while a character is still developing, offering sets such as Practiced Technique, Slaughter and Mastery without locking the player into one particular class. The problem, according to a growing collection of player observations, is that these Charms may effectively disappear once a character reaches Torment difficulty. By the time somebody decides they would actually like to complete one of the sets, the game may already have moved them into a different loot pool.

The current bug report began with a player noticing that class-specific Set Charms continued dropping regularly while generic ones had apparently vanished. They had only seven generic pieces in total — enough for one completed set and fragments of the others — despite seeing roughly ten class-specific Set Charms per day. Other players immediately recognized the pattern. Several said they had not seen a generic Set Charm for a long time and suspected that the items only drop during the pre-Torment leveling phase. One player then performed a small but particularly interesting test with a new character and Horadric Cube rerolls, producing results that appear to support that theory.

Generic Set Charms Seem to Belong to the Leveling Game

The basic distinction is important. Diablo IV's Talisman system contains class-specific Charm sets designed around particular skills and playstyles, but it also contains generic sets that any class can theoretically use. Those class-less options are useful early because they do not require a player to already have a polished endgame build. Instead, they offer broad bonuses that can complement whatever equipment happens to drop during leveling.

Players in the current discussion mention generic sets such as Practiced Technique and Slaughter, and an earlier Season 15 PTR discussion also identifies Mastery as part of this class-less category. The problem is not necessarily that these sets are supposed to compete with optimized endgame class sets. Several players are perfectly happy with them being transitional gear. The issue is that transitional gear only works if it drops early enough for the player to assemble it while it is still transitional.

One player summarizes the experience rather well: they found one generic Set Charm at level 36, another at 59 and then nothing useful before reaching level 70. By the time a full set might realistically come together, the character has already entered the part of Diablo IV where much stronger class-specific options begin taking over.

One Player Tested the Reroll System Before and After Torment

The most useful evidence comes from a player who levelled a Necromancer alt and deliberately experimented with Charm rerolling. They gave the Necromancer unwanted Barbarian Set Charms and used the Horadric Cube's three-to-one reroll recipe while the character was still on Penitent difficulty. According to their report, the rerolls repeatedly produced generic Charms such as Practiced Technique or Slaughter.

Then they unlocked Torment I and performed the same process again.

The results changed.

Instead of producing generic Charms, the rerolls reportedly began returning Necromancer-specific Set Charms. That does not prove every relevant loot table in Diablo IV uses a hard “generic before Torment, class-specific after Torment” switch, but it is considerably more useful than simply saying the items feel rare. The same player changed one major variable — Torment access — and observed a different Charm pool afterward. The original reporter subsequently tried the idea on a fresh character and confirmed at least part of the pattern by finding a generic Set Charm at around level 40.

Blizzard has not published a statement confirming that generic Set Charms are intentionally restricted to pre-Torment progression, so we should treat the exact rule as a community finding rather than official documentation. But the available reports fit together surprisingly well.

If This Is Intentional, the Drop Window May Be Too Small

There is nothing inherently wrong with leveling-only item sets. Diablo has always contained equipment that shines for twenty levels and then gets replaced. Nobody expects Sigon's Complete Steel to remain the ultimate Diablo II endgame setup simply because it looked excellent on a level 25 Barbarian. Transitional gear can make leveling much more interesting precisely because it provides temporary power spikes.

The difference is that a set needs enough time to become a set. If generic Charms stop entering the normal pool around Torment, but their individual drop rates are low enough that many players only see one or two before level 70, the system has created equipment whose theoretical purpose and practical availability barely overlap.

An earlier PTR feedback thread raised exactly this complaint before the current bug report appeared. Players described the generic sets as “too rare” and too tightly level-windowed to reliably assemble while they matter. One player said they had never used any of the sets because the pieces simply took too long to appear, while another argued that they can work as starter sets but become irrelevant once endgame class options arrive.

That makes the current Torment observation less like a random Season 14 oddity and more like a structural weakness in the Talisman progression curve.

The Collector Problem Makes It Even Stranger

There is another group affected even if Blizzard never intended generic Set Charms to be competitive at endgame: completionists. Once a character reaches Torment and class-specific Charms dominate the drop and reroll pool, collecting the older generic sets may require deliberately creating and leveling another character below Torment just to farm equipment the account has already outgrown.

The original reporter explicitly points this out. If the only reliable way to complete the generic sets is to remain below Torment, the effort required to collect them may massively outweigh their actual usefulness. A player interested in experimenting with Practiced Technique on an established character could theoretically have a harder time acquiring the pieces than somebody who does not yet need them.

That is backwards progression. Usually Diablo lets more advanced characters farm old equipment faster. Here, becoming stronger may actually remove access to part of the loot pool.

The Talisman System Already Has Enough Complexity

This issue lands inside a system that players are still learning to trust. Talismans combine Seals, Charm slots, Set bonuses, Unique Charms and multiple layers of item quality, and Blizzard has already spent several patches fixing bugs around them. We recently covered reports of Talisman set bonuses simply stopping during combat, including Habacalva's Cauldron losing its Heat functionality and separate problems involving Light's Epiphany.

Blizzard's own patch notes also contain fixes for Charm sorting, incorrect Gold Find values, missing item power displays, Seal slots that failed to unlock correctly and Talismans behaving incorrectly when Armory loadouts changed. None of that means the entire Talisman system is fundamentally broken, but it does mean players are already dealing with enough invisible rules that another undocumented loot-pool boundary is difficult to distinguish from a bug.

If generic Set Charms are intentionally pre-Torment items, the game should probably say so. If they are supposed to remain obtainable later, the current reports deserve investigation.

Rerolling Makes the Suspected Restriction More Important

The three-to-one Charm reroll system should theoretically help smooth bad luck. Receive three class Set Charms you do not want, feed them to the Cube and take another chance. That is exactly the sort of mechanism an ARPG uses to prevent useless drops from becoming completely wasted.

But if the reroll pool itself changes after entering Torment, the Cube cannot solve the generic Set Charm shortage. An endgame player could salvage or reroll hundreds of unwanted class pieces without ever seeing the generic Charm required to finish an older set. The more advanced your character becomes, the less useful the game's bad-luck conversion system becomes for this specific collection.

This is particularly odd because Diablo IV has been moving in the opposite direction elsewhere. Season 15's PTR made Mythic crafting more deterministic, while other systems increasingly allow players to target categories rather than depend on completely uncontrolled RNG. We have also seen players recently ask whether Diablo IV needs genuinely rare chase items again. Generic leveling Charms are probably not where most people wanted Blizzard to restore impossible scarcity.

Season 15 May Make Charm Availability Even More Important

The current conversation is happening while Blizzard is already preparing another expansion of the Charm pool. The Season 15 PTR includes additional Unique Charms based on existing and Legacy Uniques, giving players more options for endgame build construction. That is good for variety, but every new Charm also makes the underlying acquisition rules more important.

Players have already raised concerns that some classes have much stronger Unique Charm pools than others, and that the gap between the best combinations and mediocre ones can materially affect build power. Generic sets could provide a useful fallback or complementary option if Blizzard allowed them to remain relevant beyond leveling. Instead, the current design appears to place them in the one part of progression where players are least likely to stop and farm a complete collection.

That does not necessarily mean Blizzard should simply make the generic sets powerful enough to replace class sets. The game already has plenty of endgame systems competing for attention. But allowing generic Charms to remain obtainable at higher difficulties would at least give players the option to experiment with them.

There Are Several Easy Ways Blizzard Could Fix the Awkwardness

If the current behaviour is unintended, the obvious solution is simply restoring generic Set Charms to the Torment loot and reroll pools. They could remain less common than class-specific pieces without becoming effectively inaccessible. If Blizzard deliberately wants them restricted to leveling, there are cleaner alternatives that preserve the intended progression role.

A vendor could sell generic Charm caches after level 70. The Horadric Cube could include a recipe specifically targeting class-less sets. Generic Charms could be added to a low-cost cache from an existing activity, or the player could choose between generic and class-specific output when rerolling. None of those changes would make the sets powerful. They would simply keep them obtainable.

Blizzard could also increase their early drop rate dramatically. If the intended fantasy is “assemble a small generic set while leveling and replace it in Torment,” then make sure players actually assemble one before Torment. Finding the third piece fifteen minutes after the character has already graduated into stronger class sets misses the point.

Maybe They Are Supposed to Be Disposable — But They Still Need Time to Exist

One of the more reasonable responses to the earlier PTR feedback argues that not every item in Diablo needs to have an endgame purpose. That is true. Games become exhausting when every low-level mechanic needs a Tier 150 Tower build attached to it. Generic Charm sets can simply be useful leveling tools.

But a leveling tool that is too rare to assemble while leveling is not really a leveling tool. It is a collection of isolated orange objects with aspirations.

The distinction matters because set bonuses are inherently about completion. A single generic Set Charm may provide useful affixes, but the reason the item exists as part of Practiced Technique or Slaughter is to make the player chase the combination. If most characters naturally reach Torment before that combination becomes realistic, the progression window needs another look.

For Now, Farm Them Before Torment If You Want Them

Until Blizzard clarifies the intended drop rules, the available player testing suggests one practical piece of advice: if you specifically want to collect generic Set Charms, do it before unlocking Torment. The current reports indicate that both natural drops and three-to-one rerolls may become heavily or entirely class-specific afterward.

That advice comes with an obvious caveat. We do not have Blizzard-confirmed drop tables, and the sample size is small. RNG can create convincing patterns from very little data, particularly when the items involved are already uncommon. More players reproducing the Penitent-versus-Torment reroll test would tell us much more.

But the current evidence is good enough to make the system worth watching. One player noticed generic Charms had vanished. Others independently said the same thing. A reroll experiment produced generic sets before Torment and class sets after Torment. A fresh character then produced a generic drop around level 40.

If that is intentional design, it probably needs better communication.

If it is not intentional?

Somewhere in Sanctuary, a box of Practiced Technique Charms may have been accidentally left behind at level 69.

Sources

Diablo IV Forums: Generic Set Charms Stopped Dropping

Diablo IV PTR Forums: Generic Charm Sets and Their Leveling Window

Blizzard: Diablo IV Patch Notes — Talisman and Charm Updates

Blizzard: Season 15 PTR Charm Updates

```

Read More

Diablo 2 Warlock Players Say a 62% Bind Chance Doesn’t Feel Like 62%

Diablo II: Resurrected's Warlock has already spent much of 2026 being adjusted, rebalanced and occasionally hit with the sort of numerical correction that makes an entire build quietly put its equipment back into the stash. Now players are questioning something more fundamental about Bind Demon. One Season 15 Warlock reports showing a 62% chance to bind while repeatedly channeling the skill on Lister the Tormentor, only to spend 20–30 seconds watching attempt after attempt fail while Lister was already down to roughly 30% Life. Other Warlock players responding to the report say Bind Demon has felt noticeably less reliable since the latest updates, raising a simple question: does the percentage displayed by the skill actually represent what players think it represents?

There is not enough evidence yet to say Bind Demon is mathematically bugged. We have one detailed current report, several players saying the skill feels strange, and a mechanic that has become substantially more complicated since Reign of the Warlock launched. Missing monster health affects the bind chance, Death Mark provides a synergy, different monster types require different levels of hard-point investment, and Blizzard changed how often the game actually performs a bind check. That gives us several perfectly plausible explanations before we arrive at “the percentage is fake.” But when the interface says 62% and a player can apparently channel for half a minute without success, it is understandable that people start looking suspiciously at the number.

The Current Report Involves Lister at Around 30% Life

The new discussion was posted on August 29 by a Warlock player who says their Bind Demon tooltip showed a 62% success chance. They were trying to convert Lister the Tormentor, one of Baal's Super Unique minions, and report reducing him to around 30% Life before beginning repeated binding attempts. According to the player, Lister continued resisting Bind Demon for roughly 20–30 seconds despite continuous attempts, leaving the Warlock standing close enough to be “mauled” while waiting for the conversion to happen.

Other players immediately suggested the normal Bind Demon troubleshooting steps. Lower the demon's health further. Make sure you are holding the Bind Demon channel rather than repeatedly clicking it. Confirm that enough hard points have been invested to bind a Super Unique. The original poster says they were already channeling the skill, had 20 hard points in Bind Demon and continued seeing the same failures with Lister at roughly 30% health.

That does not give us a controlled test sample, but it does make the report harder to dismiss as somebody simply misunderstanding how the skill works.

Bind Demon No Longer Works Like It Did at Launch

Part of the confusion comes from how aggressively Blizzard has changed Bind Demon since Reign of the Warlock arrived. The original version was extraordinarily generous. A tiny investment could give Warlocks access to powerful permanent demons with exceptional affixes and auras, which quickly created balance concerns. Blizzard's later redesign made the skill much more investment-heavy: 10 hard points are required for Champions, 15 for Unique monsters and 20 for Super Uniques. Death Mark's bind-chance synergy was reduced from 1% per point to 0.5%, and the benefit gained from lowering the target's health was reduced and made dependent on monster type.

Blizzard also changed the actual bind-check timing. During the Season 14 PTR, the developer explicitly fixed Bind Demon because it was checking the conversion roll far too frequently. Instead of rolling every two frames, the game now performs the bind check on the 24th frame, effectively around once per second. That was a major mechanical change and helps explain why modern Bind Demon can feel dramatically slower than the version players first encountered.

We already covered the next stage of the problem when Patch 3.3 corrected Bind Demon's additional damage bonus. Warlock summoners immediately reported enormous damage losses from their bound demons, particularly in high-end content. Now the conversation is moving from how hard the demon hits after conversion to how reliably the player can convert it in the first place.

If 62% Means 62% Per Check, a 20-Second Failure Streak Would Be Extraordinary

This is where the tooltip becomes interesting. If the displayed 62% were literally an independent 62% success chance on every eligible once-per-second bind check, failing 20 consecutive times would be astonishingly unlikely. The probability of failing one 62% roll is 38%. Failing 20 independent rolls in a row would be roughly 0.0000004%. Thirty consecutive failures would be even more absurd.

That does not prove the skill is broken, because we do not know that the displayed percentage should be interpreted as a simple final per-second success roll. Bind Demon may have additional eligibility checks or monster-specific calculations that the interface does not communicate. Lister may behave differently because he is a Super Unique. Remaining Life may alter the actual conversion calculation in a way the tooltip does not fully expose. There may also be an attack-rating or defensive interaction involved that players are conflating with the displayed bind percentage.

But that is precisely why the report deserves attention. If “62% chance to bind” is not the final chance that players intuitively think it is, the UI needs to explain what the number actually means.

Missing Health Is Still a Major Part of the Mechanic

Players in the current thread repeatedly point toward target health. Blizzard's official Bind Demon redesign specifically says that missing health increases the chance to bind and that the benefit varies by monster type. Another experienced Warlock player responding to the report says Bind Demon still appears to scale very strongly with remaining Life and recommends damaging stubborn targets further before trying again.

That means 30% health may sound low without necessarily being the ideal binding threshold for a Super Unique. If the game heavily penalizes attempts while a high-tier demon still has substantial Life remaining, the displayed 62% may represent only one component of the calculation rather than the actual final success probability.

This design makes thematic sense. Bind Demon has increasingly become Diablo II's version of catching a dangerous monster after weakening it first. The problem is that the game needs to communicate the rules clearly enough that players can distinguish bad luck from incorrect play. A percentage is supposed to help with that. If the percentage still leaves players wondering whether they should believe it, it is not doing much work.

Death Mark Makes the Skill-Point Requirement Even Heavier

The discussion also highlights how expensive a serious Bind Demon setup has become. To bind a Super Unique at all, the Warlock needs 20 hard points in Bind Demon. Death Mark then contributes additional bind chance through its synergy, while Demonic Mastery controls how many demons the Warlock can maintain. A player building heavily around bound demons can therefore spend a very large portion of Diablo II's limited skill-point budget simply making the system function consistently.

That was intentional. Blizzard wanted to remove the old “one-point wonder” version of Bind Demon and force players to commit if they wanted powerful permanent demons. The tradeoff is that failures now feel worse. If somebody spends 20 hard points in Bind Demon, additional points supporting the mechanic and gear raising the displayed chance to 62%, standing beside Lister for 30 seconds without success does not feel like a light investment encountering normal resistance.

This same tension is why the new Warlock has generated complaints from older summon classes. In our article on Necromancer players wanting some of the Warlock's more modern summon-control tools, the interesting comparison was how much design attention Blizzard gave the new class's demon systems compared with the twenty-five-year-old skeleton army. Bind Demon shows the other side: newer does not necessarily mean simpler.

Patch 3.3 Fixed Bind Demon Damage, Not the Bind Chance

It is also important not to confuse two different changes. Season 15's Patch 3.3 contains one explicit Bind Demon bug fix: Blizzard says the skill's additional damage bonus was greater than intended. That is the correction that caused the major summoner damage complaints after the patch. Blizzard's 3.3 notes do not list a change to the actual conversion-success formula.

The major binding-mechanic changes happened earlier during Patch 3.2 development: hard-point requirements, weaker Death Mark synergy, reduced missing-health benefit and slower check frequency. If Bind Demon genuinely feels different again after 3.3, either the damage fix affected something unexpected, another undocumented interaction changed, or players are simply noticing the already harsher binding system more now that the class has entered another fresh Ladder season.

At the moment, there is no Blizzard acknowledgement confirming a new Bind Demon success-rate bug in Season 15.

The Skill Has Been Controversial Since the PTR

What makes the current complaint less surprising is that players raised almost exactly the same issue during the April PTR. Testers with 20 hard points in Bind Demon reported struggling to convert high-tier demons even after lowering their health. One player described the new system as tedious because the player has to carefully reduce the target's Life without killing it, then stand still channeling Bind Demon while hoping the conversion occurs before either the demon or Warlock dies.

Another PTR feedback post argued that random conversion chance itself was the wrong design. The suggested alternative was a fixed bind probability with Death Mark instead controlling how early in the target's health bar the conversion became possible. That would preserve investment without creating prolonged streaks where the player simply holds a button and waits for probability to cooperate.

Blizzard ultimately kept the random system, although it adjusted other parts of Bind Demon before release. Season 15 is now providing the first longer-term test of what that system feels like after multiple rounds of balance changes.

Lister Is Also About the Worst Demon to Stand Beside While Testing Probability

There is a practical reason this particular report sounds so painful. Lister the Tormentor is not a passive training dummy patiently waiting while the player studies the UI. He is the leader of Baal's final minion wave and is perfectly capable of making a stationary Warlock regret their statistical curiosity.

Bind Demon therefore creates a strange gameplay loop against valuable Super Unique targets. First, the Warlock needs to reduce the demon's Life enough to improve conversion odds without accidentally killing it. Then the player must channel near a dangerous enemy while waiting for a periodic success check. If the roll fails repeatedly, continuing to damage the demon increases the chance but simultaneously increases the possibility that it dies before being captured.

That can be an interesting risk/reward mechanic when it works cleanly. When the tooltip says 62% and the target still refuses to cooperate for half a minute, it starts feeling less like demon binding and more like trying to get a cat into a carrier.

A Larger Sample Would Tell Us Much More

The next useful step is not another forum post saying “same.” Warlock players need data. Take an eligible Super Unique, record its remaining Life, record Bind Demon and Death Mark hard points, note the displayed bind chance and count how many valid once-per-second checks occur before success. Repeat that across dozens or hundreds of attempts.

If a displayed 62% chance consistently produces something much closer to 10–20% success under identical conditions, Blizzard has a reproducible problem to investigate. If most attempts succeed quickly and the 30-second Lister incident turns out to be an extreme outlier, then the skill may simply have produced one spectacularly ugly RNG streak — or the tooltip may be presenting a value that is modified elsewhere in the process.

That distinction matters. Diablo II players are extremely familiar with bad luck looking like a bug. Yesterday we covered a player going more than 100 Herald kills without receiving a Sunder Charm, while another player's larger sample showed how wildly legitimate RNG streaks can vary. Bind Demon is different because the game displays an explicit percentage, but the lesson remains useful: anecdotal pain is evidence worth investigating, not automatically proof of broken mathematics.

The Bigger Problem May Be That the Tooltip Does Not Explain Enough

Even if Bind Demon is working exactly as Blizzard intended, the current discussion exposes a usability problem. Players see 62% and understandably assume the next eligible binding attempt has approximately a 62% chance to succeed. If that number is then modified by monster Life, monster tier, Death Mark investment, hidden defense interactions or some other internal rule, Diablo II needs to make that clearer.

A more useful tooltip could display the actual current final bind chance against the targeted monster rather than a generalized skill number. If Lister at 30% Life only has a 15% effective chance to bind despite the character sheet showing 62%, show 15% while the player targets him. If 62% really is the final per-check chance, then repeated 20–30 second failures become much more suspicious and easier for Blizzard to reproduce.

The worst outcome is the current one, where players cannot tell whether the skill failed because of bad RNG, insufficient target damage, an undocumented calculation or a bug.

Bind Demon Has Already Been Nerfed Enough That Reliability Matters

Before Patch 3.3, Warlock summoners could at least justify an awkward binding process with the extraordinary power of the demon they eventually captured. Blizzard has now corrected the unintended additional damage bonus, and summoner players say their bound demons are dramatically weaker in pinnacle content. That makes the acquisition experience more important, not less.

If the reward is weaker while the process of obtaining it remains unreliable and skill-point intensive, Bind Demon risks sliding from one of Warlock's defining fantasy mechanics into something players decide is simply not worth building around. Several post-3.3 Warlock threads are already moving toward pure Goatman/Tainted summons rather than relying on a bound Super Unique for the hardest content.

That would be an unfortunate outcome for the skill Blizzard literally named Bind Demon. Warlock should probably still want to bind demons.

For Now, 62% Is a Question Mark

There is not enough evidence to write “Bind Demon is bugged.” Blizzard has not acknowledged a success-rate problem, the skill has multiple variables that are poorly communicated, and one awful Lister encounter does not establish the true probability distribution.

But the report is specific enough to watch. Twenty hard points. Around level 40 Bind Demon after bonuses. A displayed 62% chance. Lister at roughly 30% Life. Continuous attempts for something approaching 30 seconds.

If the game is working correctly, Blizzard may need to explain what that 62% actually means.

If it really means what players think it means?

Lister has apparently discovered his own passive skill.

Statistical Immunity.

Sources

Diablo II: Resurrected Forums: 62% Bind Demon Chance Repeatedly Failing

Blizzard: Diablo II: Resurrected Season 15 and Patch 3.3

Blizzard: Patch 3.2 Bind Demon Changes

Diablo II: Resurrected PTR: Earlier Bind Demon Reliability Feedback

```

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 2 Player Kills 100 Heralds Without a Sunder — Is the Grind Too Harsh?

Diablo II players are usually very good at accepting terrible odds. This is a community that can spend an evening killing the same boss hundreds of times, find absolutely nothing useful and still describe the session as “not too bad.” Season 15's Heralds of Terror are testing even that relationship with probability. One player says they have now killed more than 100 Heralds without seeing a single Latent Sunder Charm, while other players in the same discussion describe runs stretching into the hundreds with only a handful of Sunders to show for it.

The problem is not simply that Sunder Charms are rare. Blizzard deliberately wants them rarer than they were before Reign of the Warlock, and Diablo II has never promised that 100 kills earns anything. The more interesting complaint is about risk versus reward. High-tier Heralds can stop powerful characters in their tracks, erase mercenaries, roll miserable combinations such as Thorns and Stone Skin, and sometimes take minutes to kill. When the reward at the end is two blue items your loot filter does not even bother displaying, the player is left wondering what exactly the fight was for.

One Player Has Passed 100 Heralds Without a Sunder

The current discussion began on August 28 with a player saying their Herald count had crossed 100 without producing a Sunder Charm. They describe deliberately farming Terror Zones in large multiplayer games and becoming increasingly frustrated by both the Sunder drought and the general quality of Herald drops. Other players immediately pointed out that a streak like this is entirely possible under Diablo II's RNG. One community calculation suggested that even if a Tier 5 Herald had roughly a 2% Sunder chance, going 100 kills without one would still not be remotely impossible.

That statistical point matters. A bad streak is not automatically evidence that Blizzard broke the drop table. We already covered the wider Season 15 changes to Sunder Charm farming, and Blizzard's Patch 3.3 notes specifically say that the Herald-specific Sunder drop rate was not reduced. What Blizzard did reduce was the effectiveness of Magic Find on Latent Sunder Charms obtained through the normal loot system, while also restricting those Magic Find drops to Hell difficulty and increasing the minimum drop level from 69 to 75.

So if Herald Sunders feel rarer, the current official patch notes do not support the simple explanation that Blizzard secretly nerfed their special Sunder chance in Season 15. The frustration is real. The cause may simply be Diablo being Diablo.

Another Player Logged 344 Herald Kills and Got Five Sunders

The strongest counterpoint in the thread comes from a player who has actually been counting. They report 344 total Herald kills, including 287 Tier 5 Heralds, resulting in five Sunder Charms. Their longest drought between Sunder drops was 133 Tier 5 kills; their shortest was only 11. They still believe Sunders are slightly too rare and say seven or eight across that sample would have felt healthier, but their results also demonstrate how wildly the experience can swing from one stretch to another.

This is why anecdotal Sunder farming can feel so brutal. Player A kills 11 Heralds and gets one. Player B goes 100 without anything. Player C reaches 133 before the next drop. All three may be interacting with exactly the same drop table. Random distribution has no obligation to make individual players feel that the mathematics are being fair.

Diablo II veterans understand that intellectually. The emotional response after the 100th unsuccessful Herald is usually less academic.

Season 15 Was Supposed to Make Heralds More Worth Fighting

This is where the complaint becomes more interesting than one unlucky Sunder streak. Patch 3.3 explicitly increased the chance for Tier 3 and higher Heralds to drop Rare-quality and better items. That change followed months of complaints that Heralds were disproportionately dangerous compared with the piles of blue items they often left behind.

Blizzard had already tried to improve the system in Patch 3.2. Heralds were made easier to spawn, the increased Sunder chance began at Tier 2 rather than Tier 4, player count stopped heavily modifying their special Sunder chance, and a failed special Sunder roll gained an increased chance to produce another desirable item such as a Charm or Amulet. Blizzard's developer note explicitly acknowledged that players felt both Herald spawn rates and Sunder drops were too low.

Season 15 then increased Rare-and-higher drops for Tier 3+ Heralds again. The direction is obvious: Blizzard knows these monsters have to feel worth killing.

Players are still debating whether they do.

A Tier 5 Herald Can Be Much Harder Than Its Loot Suggests

The strongest complaint in the current thread comes from players who do not mind Sunder Charms being rare but strongly dislike how punishing some Heralds can be relative to their ordinary loot. Multiple players specifically call out Thorns, while Stone Skin and other defensive combinations can dramatically extend the encounter. One Barbarian player describes fighting a Stone Skin Herald for several minutes despite using a Physical Sunder setup, only for the monster to drop basic blue equipment afterward.

Other players describe mercenaries dying almost instantly against particularly ugly combinations. That creates a direct Gold cost through resurrection, slows down the Terror Zone farm and increases the danger of continuing the run. One player summed up the problem neatly: if Heralds are going to remain this dangerous, their non-Sunder loot needs to reflect it. If their loot remains ordinary, perhaps the difficulty needs to come down.

Either approach is defensible. What feels bad is combining raid-boss enthusiasm with Fallen Shaman rewards.

The Grind Does Not End When a Sunder Finally Drops

There is another layer to the complaint that becomes easy to forget when discussing only the initial drop chance. Reign of the Warlock changed Sunder Charms from simple finished items into a deeper progression system. Getting a Latent Sunder is only the first roll. You then need the right element for your build, useful affixes and the additional resources required to upgrade it.

A player in the current discussion lays out the problem as RNG stacked on RNG. First the Sunder must drop. Then it must be the correct type. Then the player needs the relevant upgrade Runes. Then the resulting affixes need to be useful, with properties such as enemy resistance reduction, Magic Find, Gold Find and Faster Hit Recovery creating another layer of quality differences.

That system creates excellent long-term chase potential, but it also makes the first Sunder drought more painful. After 100 Heralds, you are not necessarily 100 kills away from finishing the item you want. You may only be 100 kills away from finally receiving the wrong one.

The First Sunder Is Particularly Important

Several players point out that the very first relevant Sunder can be the hardest part of progression because a Sunder itself helps unlock more efficient farming. A Fire build that cannot comfortably kill Fire Immunes has fewer viable zones and bosses than the same build after acquiring the appropriate Charm. Supporting equipment still matters, but breaking the immunity barrier can dramatically broaden the character's options.

That creates an awkward progression loop. The item that makes Sunder farming easier is the thing you are currently trying to farm without having one. Veteran Non-Ladder players may already own old Sunders and barely notice the problem, while a fresh Season 15 character experiences the new system from zero.

That distinction also feeds into our recent discussion about whether Diablo II's three-month Ladder seasons are too short. A long chase is easier to accept on a permanent character. It feels more demanding when the seasonal clock is already running.

Magic Find No Longer Solves the Problem the Same Way

Patch 3.3 also changed the relationship between Magic Find and Sunders. Blizzard says the effectiveness of Magic Find on Latent Sunder Charm drops was reduced, while the Herald-specific Sunder chance remained unaffected. That means stacking additional Magic Find does not directly improve the Herald's special Sunder roll in the way some players initially assumed.

This caused confusion immediately after the patch. Players experimented with different Magic Find levels and larger multiplayer groups expecting the old relationship to improve their odds, only to learn that the special Herald drop functions differently. Season 15 deliberately pushes players toward hunting Heralds as the more targeted Sunder route while making random Sunder discovery through the normal Magic Find system less generous.

That design makes Herald reward quality even more important. Blizzard is effectively telling players: if Sunders are your goal, this is the monster you should care about. If the monster then feels miserable to fight and rewards nothing useful most of the time, the targeted farming system begins to feel more like targeted disappointment.

Blizzard Does Want Sunders to Be Rare

It is worth remembering that Blizzard has already explained the broad philosophy. When Patch 3.2 increased Herald spawning and Sunder opportunities, the developers said the goal was to improve access while keeping Sunder Charms rarer than they were before Reign of the Warlock. That is intentional. The developers are not currently trying to make Sunders common seasonal starter gear.

There is a reasonable design argument behind that choice. The modern Sunder system is stronger and more elaborate than the original version. A well-rolled upgraded Sunder can become a serious endgame item rather than merely an immunity-breaking utility Charm. If those dropped constantly, the entire progression system surrounding them would collapse almost immediately.

The problem is finding the point where “rare enough to be exciting” becomes “rare enough that players stop bothering.” That line is notoriously difficult to see from a spreadsheet.

Better Backup Loot Could Solve Most of the Frustration

The best solution may not require dramatically increasing the Sunder rate at all. If Heralds consistently provided good fallback rewards, going 100 kills without a Sunder would still produce meaningful progress. Better chances at Uniques, Set items, useful Charms, Jewels, Runes or crafting resources could make the monster itself worth fighting regardless of whether the special drop appears.

Blizzard is already moving in that direction. Patch 3.2 added the improved consolation drop when the special Sunder roll fails, and Patch 3.3 further increased Rare-and-higher item chances for Tier 3+ Heralds. The community feedback suggests Blizzard may simply not have pushed that idea far enough.

One player proposes guaranteeing at least a Unique or Set item from Tier 5 Heralds. That might be too generous depending on how frequently they can be spawned, but the basic principle is sound: the hardest version of a specialized endgame monster should probably produce something visible enough that the player notices they killed it.

100 Kills Without a Sunder Is Bad Luck — But the Real Problem Is What Happened During Those 100 Kills

This is ultimately why the current thread is worth more than a headline about one unlucky player. Going 100 Heralds without a Sunder can happen. Depending on the actual hidden drop rate, it may not even be particularly extraordinary. Diablo II has always contained miserable streaks, and eliminating them entirely would mean eliminating much of what makes rare drops exciting.

The better question is whether those 100 Heralds delivered enough value along the way. If the player gained good Uniques, useful Charms, meaningful XP and other valuable drops, the missing Sunder becomes one unfinished chase among many. If the experience was 100 difficult encounters, dozens of dead mercenaries and a warehouse full of blues, the system feels broken even if the underlying probability is mathematically correct.

That is the strange thing about loot games. RNG does not have to be fair.

The grind still has to feel worth doing.

After 100 Heralds, some Season 15 players are no longer sure it does.

Sources

Diablo II: Resurrected Forums: 100 Heralds of Terror Without a Sunder

Blizzard: Diablo II: Resurrected Ladder Season 15 and Patch 3.3

Blizzard: Patch 3.2 Herald and Sunder Charm Changes

Diablo II: Resurrected Forums: Season 15 Herald Sunder Drop Discussion

```

Read More

Diablo Immortal Will Keep Removing Legendary Essences — Players Want Reworks Instead

Diablo Immortal has accumulated a lot of Legendary Essences. Four years of updates have given every class an increasingly enormous library of skill modifiers, forgotten experiments, old meta pieces and niche interactions that somebody, somewhere, probably still loves. Blizzard thinks that library has become too large. The solution is not merely to stop adding more. Legendary Essences will continue to be permanently retired from the game.

Blizzard first removed a wave of Essences in June, then admitted that it had done a poor job explaining why. An August Developer Diary was intended to provide the missing context, and the message is now very clear: retirement is a long-term design strategy. Blizzard plans to gradually reduce the total number of Essences until every class reaches what the developers consider a healthier and more stable pool. New Essences will continue arriving, but an old Essence disappearing does not necessarily mean another one will replace it one-for-one.

The community response has been equally clear. Many players understand the problem Blizzard is trying to solve. They simply think deleting old builds is the wrong solution.

Blizzard Wants a Smaller, Healthier Essence Pool

The developer's argument makes sense on paper. Every time Diablo Immortal adds another batch of Legendary Essences, the drop pool becomes larger, new players have more effects to understand, and individual additions have less impact because they are competing with years of existing options. Blizzard wants future updates to produce more noticeable changes instead of adding another collection of items that disappears into an increasingly crowded catalogue.

According to the Systems and Design team, Essences will not be retired simply because they are old. Blizzard says it will consider usage rate, build ecosystem health, gameplay diversity, design goals, upcoming content and the amount of useful design space an Essence occupies. The intended end state is a stable pool where each class still has meaningful build choices but does not carry every experimental Legendary modifier ever released.

That is a reasonable maintenance problem for a live-service ARPG. Diablo Immortal cannot add another dozen modifiers to every class forever without eventually creating something resembling a spreadsheet with combat animations attached. The controversial part is what happens to the player who built around the Essence Blizzard decides no longer deserves a chair.

Retired Essences Do Not Simply Stop Dropping

“Retired” is stronger than “removed from the loot pool.” Blizzard's August 12 retirement wave removed the affected Legendary items from future drops and rendered their Essences inactive. If you already had one unlocked, you did not get to keep using the old version indefinitely. A loadout built around that modifier could simply stop functioning as designed after the update.

That distinction is central to the backlash. Several players say they would be much less concerned if retirement meant removing old Essences from the general drop pool while preserving them for accounts that had already unlocked them. Others have suggested moving obsolete effects into an archive, legacy system or optional support slot. Blizzard instead wants the live build ecosystem itself to evolve, which inevitably means some existing builds will die.

Community Manager Jadai was unusually direct when challenged on that point. Responding to a player who argued that future retirement waves would continue breaking builds, Jadai essentially confirmed that both things are true: existing builds will break, and new builds will be created as new Essences arrive. Blizzard sees that turnover as part of an evolving game rather than a failure of the system.

Players Say That Is Forced Change, Not Build Diversity

This is where Blizzard and a large part of the community seem to be using the word “diversity” differently. Blizzard wants fewer but more meaningful options, with new Essences having enough room to change how classes play. Critics argue that removing old options cannot create diversity by definition. It narrows the number of possible combinations and forces players toward whatever Blizzard has decided should remain viable.

One player in the Developer Diary discussion described losing a build that relied heavily on the retired Wiltbloom Essence. Rather than discovering an exciting new option, they say the retirement destroyed the playstyle they preferred and pushed them toward changing class. Another response summarized the problem more broadly: releasing an interesting new Essence can tempt somebody into trying a new build; removing their old Essence forces them to.

Those are very different kinds of experimentation. One begins with curiosity. The other begins with opening your Armory and discovering that part of the build has been administratively deceased.

This Hits Harder in Diablo Immortal Than a Normal Balance Nerf

Live-service games change builds constantly. A skill loses damage. A cooldown increases. A Legendary Gem gets adjusted. Players complain for three days and eventually move numbers around. Essence retirement is more disruptive because it can remove the interaction itself. You are not necessarily dealing 8% less damage with the same build. You may no longer have the build.

That matters particularly in Diablo Immortal because character setups are connected to a much larger investment structure. Players collect Essences, Legendary equipment, Set pieces, Runes, Eternal Magic attributes and Legendary Gems around a specific playstyle. Some of those systems involve significant time investment, and for paying players they may involve significant money as well. Reconstructing a replacement setup is therefore more complicated than changing one skill point.

We saw a smaller version of that frustration in our recent look at the Wizard player who lost 46 million PvE damage after the August balance patch. That build still existed after the change; it simply performed worse. Essence retirement can go one step further and remove the mechanical piece that made the setup work in the first place.

Blizzard Says Low Usage Is Not the Only Factor

One fear in the community is that anything unpopular could eventually disappear. Blizzard says the process is more nuanced than that. Usage rate matters, but retirement decisions also consider whether an Essence contributes something healthy to the class, whether it overlaps too heavily with another effect, whether its design restricts future additions and whether Blizzard believes the gameplay itself should continue existing.

That opens the door to another solution players keep suggesting: rework weak Essences instead of deleting them. If an old modifier has extremely low usage because its numbers are poor or its slot competes with a mandatory damage option, move it, buff it or redesign it. Blizzard has already indicated that this can happen in individual cases. During the retirement discussion, Jadai responded to criticism of one Crusader effect by saying the design might work better as a support Essence in another slot and that the team wanted to bring that functionality back in a different form.

That response is important because it proves retirement and rework do not have to be mutually exclusive. Blizzard can identify a useful gameplay idea trapped inside an outdated Essence and preserve it somewhere better. Many players simply want that philosophy applied more broadly.

The August 12 Wave Made the Policy Real

The Developer Diary was not hypothetical. Blizzard followed it with another retirement wave on August 12, publishing a class-by-class list of Legendary equipment whose Essences would become inactive after the update. As an acknowledgement of the negative reaction surrounding the earlier June removals, Blizzard also mailed players five Legendary Crests as a thank-you for their feedback.

Free Crests are free Crests. Nobody is likely to throw them back.

They also do not reconstruct a deleted loadout.

One player in the continuing discussion explained that after an Essence disappeared, their saved Armory setup was left with a blank slot and no easy way to remember exactly which item, Gem, Rune and stats had previously occupied it. They ended up relying on handwritten notes to rebuild something close to the old configuration. That is a very specific quality-of-life problem Blizzard could address even if it refuses to reconsider retirement itself.

Blizzard Is Not Planning Separate PvE and PvP Retirement Rules

The Developer Diary FAQ also contains an important detail for players hoping their niche PvE setup might be protected simply because it causes no competitive problems. Blizzard currently has no plan for completely separate PvE and PvP Essence-retirement rules. Future updates may target different gameplay directions, but the retirement system itself is intended to manage the overall Legendary ecosystem.

That makes the policy particularly relevant after the recent balance controversies. The August 26 patch already demonstrated how difficult it is to make one Essence work across Battlegrounds, raids and tournament PvP. We covered that from another angle when players worried the Warlock nerf would simply push the competitive meta toward Demon Hunter. Essence retirement gives Blizzard a much more permanent tool: instead of endlessly balancing an unhealthy modifier across every mode, the team can eventually decide that the game would be healthier without it.

From a systems-design perspective, that flexibility is attractive. From the player's perspective, it means no existing niche build can assume its key Essence will remain available forever simply because it is harmless outside one activity.

Could Blizzard Remove Essences From Drops Without Deleting Them?

One of the strongest compromises suggested by players would separate loot-pool management from build availability. Blizzard's complaint that too many Essences dilute drops is valid, but permanent deactivation is not the only way to solve that. Old Essences could move into a Legacy collection after they are extracted. New players could unlock them through a separate vendor or archive system, while standard Legendary drops remain focused on the current pool.

That would allow Blizzard to keep the active loot table manageable without destroying every old build. It could even create a rotating system where retired Essences occasionally return, much like live-service games rotate older cosmetics or seasonal content back into availability.

The obvious downside is maintenance. Every Essence preserved forever remains something Blizzard must consider when designing future items, skills and balance changes. A supposedly “legacy” interaction can still combine with a new Essence three years later and create something deeply unreasonable. Blizzard's desire to reclaim design space is therefore not solved entirely by hiding old modifiers from the drop table.

Diablo Immortal Has a Four-Year Accumulation Problem

This may be the larger issue behind the entire policy. Diablo Immortal was never designed to stop receiving content. New Legendary Essences arrive repeatedly, and every batch increases the number of interactions the developers must test against every future batch. The game is now old enough that the cost of never removing anything is becoming visible.

Traditional Diablo games largely avoid this problem because their item pools eventually stabilize. Diablo Immortal behaves more like an MMO. Its classes are expected to continue evolving indefinitely, which means Blizzard eventually has to choose between permanent accumulation and some kind of rotation.

The question is not whether an infinitely growing Essence pool eventually becomes awkward. It obviously does. The question is whether Blizzard's solution should feel like pruning a tree or replacing the garden while somebody is still sitting in it.

New Essences Do Not Necessarily Replace the Old Ones One-for-One

Another source of anxiety is that retirement does not guarantee numerical replacement. Blizzard says future updates may simultaneously remove old Legendary affixes and introduce new ones, but retiring one does not mean one new Essence automatically appears in the same slot or fills the same gameplay role.

That gives Blizzard freedom to reduce the total pool gradually until it reaches the desired size. It also means a class can temporarily lose more options than it gains during a particular wave. For players already skeptical of retirement, this is probably the least reassuring sentence in the FAQ.

The long-term promise is quality over quantity: fewer Essences, but each one should create more meaningful gameplay differences. Whether Blizzard can deliver enough genuine build diversity inside that smaller pool is the part we cannot evaluate yet.

Reworks Would Make Retirement Much Easier to Accept

The community is not universally demanding that every forgotten 2022 Essence remain immortal. Some modifiers really are obsolete. Some have been power-crept beyond relevance. Others occupy valuable equipment slots despite offering effects almost nobody would intentionally choose. Cleaning those up can make the game easier to understand.

The strongest criticism is therefore not “never change anything.” It is that retirement should be the final option after Blizzard has considered updating, combining or relocating the useful parts of an Essence. If an effect supports a genuinely distinct playstyle, preserve that playstyle even if the original item disappears. If an Essence is simply an inferior numerical version of something newer, retirement becomes far easier to justify.

That approach would also make Blizzard's stated goal of build diversity easier to believe. Players care less about the name printed on an old Legendary than they care about what it lets their character do.

Blizzard Has Chosen Evolution Over Preservation

The most important thing in the Developer Diary is not the exact list of Essences being removed next. It is that Blizzard has now clearly chosen a philosophy. Diablo Immortal's class systems will not preserve every build forever. The Legendary ecosystem is intended to change, shrink and replace itself over time.

Blizzard knows that means some builds will stop working. The developers have acknowledged the friction and say the decision itself was made months ago and is not being reversed simply because the first retirement waves were unpopular. What Blizzard says it can improve is communication: earlier warnings, clearer reasoning and more transparency about what is disappearing and why.

That is better than waking up to a broken Armory loadout without explanation. It does not solve the underlying disagreement.

Players asking for reworks are essentially saying that a live-service RPG should evolve by adding possibilities. Blizzard is saying that after four years of accumulation, meaningful evolution sometimes requires removing them too.

Both positions make sense.

Only one of them gets to choose what remains in the game.

For now, that means Diablo Immortal players should probably stop treating every Legendary Essence as permanent property.

Some of them are apparently renting.

Sources

Blizzard Systems and Design Team: Dev Diary — Retiring Essences and the Future

Blizzard: Legendary Essences Retired on August 12

Reddit: Community Discussion of Essence Retirement

```

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

Diablo Immortal Wizard Player Loses 46 Million PvE Damage After Balance Patch

Diablo Immortal's August 26 balance patch was announced just before Bout of Realms, so most of the immediate conversation naturally focused on PvP. Warlock changed. Wizard changed. Several other classes changed. Teams suddenly had new compositions to think about. But one Wizard player has now highlighted the awkward side effect of balancing skills that exist in both competitive and PvE content: their one-minute Boss Dummy damage dropped from 760 million to 714 million after the update.

That is a loss of roughly 46 million damage, or just over 6%, in a test the player says was performed against the same target using the same PvE setup before and after the Disintegrate changes. One player's dummy test is not enough to declare that every Wizard in Diablo Immortal has lost exactly 6% of its raid damage. Builds, equipment, Resonance and skill combinations vary enormously. But the result adds substance to a complaint Wizard players have been making for months: changes aimed at controlling the class elsewhere can keep removing pieces from PvE builds that were not dominating anything to begin with.

Blizzard Changed Searing Judgement on August 26

The relevant change involves the Wizard Legendary Essence Searing Judgement. It modifies Disintegrate so the beam channels Fire and applies a stacking Burn. Under the revised version, that Burn can now stack to five before being consumed for additional damage. Blizzard also reduced the beam's distance and increased the maximum number of stacks, meaning the bonus damage triggers less frequently. The developer says the damage of that trigger was increased specifically to help compensate for the lower frequency.

On paper, that is not simply a raw damage nerf. Blizzard reduced one part of the mechanic and increased another. The intent appears to have been to alter how the beam performs rather than simply delete damage. The problem is that the player testing the finished patch says the compensation did not compensate enough for their PvE setup.

Before the change, their Wizard produced 760M damage in one minute against the Boss Dummy. After the patch, the same test produced 714M. That works out to approximately 46M less total damage during the minute, which is substantial enough to notice in a build constructed around sustained raid DPS.

This Is Not the First PvE Damage Loss the Same Player Has Documented

The frustration becomes easier to understand when you look at the player's previous reports. On August 12, the same Wizard player documented another significant PvE decline after Blizzard removed the Chaosrupture essence. Their one-minute dummy result reportedly fell from more than 600M to more than 540M, and they described a longer progression in which the same general Wizard raid setup had moved from above 700M to around 600M and then into the 540M range following successive essence and set changes.

That history is why the new 46M loss is being treated as more than an isolated numerical adjustment. From the player's perspective, the problem is cumulative. A PvE build gets assembled around one interaction, that interaction changes or disappears, another build takes its place, and then the replacement gets hit by a later balance pass. Eventually the frustration is not that one patch reduced damage. It is that rebuilding the same class begins to feel like seasonal maintenance.

We have seen a similar conflict from the PvP side of this exact update. Our look at the Warlock nerfs and the fear that Demon Hunter would simply inherit the PvP meta showed how difficult it is to change one dominant interaction without moving pressure somewhere else. Wizard illustrates the other half of the problem: a balance adjustment can make sense competitively while still creating collateral damage in PvE.

Blizzard Says These Changes Were Not Made Specifically for Bout of Realms

There is an important clarification here. Because the balance patch was announced immediately before Bout of Realms, it would be easy to describe the Wizard change as a tournament nerf that accidentally escaped into PvE. Blizzard has explicitly said that is not what happened. Community Manager Jadai clarified that the changes were not created specifically for Bout of Realms; they are normal permanent balance changes that also affect the tournament.

Blizzard announced them early because competitive teams needed additional time to reconsider compositions, equipment and strategy before the event. That means Searing Judgement was always intended to change across the broader game, including PvE. The question is therefore not whether a PvP-only adjustment mistakenly leaked into raids. The question is whether one version of an Essence can be balanced satisfactorily across very different activities.

The Reduced Range Is Part of the Complaint Too

Damage is only one side of the Wizard feedback. Blizzard also reduced Disintegrate's beam distance, and players had already raised concerns about that change before it went live. One forum thread pointed out that Wizard has existing Disintegrate Essences designed around ranged play and argued that shrinking the beam pushes an archetypal ranged class closer to enemies at exactly the moment many other classes have gained strong mobility, immunity or ranged-pressure options.

That complaint is more subjective than a dummy number, but it connects to a broader identity problem. If Wizard's ranged options are repeatedly shortened or weakened while its defensive tools remain limited, players can feel they are being encouraged to play closer to enemies without receiving the durability expected of a melee-oriented class. Whether Blizzard agrees with that diagnosis is another question, but it helps explain why a 46M dummy loss has generated more frustration than the percentage alone might suggest.

A 6% Loss Is Not the Same as “Wizard Is Dead”

It is worth applying some brakes here. A reduction from 760M to 714M does not make the build unusable. The Wizard still dealt more than 700 million damage during the test. We also do not have controlled measurements from a large sample of Wizard players using different Searing Judgement setups, so the result should not be treated as a universal class-wide coefficient.

Boss Dummy results can also be sensitive to rotation, proc timing and short-term variance. Even when a player performs the test carefully, one minute is a relatively small window in a game full of conditional bonuses. The useful conclusion is therefore narrower: this particular established PvE Wizard build produced measurably less damage after the August 26 Disintegrate adjustment.

That is still worth discussing because Blizzard's own developer note says the increased damage was supposed to help offset the less frequent Burn trigger. For this setup, the net result remained negative.

PvE and PvP Probably Need More Separation

This brings Diablo Immortal back to a problem shared by almost every live-service RPG with competitive modes. A skill can be too frustrating in PvP without being too strong in PvE. The obvious solution is separate tuning, and Diablo Immortal already uses mode-specific scaling in various parts of its combat system. Expanding that philosophy would let Blizzard reduce problematic range, crowd control or burst behavior against players while preserving the damage profile that keeps a PvE raid build functional.

There are complications. Maintaining multiple versions of every Essence can become a balancing nightmare, and players already have enough tooltips to read without adding a small legal contract explaining what their beam does in six different activities. But the alternative is exactly what Wizard players are complaining about now: a build that is not considered a PvE problem can lose damage because an interaction needed adjustment somewhere else.

The same patch demonstrates how many competing goals Blizzard is trying to satisfy at once. It arrived alongside the new Bout of Realms format with its brutal six-match opening stage, while also changing Warlock, Crusader, Druid, Monk, Tempest and Wizard. A single balance pass has to serve casual PvE, raids, Battlegrounds and Diablo Immortal's most competitive tournament. That is a lot of jobs for one set of numbers.

The Frustration Is Really About Rebuilding the Same Class Again

The strongest part of the Wizard complaint is not “46 million damage is unacceptable.” It is the sense that PvE players keep needing to rebuild around disappearing pieces. The same player says previous raid setups were weakened by changes to Terminus-related builds, Endwinter and Chaosrupture before the current Fire Disintegrate setup took another hit. Even if every individual change can be defended in isolation, repeated disruption eventually makes class investment feel temporary.

That matters more in Diablo Immortal than it would in a game where changing builds is free and instant. Players invest in Essences, Legendary Gems, Eternal Magic attributes, gear and sometimes real money around particular class setups. When an important interaction changes, the damage number is only the visible part of the cost. The player may also have spent weeks building equipment around the thing that no longer performs the same way.

That is particularly uncomfortable when another class appears capable of producing better raid results without receiving equivalent reductions. The forum claim that Demon Hunter and Blood Knight outperform Wizard in raids is player opinion rather than an official Blizzard ranking, and we should treat it as such. But perceptions of relative power matter. A 6% nerf feels very different when you believe you were already behind.

Blizzard May Have Achieved the Intended Balance Change — Just Not for This Build

There is also a perfectly plausible explanation that does not involve Blizzard forgetting PvE exists. Searing Judgement may simply have been outperforming Blizzard's intended overall power budget once its range, Burn timing and other interactions were considered together. Increasing the five-stack payoff while reducing how often it occurs may produce healthier results across a wider collection of content even if one optimized dummy setup loses several percent.

That is what broader balance passes do. They are not designed to preserve every existing build's exact benchmark. The problem is communication. If Wizard PvE is expected to lose damage because Blizzard believes the Essence was too strong everywhere, say so. If PvE was supposed to remain roughly neutral, the 760M-to-714M test becomes useful feedback that the compensation may need another look.

One Dummy Test Has Turned Into a Much Bigger Wizard Argument

The forum thread itself is small, but it plugs into a much larger Wizard conversation. Other recent Wizard feedback complains about reduced mobility, long cooldowns, lack of sustain and a gradual push toward shorter-range gameplay. The August 26 balance thread also contains Wizard players arguing that the class feels increasingly irrelevant compared with newer or more durable alternatives.

None of that proves the class is objectively weak in every mode. Communities are rarely calm laboratories of controlled testing immediately after a patch. But repeated feedback around the same themes is useful. Players are not only asking for more damage. They are asking Blizzard to decide what Wizard is supposed to be good at.

If it is a fragile ranged damage dealer, ranged tools should probably feel rewarding. If Blizzard wants Wizard fighting closer to enemies, survivability may need to reflect that. And if a PvP adjustment costs an established raid build another measurable chunk of damage, players understandably want to know what they are getting in return.

For Now, the Number Is 46 Million

The August 26 patch has only been live for a few days, so broader testing may reveal Wizard setups that compensate for the changes more effectively. Players may adjust rotations. Different Essences may emerge. Blizzard may decide the current numbers are exactly where it wants them. Or enough PvE data may show that Searing Judgement needs another pass.

For now, we have one unusually clean before-and-after example: 760M before, 714M after, same player's one-minute Boss Dummy test. That is not enough to sentence the entire Wizard class to death, but it is enough to demonstrate that the latest balance changes were not PvE-neutral for everybody.

And for Wizard players who already rebuilt after the last PvE loss, that is probably the part that hurts most.

The spell still works.

The build still works.

It just works 46 million damage less than it did on Tuesday.

Sources

Blizzard: August 26 Diablo Immortal Balance Changes

Diablo Immortal Forums: Wizard Player's 760M vs. 714M Boss Dummy Test

Diablo Immortal Forums: Earlier Wizard PvE Damage Loss After Chaosrupture Removal

Diablo Immortal Forums: Searing Judgement Range and Wizard Design Feedback

```

Read More