Diablo news and guides

Diablo 4 Heads Into BlizzCon With Its Recent Steam Reviews Back at “Mixed”

2026-09-11T02:01:35.009-07:00

Blizzard is heading into its biggest Diablo weekend of the year with one slightly awkward number following behind it. Diablo IV's recent Steam reviews are currently back at “Mixed,” with 68% of 509 English-language reviews from the last 30 days giving the game a positive rating. That is not a catastrophe. The game's wider English review score remains “Mostly Positive” at 74%, and Steam represents only one corner of a considerably larger Diablo IV audience spread across Battle.net, Xbox and PlayStation. But one day before Blizzard takes the BlizzCon stage to reveal what it calls “extensive plans” for Sanctuary, the recent rating offers a useful reminder: Blizzard is not walking into Anaheim with a player base that has unanimously decided Diablo IV is fixed.

Tomorrow is therefore about more than announcing something shiny. Blizzard has to make people want to come back.

Diablo 4's Recent Reviews Are Sitting at 68%

At the time of writing, Diablo IV's Steam page shows 509 recent English reviews, with 68% positive. Steam classifies that result as Mixed. Across the game's broader English review history, 74% of more than 20,000 reviews are positive, enough for a Mostly Positive rating.

That six-point difference is not enormous, but the direction matters. Recent players are currently less enthusiastic than Diablo IV's Steam audience has been overall.

And this comes at the end of a season that has already looked unusually quiet on the platform. Earlier this month, we examined Diablo IV's Steam player count falling into the low thousands ahead of Season 15. That number should never be mistaken for Diablo IV's complete population, but combined with the current review score it paints a fairly straightforward picture: Steam players are waiting for a reason to become excited again.

This Is Not Another “Diablo 4 Is Dead” Story

There is an important distinction here because Diablo discussion occasionally develops the subtlety of a Barbarian solving a locked door. Mixed reviews do not mean Diablo IV is dead. They do not mean 32% of every player in Sanctuary hates the game. They do not tell us how Battle.net players feel, and Steam review percentages can move quickly when new content, sales and returning players arrive.

They do tell us that the most recent Steam audience remains divided.

That is considerably more interesting.

Diablo IV has spent three years in a strange position where individual systems can improve dramatically while the broader conversation remains unsettled. Loot h

Diablo Immortal Is Crossing Over With Spawn — And That’s Only Part of Its Next Major Update

2026-09-11T01:46:05.154-07:00

Diablo Immortal has spent four years proving that there is apparently no upper limit to how many things can happen in Sanctuary at once. Its next major update continues that noble tradition. Blizzard has revealed the first details of Made to Suffer, continuing the Nation in Agony storyline with a new part of Lut Gholein, another battle involving Andariel and Duriel, new Legendary Gems and further Battleground changes. And then, almost casually, Blizzard announced that Spawn is coming to Diablo Immortal. Yes, Todd McFarlane's chains, hellfire and necroplasm-powered antihero is crossing into Sanctuary this fall, because apparently Diablo looked at Spawn and concluded that what the man really needed was slightly more Hell.

The announcement comes through Blizzard's first official look at Made to Suffer, with the full patch notes scheduled for September 14. Spawn does not yet have an exact event date, reward list or cosmetic breakdown, so there is still plenty Blizzard is keeping hidden. What we do know is that this will be a limited-time crossover built around the character's familiar chains, hellfire and necroplasmic powers, with Blizzard promising a proper first look later.

Spawn Might Be the Most Natural Weird Crossover Yet

Diablo Immortal has never been particularly shy about collaborations, but Spawn feels unusually comfortable inside Sanctuary. Todd McFarlane's character has spent decades dealing with Hell, demons, infernal bargains, grotesque monsters and supernatural violence. Compared with some gaming crossovers where a guest character arrives looking like they accidentally walked through the wrong convention door, Spawn barely needs directions.

Blizzard describes the event as a collision between worlds, with Spawn preparing to leave his mark on the Eternal Conflict. That is deliberately vague, and right now we do not know whether the crossover will include playable transformations, cosmetics, boss encounters, story content or some combination of those things. The sensible move is therefore to enjoy the concept without inventing the feature list ourselves.

Chains and Hell are confirmed.

Everything beyond that can wait.

Lut Gholein Is Getting Bigger Again

The Spawn reveal risks overshadowing what is actually a fairly substantial update to Diablo Immortal's current story. Nation in Agony continues inside Lut Gholein, where Blizzard is opening a new area called the High Ward. The district surrounds Sultan Jerhyn's palace and is described as a once-prosperous section of the city now being consumed by the spreading darkness.

That continues the expansion of Lut Gholein that began with The Taking and its new Rocky Waste storyline earlier this year. Immortal has gradually been turning one of Diablo II's most recognizable locations into something considerably larger than a nostalgia backdrop, and Blizzard says the final portion of the Lut Gholein zone will arrive toward the end of the year.

For a game originally dismissed by plenty of Diablo players as the mobile side project, Immortal has become rather enthusiastic about expanding Sanctuary's actual geography.

Andariel and Duriel Are Now Fighting Over Who Gets to Ruin Your Afternoon

The Rocky Waste is also getting a new zone event called Twisting Torments. Andariel and Duriel are effectively competing over whose particular flavor of misery should dominate the area, causing their influence to spill across the region. Enemy groups become empowered by Pain or Anguish-themed affixes, including Andariel's chains and Duriel-style maggot-spawning effects.

Players who defeat these empowered enemies will receive increased rewards, including a weekly Legendary equipment drop. It is the sort of Diablo setup that sounds very serious in lore terms and considerably simpler once translated into player language: two Lesser Evils are having an argument, please kill everything until loot falls out.

Two New Legendary Gems Are Coming

Made to Suffer also introduces two Legendary Gems. Enigma Latera is a new 5-Star Gem built around a Primary Attack effect called Cruel Enigma, which chains between enemies, increases damage against affected targets and reduces the damage they deal. More unusually, the effect can steal several seconds from one of an enemy's non-Skill beneficial effects and give that benefit to you instead.

The second Gem, Prong Crag, is a 2-Star option focused on surviving heavy incoming hits. Taking sufficiently large single-hit damage builds Resolve, increasing damage dealt while reducing subsequent damage from that source, while also improving Critical Resistance.

Diablo Immortal certainly does not suffer from a shortage of build pieces. Blizzard recently added 60 new Legendary Affixes across its ten classes, so anyone hoping the September update might provide an opportunity to finish organizing their builds has once again misunderstood the game they are playing.

Battlegrounds Are Going Back to Their Nephalem Look

Blizzard is also changing Battlegrounds again. The current demonic invasion theme is ending, returning PvP to the familiar Nephalem visual style while retaining some changes players responded positively to. The Final Guardian mechanic is effectively moving back toward its previous form: defeating the Final Guardian grants the entire team Nephalem Power, allowing players to execute enemies below 20% Life even through effects such as Undying and invulnerability.

That continues a year in which Blizzard has spent considerable effort adjusting Immortal's competitive side. Earlier updates experimented with equalized PvP and broader Battleground changes, which matters in a game where competitive balance and account power have never exactly enjoyed a quiet relationship.

And Blizzard Is Already Teasing What Comes After Spawn

The roadmap does not stop with Made to Suffer. Blizzard says the Spawn collaboration will be followed by a Halloween celebration, which will then lead into a special Diablo 30th Anniversary event the studio is not ready to discuss yet. Later in the year, Nation in Agony will reach its conclusion alongside the final section of Lut Gholein and additional Helliquary bosses.

All of this also lands around the same period as Diablo Immortal's substantial engine upgrade, which overhauls lighting, environmental materials and visual effects across the game. Put together, September is looking less like another routine Immortal patch and more like the beginning of a fairly busy final quarter.

Spawn is inevitably going to get most of the attention.

That is what happens when you invite a cape-wearing corpse powered by Hell into a Diablo game.

But underneath the crossover is a proper expansion of Immortal's current storyline, a larger Lut Gholein, new build options, another PvP revision and a roadmap stretching through Diablo's 30th anniversary.

Apparently Sanctuary was not busy enough already.

Blizzard Said Diablo Fans Would “Freak Out” at BlizzCon — Tomorrow We Find Out Why

2026-09-11T01:17:13.146-07:00

Seven months ago, Diablo IV Game Director Brent Gibson accidentally, deliberately or perhaps very conveniently gave Diablo players one sentence to carry all the way to BlizzCon. At the very end of February's Diablo 30th Anniversary Spotlight, with the presentation apparently finished, Gibson looked away from the camera and said: “They're gonna freak out at BlizzCon when we announce…” Then the video ended. Blizzard never completed the sentence. Diablo players, naturally, have spent the intervening months completing it approximately fourteen thousand different ways.

Tomorrow we finally find out whether the missing words justified all of that attention. BlizzCon 2026 begins on Saturday, September 12, and Blizzard is no longer being particularly subtle about Diablo's importance to the show. The company's official Diablo BlizzCon preview says Diablo will take center stage during the Opening Ceremony to reveal “extensive plans” for the future of Sanctuary. A dedicated Diablo Developer Update follows later Saturday, while Sunday brings the Diablo IV: What's Next presentation we have been watching particularly closely. Whatever Gibson was talking about in February, Blizzard has built a very comfortable stage on which to finally explain it.

The Quote Really Happened

This is worth establishing because pre-BlizzCon season has now reached the point where genuine developer comments, datamining, anonymous claims and screenshots that have been passed through three image enhancers tend to end up living in the same drawer. Gibson's remark is not one of those questionable leaks. You can hear it yourself at the end of the official Diablo 30th Anniversary Spotlight broadcast. The camera was still rolling, Gibson appeared to believe the segment was essentially finished, and the sentence stops exactly where everyone would prefer it not to.

What it does not tell us is what Blizzard plans to announce. “They're gonna freak out” describes an expected reaction, not a product. It could refer to Diablo IV. It could concern another Diablo game. It could be a new class, an expansion, a returning location, a classic-game project or something nobody has currently managed to datamine from a menu file.

That last possibility would almost be refreshing.

Blizzard Has Since Made the Tease More Interesting

If Gibson's sentence existed completely on its own, it would be easy to treat it as developers being enthusiastic about their own convention. What has happened since February is what makes the remark considerably harder to forget. When Blizzard opened the Season 15 PTR, the company explicitly warned players that the test realm did not contain everything coming next season. Blizzard said this was intentional because it had more to share at BlizzCon and did not want all of Season 15 available before the team had the chance to discuss it.

That admission has powered much of the speculation we have been following over the past month. Our look at the hidden Season 15 content and possible Westmarch connection grew directly from the fact that Blizzard itself told us something was missing. The important distinction is that the missing content is confirmed. Westmarch, Malthael and practically everything players have subsequently tried to put inside that empty space are not.

BlizzCon should finally separate those two categories.

Diablo 4 May Not Be the Only Game Involved

There is another reason not to automatically translate Gibson's unfinished sentence into “Diablo IV expansion three.” Blizzard's Saturday presentation is called Diablo: Developer Update, not Diablo IV: Developer Update, and this year's convention is celebrating the franchise's 30th anniversary rather than a single game.

The original Diablo will even be playable on the convention floor. That detail added another piece to the increasingly curious Diablo 1 remaster speculation we have been tracking, especially alongside Blizzard's unusually strong focus on legacy games. Diablo II: Resurrected has already received Reign of the Warlock this year, proving that Blizzard is willing to reopen games many players assumed were essentially complete.

None of that means Gibson was talking about Diablo 1 either. It simply makes the possibilities wider than “which Season 15 feature was missing from the PTR?”

Players Have Had Seven Months to Invent Answers

The community theories have consequently become wonderfully expansive. Another Diablo IV class is one of the obvious candidates. Demon Hunter has been discussed because of the unexplained Hand Crossbow data. Amazon makes almost suspiciously good narrative sense now that Lord of Hatred has taken players into Skovos and expanded the Askari. A third Diablo IV expansion remains an obvious possibility simply because Blizzard has every reason to continue the game's commercial roadmap.

Then there are the larger swings: a Diablo 1 remaster, more Diablo II content, a completely separate Diablo project or something new built around the franchise's anniversary.

The problem is that Gibson's quote can support almost all of those theories equally well, which means it does not actually prove any of them.

It is a magnificent hype generator.

It is a terrible source of specifics.

Blizzard Is Clearly Expecting People to Watch

The scale of Blizzard's viewing push suggests the company is comfortable with those expectations. As we covered earlier this week, Diablo IV's BlizzCon Twitch Drops require six cumulative hours of viewing, with weapon cosmetics unlocking at two, four and six hours. Blizzard is not treating Diablo as a twenty-minute seasonal footnote squeezed between larger announcements.

The official schedule gives Diablo prominent Opening Ceremony time, a franchise Developer Update, an art presentation, Sunday's What's Next panel and additional creator programming. Blizzard has also explicitly described the Opening Ceremony as containing major game announcements.

There is clearly something to talk about.

Whether it is something capable of making everyone “freak out” is the question Gibson accidentally left us with.

Tomorrow the Sentence Finally Gets an Ending

Pre-BlizzCon speculation is fun precisely because everything still fits. The Amazon theory fits. A Diablo 1 announcement fits. Another expansion fits. Season 15 surprises fit. If you move enough pieces around the board, practically anything except Diablo Kart can currently be made to look plausible, and somebody is probably working on that one too.

Tomorrow the board gets considerably smaller.

The useful facts are these: Brent Gibson really did tease a BlizzCon announcement in February. Blizzard really did hold some Season 15 content back specifically for BlizzCon. The company really is promising extensive plans for Sanctuary during Saturday's Opening Ceremony.

Everything after that remains speculation.

For one more day.

Seven months ago, Blizzard cut the video before Gibson could finish his sentence.

On Saturday, September 12, we finally get to hear the rest of it.

Diablo 4 Just Dropped to $12.49 on Steam Right Before BlizzCon

2026-09-11T00:58:45.473-07:00

Diablo IV has apparently decided that the traditional way to prepare for BlizzCon is to become extremely cheap. Blizzard's action RPG is currently 75% off on Steam, dropping the Standard Edition from $49.99 to just $12.49. The promotion is labelled as a Weekend Deal, although Steam currently lists the end date as September 24, giving players considerably more than a weekend to decide whether Sanctuary is worth approximately the price of a moderately ambitious lunch. More interestingly, the discount arrives immediately before BlizzCon 2026, where Blizzard has already promised substantial news about the future of Diablo.

The timing does not prove that the sale is connected to any particular announcement, and we should probably establish that before somebody decides $12.49 confirms Diablo V. Publishers discount games around major events all the time, particularly when they are about to put those games in front of a very large audience. But it is still difficult to imagine a better moment to lower Diablo IV's barrier to entry. BlizzCon begins tomorrow, Diablo has a major Opening Ceremony presence, Saturday includes a Developer Update, and Sunday brings the dedicated Diablo IV: What's Next presentation that Blizzard has deliberately surrounded with unanswered Season 15 questions.

$12.49 Is a Very Different Diablo 4 Purchase

The Steam offer applies to the Diablo IV Standard Edition. At 75% off, the current US store price is $12.49 instead of $49.99. That does not include every expansion ever released, but for anyone who has spent the last three years watching Diablo IV from a safe distance while the rest of us debated tempering, loot systems, seasonal mechanics and the correct number of demons required per square metre, this is an unusually inexpensive way in.

There is also a separate promotion on Lord of Hatred. Steam currently lists the expansion's Standard Edition at $29.99, down 25% from $39.99, and the US PlayStation Store is showing the same $29.99 price with the offer ending September 24. The larger Age of Hatred Collection, which bundles Diablo IV, Vessel of Hatred and Lord of Hatred, is still listed at its normal $69.99 Steam price at the time of writing.

That distinction matters. This is not Blizzard simply cutting 75% from everything carrying the Diablo IV name. The most dramatic discount is specifically on the base game, which makes considerably more sense if the goal is to get new or returning players through the front door.

The Sale Arrives at an Interesting Moment for Diablo 4

Diablo IV could use fresh bodies in Sanctuary. Earlier this month we looked at how Diablo IV's Steam concurrent player count had fallen into the low thousands late in Season 14. Steam is only one platform and cannot represent Diablo IV's total population across Battle.net, Xbox and PlayStation, but the trend still showed a game deep in the quietest part of its seasonal cycle.

BlizzCon offers Blizzard an opportunity to change that conversation. Season 15 is approaching, some of its content was deliberately withheld from the PTR, and the company says its Opening Ceremony will reveal extensive plans for Sanctuary. Blizzard is also encouraging people to watch for a long time, with three Diablo IV BlizzCon Twitch Drops requiring six cumulative hours of viewing. Lowering the base game's price to $12.49 immediately before all of that is not exactly subtle marketing.

It is also sensible marketing.

A spectacular BlizzCon trailer is considerably more useful if somebody watching it can immediately buy the game for twelve dollars rather than putting Diablo IV on a wishlist and reconsidering their life choices later.

This Does Not Tell Us What Blizzard Is Announcing

We should resist turning the sale itself into another BlizzCon leak. Over the last week almost every unexplained Diablo detail has been recruited into one theory or another. Hidden Season 15 content has produced Westmarch speculation. A Hand Crossbow entry has been used to argue for Demon Hunter. Skovos lore has helped create an increasingly loud Amazon theory. Even an undocumented game update now has players wondering whether Blizzard quietly installed something ahead of the convention.

A discount is much less mysterious. Diablo IV is approaching a major marketing weekend, and putting the base game on sale makes it easier to convert attention into players. Blizzard does not need a secret third expansion or surprise class to justify that strategy.

But the timing still makes the deal much more interesting than an ordinary seasonal promotion.

If You Were Waiting, $12.49 Is Hard to Ignore

Diablo IV has changed enormously since launch. Whether every change improved it is the sort of question capable of consuming an entire forum for several working days, but the game players enter in 2026 is certainly not the same one released in June 2023. Multiple seasons, itemization reworks, endgame changes and expansion systems have fundamentally reshaped the experience.

At $49.99, someone who has avoided Diablo IV for three years may still decide to continue avoiding it with admirable consistency.

At $12.49, the calculation becomes rather different.

And if Blizzard walks onto the BlizzCon stage tomorrow with something genuinely compelling to show, that 75% discount suddenly gives millions of curious viewers a very inexpensive button to press.

Pure coincidence?

Quite possibly.

Very convenient coincidence?

Absolutely.

Diablo 4 Quietly Got Patch 3.1.4 — But Blizzard Still Hasn’t Published Any Patch Notes

2026-09-11T00:29:46.117-07:00

Diablo IV received a new update this week, which would normally be about as mysterious as a Treasure Goblin running away with your gold. Except this time Blizzard apparently forgot one fairly traditional part of the process: telling anybody what the patch actually does. Players began receiving Diablo IV version 3.1.4, Build 73548 on September 9, while Blizzard's official patch-notes page still lists 3.1.3 Build 73224 from August 12 as the latest documented live update. That has left players staring at a small unexplained download immediately before BlizzCon and asking the obvious question: did Blizzard quietly prepare something for this weekend?

The answer, unfortunately for anyone hoping they accidentally downloaded Amazon, Baal and half of Westmarch on Wednesday evening, is that we do not know. But the timing is certainly good enough to make people curious.

Patch 3.1.4 Is Real. The Patch Notes Are Not Here

The mystery began when players noticed Diablo IV downloading version 3.1.4. One Battle.net player reported an update of roughly 150 MB, while another player using Steam said their download was closer to 1 GB. Different platforms can package and distribute updates differently, so those numbers do not necessarily mean different content was delivered, but both reports agree on the important part: the game now identifies itself as Build 73548.

What Blizzard has not done is explain it. The company's official Diablo IV patch archive still ends with version 3.1.3, an August update containing a collection of Season of Death Awakening fixes, class corrections and gameplay changes. There is currently no public 3.1.4 changelog explaining whether the new build contains bug fixes, backend work, promotional assets or something else entirely.

Naturally, the Diablo IV forum discussion around the missing patch notes immediately arrived at BlizzCon. This is Sanctuary. Give players an undocumented 150 MB file two days before Blizzard's biggest convention and somebody will have Mephisto's complete 2027 roadmap extracted from it before dinner.

The BlizzCon Timing Is Almost Comically Convenient

The suspicion is understandable because Blizzard has already given players several reasons to expect unusual Diablo activity this weekend. We recently looked at Diablo IV's dedicated “What's Next” BlizzCon presentation, and Blizzard has openly admitted that it deliberately kept some Season 15 content out of the PTR because it wanted to reveal more at BlizzCon. Saturday also includes a broader Diablo Developer Update, while the Opening Ceremony is expected to outline what Blizzard has described as extensive plans for Sanctuary.

Blizzard is also preparing a substantial viewing campaign around the event. As we covered in our look at Diablo IV's six-hour BlizzCon Twitch Drop campaign, players will be able to earn three weapon cosmetics by watching the broadcasts across the weekend. One forum user looking at 3.1.4 suggested the update may simply contain BlizzCon promotional material and Twitch Drop-related assets. That explanation is considerably less exciting than a hidden class, but boring explanations have an irritating habit of surviving contact with reality.

There Is One Big Problem With the Secret Season 15 Theory

Version numbering matters here. The current live game is on the 3.1.x branch, while Blizzard's Season 15 PTR was version 3.2.0. That makes 3.1.4 look much more naturally like another Season 14 maintenance update than a secret delivery mechanism for major Season 15 content. Blizzard could still include preparatory files, interface assets or backend changes that support something being announced at BlizzCon, but the existence of Build 73548 alone does not demonstrate that.

The size should also keep expectations under control. A roughly 150 MB Battle.net download is perfectly capable of containing useful client changes, assets or fixes. It is not the sort of number that requires us to assume Blizzard has secretly installed a new region. Even the larger Steam download does not tell us how much genuinely new game data was added, because patching systems frequently rewrite or repackage existing files.

This is particularly worth remembering after the last week of Diablo speculation. We have already seen hidden Season 15 content fuel Westmarch and Malthael theories, while practically every unexplained database entry now seems capable of producing a new playable-class rumor. Sometimes an undocumented patch is the beginning of something interesting.

Sometimes somebody forgot to publish the notes.

Blizzard Should Still Explain What Changed

Even if 3.1.4 turns out to contain nothing more glamorous than stability fixes and convention banners, players have a reasonable reason to want documentation. Diablo IV is a live-service game where relatively small changes can affect builds, performance, bugs and platform behavior. Patch notes do not need to contain a dramatic feature reveal to be useful.

There have also been isolated forum reports of issues including loading-screen hangs and missing sound after the update. Those reports are far too limited to establish that 3.1.4 caused either problem, especially because Diablo IV has experienced similar technical issues before, but that is precisely why knowing what Blizzard actually changed would help.

For Now, Patch 3.1.4 Is Mostly Excellent Timing

So yes, Diablo IV received an undocumented build immediately before BlizzCon. Yes, Blizzard is deliberately keeping parts of Diablo's future hidden until this weekend. And yes, it is very tempting to draw a thick red line between those two facts on the conspiracy board.

We just cannot justify doing it yet.

Build 73548 may contain preparation for BlizzCon. It may contain promotional assets. It may quietly fix bugs. It may contain backend changes nobody will ever notice. Until Blizzard publishes patch notes or players identify something concrete inside the update, 3.1.4 is an interesting mystery rather than a leak.

Fortunately, BlizzCon begins tomorrow.

If Blizzard really did slip something interesting into the client early, we should not have to stare at 150 MB of digital tea leaves for very much longer.

Diablo 4’s Amazon Rumor Is Getting Huge Before BlizzCon — Here’s Why We’re Not Buying It Yet

2026-09-10T01:25:39.746-07:00

There are only two days left until BlizzCon, which means Diablo IV has entered that wonderful period where every unexplained file name, blurry map and unusually enthusiastic forum post can become a fully developed expansion roadmap before breakfast. The newest theory gaining traction is that Amazon could be Diablo IV's next playable class, perhaps even announced at BlizzCon and offered early as a pre-purchase incentive in the same broad fashion Blizzard used with Paladin. It is an extremely attractive theory. Amazon is one of Diablo II's most beloved classes, Lord of Hatred has just taken players directly into Skovos, and Blizzard itself describes Skovos as the cradle of the Askari ruled by an Amazon Queen. If Blizzard wanted to bring Amazon back, the narrative door could hardly be more open.

Unfortunately, an open door is not the same thing as somebody walking through it. The evidence currently being passed around as an “Amazon leak” is a mixture of genuine curiosities, community assumptions and claims whose original sourcing becomes considerably less impressive once followed backwards. A rapidly growing Diablo IV forum thread bundles together a supposed Hand Crossbow clue, the circulating Kingsport and Duncraig map, speculation about another expansion and the theory that Blizzard could repeat Paladin's early-access strategy with Amazon. The thread's author subsequently removed the original source because it came from an RMT site. That alone does not prove every claim is wrong. It does suggest we should probably put the champagne back in the refrigerator until Saturday.

Amazon Absolutely Makes Sense After Lord of Hatred

First, the reason people want to believe this. Amazon is not being pulled randomly from Diablo's old character-select screen. Lord of Hatred placed Diablo IV in Skovos, the historic homeland of the Askari. Blizzard's own expansion announcement describes Skovos as being ruled by the Amazon Queen and Oracle Queen, while the campaign and environmental storytelling spend considerable time developing Askari history. After years of players asking when Diablo IV might revisit one of Diablo II's most recognizable archetypes, Blizzard has quite literally taken the game to Amazon country. That is real. (Blizzard's Lord of Hatred overview)

An Amazon could also occupy useful mechanical territory. Diablo IV has Rogue for bows, traps and agile ranged combat, but it still lacks a class truly built around javelins and spears in the classic Diablo II sense. A modern Amazon could lean into spear-and-shield melee, thrown javelins, lightning-infused ranged attacks and Askari magic without simply becoming Rogue with a different helmet. Players in the current discussion have already pointed toward exactly those possibilities. It would be nostalgic without needing to be mechanically trapped in 2000.

That makes Amazon plausible.

It does not make Amazon leaked.

The Hand Crossbow Clue Actually Points Somewhere Else

One of the more concrete pieces of evidence being bundled into the Amazon theory is a Hand Crossbow entry discovered in Diablo IV's loot filter. Players noticed it back in May, and it immediately caused speculation because Diablo IV currently has no normal playable class associated with dual-wielded Hand Crossbows. In Diablo III, of course, Hand Crossbows were practically Demon Hunter business cards. That is why the original discussion around the discovery was predominantly about Demon Hunter, not Amazon. (May Hand Crossbow discussion)

The clue is interesting, but even there we should keep both feet on the ground. A loot-filter entry can exist because Blizzard is preparing a future weapon family. It can also exist because a planned item changed, because a system contains unused categories, because Rogue may eventually receive another weapon type or because development files are considerably messier than fans would like them to be. Diablo IV already gives Rogue a Unique Two-Handed Crossbow with its own Reload mechanic, so Blizzard experimenting further with ranged weapon categories would hardly require the immediate construction of another class.

And if the Hand Crossbow really is a deliberate class breadcrumb, Demon Hunter remains the much more obvious interpretation. That does not eliminate Amazon. It simply means one of the “Amazon clues” does not actually say Amazon when examined on its own.

We have been here before. In late August, the same Hand Crossbow discovery was already driving Demon Hunter speculation ahead of BlizzCon. One unexplained database category cannot simultaneously confirm every ranged class Diablo has ever had.

The Kingsport Map Is Interesting — and Also Wrong in Some Interesting Places

Then there is the map. An alleged Diablo IV world-map screenshot has circulated showing Kingsport and Duncraig on previously inaccessible western territory. We already looked at the broader implications in our Season 15 Westmarch and Malthael speculation, because the timing is undeniably intriguing. Blizzard deliberately withheld some Season 15 content from the PTR, BlizzCon is days away, and Kingsport and Duncraig are legitimate locations associated with Westmarch. A new western destination would fit several pieces of current Diablo storytelling.

But the leaked map has problems. Players familiar with Sanctuary's geography noticed that Kingsport and Duncraig appear to be positioned in the opposite relative order from established maps. Kingsport is also depicted in ways that do not cleanly match previous geography. A German Diablo site examining the image reached much the same conclusion: the discrepancy could mean Blizzard redesigned the region for Diablo IV, the screenshot could represent an unfinished internal map, the display itself could be buggy, or the image could simply be fake. To make things even murkier, at least one widely circulated version of the map has been AI-enhanced, meaning not every image currently being shared is even the original alleged screenshot. (4Fansites map analysis)

That does not kill the Westmarch theory. Early development maps can absolutely contain incorrect geography, placeholder names and unfinished layouts. Blizzard can also move cities when adapting a twenty-five-year-old world map into an actual playable open world. But those possibilities make the image weaker evidence, not stronger evidence.

And most importantly for today's rumor, a Westmarch map does not prove an Amazon class anyway.

The Original Rumor Is Doing a Lot of Work With the Word “Likely”

The forum post currently driving much of the conversation makes several jumps in quick succession. Hand Crossbow exists in the files, therefore another class is coming. Skovos has Amazon lore, therefore Amazon is the frontrunner. Paladin was unlocked early for Lord of Hatred pre-purchases, therefore Amazon may be another early-access pre-purchase class. Kingsport and Duncraig appear on an alleged map, therefore another expansion may be approaching. Blizzard has hidden BlizzCon content, therefore the announcement could happen this weekend.

Every individual step is possible.

The problem is that possibility compounds very badly when stacked.

It is the same reason a Diablo build can look magnificent when every conditional multiplier is active and rather less impressive when three of them are theoretical. The Amazon rumor currently has excellent synergy. It just does not have enough base damage.

Paladin Early Access Does Not Establish a New Annual Class Pattern

The pre-purchase theory deserves particular caution. Blizzard did indeed make Paladin playable early for people who pre-purchased Lord of Hatred. That worked because Lord of Hatred was officially sold as an expansion containing two classes: Paladin arrived early, while Warlock became playable with the expansion's April 28 launch. Blizzard could absolutely reuse that commercial model. A popular returning class is an effective pre-order incentive, and Amazon would certainly qualify.

But we currently have no officially announced third Diablo IV expansion, no announced release window for one and no Blizzard statement saying another class will be revealed at BlizzCon. Paladin's release tells us Blizzard is willing to provide expansion classes early. It does not tell us Blizzard has decided to do that every time a season approaches.

This matters because some versions of the rumor are already describing Amazon as if the only remaining mystery is when the pre-purchase page appears. That is several stages ahead of the available evidence. Blizzard has not even confirmed the product Amazon is supposedly helping sell.

What Blizzard Has Actually Said About BlizzCon Is Much Broader

There is a legitimate reason to expect something meaningful this weekend. Blizzard's new official Diablo BlizzCon guide says Diablo will take center stage during Saturday's Opening Ceremony to reveal “extensive plans” for the future of Sanctuary. The Diablo team then has a Developer Update later that day, with additional Diablo programming across the weekend. That is stronger language than “come watch us discuss balance changes.”

We have already covered why Blizzard's BlizzCon positioning suggests more than an ordinary Season 15 presentation, and yesterday's six-hour Diablo IV Twitch Drop campaign gives Blizzard every reason to keep as many eyes as possible on the broadcasts. The original Diablo will also be playable at the convention, which has kept the Diablo 1 remaster rumor alive heading into the weekend. Separately, Blizzard and CD Projekt Red have promised more information about the wider Diablo IV and Witcher partnership.

Something is clearly happening.

“Something” remains frustratingly different from “Amazon.”

Amazon Would Still Be One of Blizzard’s Best Possible Reveals

Skepticism about the rumor should not be mistaken for skepticism about the class. Amazon would be an excellent fit for modern Diablo IV. Blizzard has already shown with Paladin that it is willing to resurrect an old class fantasy while rebuilding the actual mechanics around Diablo IV's current systems. Amazon offers enough recognizable material to trigger nostalgia immediately: Javelin and Spear Skills, lightning attacks, bows, evasive movement and the broader Askari culture. But she also leaves enough design space for Blizzard to create something new rather than importing Diablo II's skill tree with higher-resolution icons.

Lord of Hatred has done much of the narrative work already. Players have walked the Amazon homeland. Blizzard has expanded the Askari beyond a paragraph in an old manual. Skovos is ruled by Amazon leadership in the current game. If Amazon appears on the BlizzCon stage Saturday, nobody will need a lore presentation explaining why she suddenly exists.

That is exactly why the rumor spreads so easily. The idea feels correct before the evidence is examined.

There Are Other Candidates With Equally Interesting Clues

The problem for anyone declaring Amazon the frontrunner is that other class theories have their own circumstantial evidence. Demon Hunter has the Hand Crossbow filter entry. Monk continues to be requested because Diablo IV still lacks Diablo III's particular martial-arts fantasy. Witch Doctor remains one of the most visually distinctive classes Blizzard has ever made. Diablo Immortal has introduced classes such as Tempest that could theoretically migrate into Diablo IV. Blizzard could also simply create another original class, as it did with Spiritborn and Warlock, rather than treating Diablo IV as a reunion tour.

Even the idea that a new class must be announced now is speculation. Blizzard's “extensive plans” could involve Season 15, future seasons, another region, a third expansion, a remaster, a separate Diablo project or combinations of several things. Two days before BlizzCon, the sensible prediction is that Blizzard wants us curious.

Congratulations to them. It worked.

The Good News Is We Only Have to Be Patient Until Saturday

Normally, Diablo rumors can float around for months while everyone studies job listings and zooms into concept art until the pixels confess. This one has an unusually short shelf life. BlizzCon's Opening Ceremony begins on Saturday, September 12, and Blizzard has explicitly placed Diablo among the major announcements. If Amazon really is preparing to step back into Sanctuary, we are unlikely to spend much longer arguing about RMT articles and geographically confused screenshots.

Until then, this is where we would place the evidence:

Amazon makes sense. Skovos provides an excellent lore foundation, the class has enormous nostalgia value and Diablo IV still has room for a dedicated spear/javelin archetype.

A new class at BlizzCon is believable. Blizzard is promising substantial Diablo news and has demonstrated that it is willing to use early class access as a major expansion incentive.

Amazon being specifically leaked is much harder to defend. The source chain is poor, the Hand Crossbow clue points at least as naturally toward Demon Hunter, and the circulating map contains enough inconsistencies that even players supporting the wider Westmarch theory are questioning its authenticity.

So yes, we would happily play an Amazon.

We might even believe Blizzard is preparing one.

But until somebody in Anaheim walks onto a stage with a javelin, “Amazon confirmed” belongs in exactly the same drawer as every other pre-BlizzCon certainty: the one marked “we'll know on Saturday.”

Diablo 4 Player Says the Jeweler Charged Twice for Two Sockets — and Added None

2026-09-10T01:17:19.357-07:00

Diablo IV's Jeweler has always operated according to a fairly comforting agreement. You bring the item, you bring the materials, the Jeweler punches a hole in the item, and everybody goes home satisfied except perhaps the item. A fresh Xbox bug report suggests that arrangement can occasionally become rather more one-sided. One player says they paid to add sockets to a Two-Handed Legendary weapon, watched the game consume the required resources, accepted the operation and then discovered that no sockets had actually been added. They tried again. More materials disappeared. The weapon remained stubbornly hole-free. By the time the player considered a third attempt, the crafting cost had climbed dramatically, leaving them with a weapon that still had no usable sockets and a bill that had already been paid twice.

The September report is currently a single Xbox case, so this is not evidence that Diablo IV's entire socket system is broken. But it has an uncomfortable precedent. In May, a separate PC player reported spending 25 Baleful Fragments to add a second socket to a chest piece. The game appeared to complete the operation, took the materials and then failed to create the socket. That earlier player also lost another unrelated seasonal reward during the same session, so we cannot assume both cases share the same cause. What they do share is the simplest possible failure state: the Jeweler accepts payment for a socket the item never receives. (September Xbox report)

The Player Paid Twice Because the First Attempt Looked Like It Had Worked

The Xbox player describes adding sockets to a Two-Handed Legendary weapon and accepting the operation normally. Resources were consumed, but when they went to insert Gems afterward, there were no sockets available. Assuming the first attempt had simply failed visually or had not registered properly, they returned to the Jeweler and performed the operation a second time. Again the materials were taken. Again no sockets appeared. The next attempt was then quoted at 25 Legendary materials, with the player noting that the price had increased after each unsuccessful attempt. At that point, continuing to test the problem would have meant repeatedly feeding increasingly valuable materials into a crafting action that had already failed twice.

That is what makes this more interesting than an ordinary visual glitch. If the socket existed but the UI temporarily failed to display it, relogging or re-equipping the item might reveal the missing slot. According to the player, however, the weapon offered no socket when they tried to insert Gems, suggesting that the actual item state had not been updated even though the resource transaction had been processed. Diablo IV apparently remembered the payment more reliably than the service attached to it. This is, admittedly, a very authentic retail experience. It is less ideal in Sanctuary.

Two-Handed Weapons Are Supposed to Support Two Sockets

The item type itself should not be the obvious problem. Two-Handed Weapons have long supported up to two Gem sockets in Diablo IV, alongside Chest Armor and Pants, while most other eligible slots use one. The current crafting system also allows sockets to be added at the Jeweler rather than requiring players to wait for an item to drop with them already present. Blizzard has revised the material economy around that process several times, particularly with Lord of Hatred, but adding sockets remains an intended and important part of finishing an item.

That importance has only increased as Diablo IV's gearing systems have become more elaborate. Gems and Runewords can represent meaningful portions of a build, and an otherwise excellent Two-Handed Weapon without its expected sockets is not actually finished. We recently covered a fresh report that high-tier Gem progression may disappear during salvage, which already made players understandably cautious around Gem materials. Now another player is reporting the opposite end of the same workflow: the Gem is ready, the weapon is ready, but the hole you paid for apparently never existed.

Baleful Fragments Make a Failed Socket Expensive

The modern socket economy makes that failure more painful than it would have been in early Diablo IV. Lord of Hatred shifted many high-level item modifications toward materials such as Baleful Fragments, and players have spent much of 2026 debating whether those costs become too restrictive while characters are moving from Penitent into Torment. A Two-Handed Weapon may need two socket additions, effectively doubling the material requirement compared with a one-socket item. In April, players were already complaining that adding both sockets to a weapon could cost around 50 Baleful Fragments, which represented a meaningful amount of salvaged gear at that stage of progression. (earlier socket-cost discussion)

That debate is about intended cost. The September report is different. A crafting expense can be high and still be fair if the player receives what they purchased. A failed transaction changes the entire calculation because the materials no longer represent progression; they simply vanish. The player then faces a wonderfully unpleasant decision: spend even more to see whether the third attempt works, abandon the weapon, or stop playing amateur quality assurance until Blizzard explains what happened.

We recently saw a similar problem with the Jeweler's Mythic crafting tooltip apparently promising a Two-Handed Sword before delivering a Mace. That case was primarily about communication because the broader random weapon output may actually be intended. This socket report is more straightforward. If you pay to add a socket and receive no socket, there is very little room for philosophical interpretation.

A Similar Socket Report Appeared Back in May

The strongest reason not to dismiss the Xbox case as a one-off controller hiccup comes from a May 16 Technical Support report. That PC player said they paid the Jeweler to add an extra socket to a breastplate. The operation consumed 25 Baleful Fragments and apparently displayed as successful in the moment, but the second socket never appeared. The player described the materials as gone and the item unchanged. Their thread received no technical diagnosis before automatically closing a month later. (May missing-socket report)

Two reports separated by four months do not establish a widespread persistent bug, particularly because they involve different platforms and different item slots. But they demonstrate that the September player's basic experience is not unprecedented. At least one other player has previously described Diablo IV taking socket materials without adding the corresponding socket. If additional reports now appear after the Xbox case, that earlier incident becomes considerably more relevant.

This has been a recurring theme with Diablo IV's item systems lately. Horadric Gems have produced bizarre repair-cost reports, players have reported entire stash tabs appearing empty, and the Gem salvage system has already required Blizzard to fix fragment losses once before. None of those issues should automatically be connected technically. They simply underline why transactions involving rare gear and materials need to be exceptionally reliable. Diablo is fundamentally a game about trusting numbers attached to objects.

The Increasing Price Makes Repeated Testing a Bad Idea

The September player says the next socket attempt had become extremely expensive after the first two failures. We cannot independently verify the exact cost progression from the forum report alone, and Blizzard has changed crafting economies often enough that we should not turn one screenshot-less description into a universal socket-price table. The practical advice is easier: if the Jeweler consumes the materials but fails to add the first socket, do not immediately pay again just to see whether the second attempt behaves differently.

Instead, inspect the item carefully, leave and reopen the Jeweler interface, change zones or relog and confirm that the socket truly did not register. Take screenshots before and after the attempt if valuable materials are involved. If the socket remains absent, document the item and the resources consumed before doing anything else to it. Adding more crafting changes can make later troubleshooting harder and, as the Xbox player discovered, potentially more expensive.

This is especially relevant for an unusually strong item. Transfiguration already means players may invest heavily in a promising endgame drop before knowing whether it becomes the final version of the item. Once a weapon survives the Greater Affix hunt, Enchanting, Tempering, Transfiguration and every other modern crafting checkpoint, losing resources at the humble “please add two holes” stage feels almost artistically cruel.

Blizzard Has Been Adjusting Socketing for Years

The Jeweler itself has changed considerably since launch. Blizzard previously lowered the level requirement for accessing the Jeweler, changed when Gem Fragments begin dropping and revised socketing costs so Scattered Prisms were required only for Ancestral equipment under the older item system. Lord of Hatred then reworked the broader crafting material economy again. Blizzard's current patch notes continue adjusting Gem conversion recipes and material availability, including increasing high-Torment Gem Fragment drops and allowing Baleful Fragments to be converted into Forgotten Souls. (current Diablo IV patch notes)

Those changes show how central the Jeweler remains to Diablo IV's endgame. It is no longer simply the person who upgrades a Ruby every twenty levels. Gem conversion, socket creation and multiple related systems all funnel players through the same interface. That makes rare transactional failures particularly noticeable. A boss can fail to drop the item you wanted and everybody understands the rules. A vendor cannot normally take the payment and then invoke RNG over whether the service occurred.

This Is Still One Fresh Xbox Report

The scale caveat matters here more than the joke. Blizzard's Console Bug Report section is not currently full of Xbox players saying their sockets disappeared. The September report has only a small number of views and responses. We therefore have no basis for telling players that socketing Two-Handed Weapons is broadly unsafe or that a new game-wide Jeweler bug has suddenly appeared. Most players are presumably adding sockets normally every day.

But the report is specific enough to watch. The player identifies the platform, the item type, the number of attempts, the resource loss and the increasing price. And we can point to a separate PC report from May describing the same fundamental transaction failure on a different item. That is enough to justify documenting it without turning two reports into an epidemic.

It also gives Blizzard a fairly simple reproduction target: add sockets to eligible socketless gear on Xbox, verify that the materials are deducted only when the item's socket count actually changes, and test whether repeated attempts after a failed state increase the crafting cost without altering the equipment. Sometimes bugs hide behind seventeen interacting seasonal systems. Sometimes you ask the Jeweler to drill a hole and need to check whether there is actually a hole afterward.

A Jeweler Should Probably Provide the Jewelry Service

Diablo IV is full of intentionally expensive mistakes. Spend the wrong Rune. Salvage the item you meant to equip. Transfigure the beautiful 4GA drop and receive a result that ruins your plans. Those moments may cause language unfit for Kyovashad's cathedral, but they are part of the player's decisions. This report describes something different. The player selected a valid service, paid the displayed cost and says Diablo IV failed to deliver the result.

Once is annoying. Twice begins to feel personal.

If the Xbox report is reproducible, Blizzard needs to make sure socket creation behaves transactionally: either the item gets the socket and the resources are consumed, or the operation fails and the player keeps the materials. There should not be a third state where the Jeweler takes the Baleful Fragments, hands the weapon back unchanged and increases the price for another try.

Sanctuary's merchants already charge enough.

They do not need to introduce invisible sockets as a premium service.

Diablo 4 Player Says Repeated Disconnects Have Eaten 13 Valuable Sigils

2026-09-10T01:10:44.464-07:00

Diablo IV has many perfectly legitimate ways to consume a Nightmare Sigil. You activate it, enter a dungeon, discover that your build was perhaps more theoretical than practical, and Sanctuary politely converts the whole experiment into experience. What players generally do not expect is for the connection itself to become the final boss. A fresh PC technical-support report from September 9 describes repeated disconnects occurring roughly nine to ten minutes after entering the game, with the player claiming the failures have already cost them 10 Nightmare Sigils and 3 Escalation Sigils. The especially painful part is that the Escalation runs are tied directly to their current War Plan progression, so every disconnect does more than end a dungeon. It consumes the entry item and sends the player back to create another one before attempting the same objective again.

The report is currently one player's detailed experience, not evidence that Diablo IV's servers are broadly failing or that every player is losing Sigils. The player believes the issue is server-side and provides several reasons for that suspicion, including a 600 Mbps connection, routine network maintenance and other internet-connected devices continuing to work normally. But without Blizzard diagnosing the connection path, there are still plenty of possibilities between the player's PC and Diablo IV's game servers. What we can document is the symptom: the game stops responding, the player disconnects, they cannot immediately reconnect while the character is apparently being saved, and once they return, the active dungeon has reset and the consumed Sigil is gone. Six reported disconnects at almost the same point after logging in makes for an unusually consistent little disaster. (September 9 technical-support report)

Six Disconnects, Roughly Nine to Ten Minutes After Login

The original post already described repeated failures during Nightmare and Escalation content, but the player later added a particularly useful detail: by that point they had experienced six disconnects, each roughly nine to ten minutes after selecting a character. That kind of timing is precisely why the player began looking for something more systematic than ordinary random internet instability. They even asked Blizzard whether there is a server address they could monitor with ping or traceroute and offered to build a simple Python or PowerShell monitoring script to capture network anomalies while playing.

That does not prove Blizzard's infrastructure is responsible. Home networks, ISP routing, packet loss, security software, local client problems and the connection between regional networks can all produce symptoms that look remarkably similar from the player's chair. “Everything else works” is useful evidence, but it is not a full network diagnosis. Still, six sessions apparently failing within the same narrow window deserves investigation, especially when each failure can consume a resource attached to seasonal progression.

The dungeon is supposed to be dangerous. Apparently the connection screen has applied for the position too.

The Player Says 13 Sigils Have Already Been Lost

The material cost is what turns a generic disconnect complaint into a proper Diablo story. According to the player, the failures have consumed 10 Nightmare Sigils and three Escalation Sigils. Ordinary Nightmare Sigils are replaceable, but losing thirteen entry items while testing the same connection problem becomes tedious surprisingly quickly. Escalation Sigils are particularly annoying because they launch Escalating Nightmares, the multi-dungeon chains Blizzard originally introduced with Season 9 and later integrated more deeply into War Plans.

Blizzard describes an Escalating Nightmare as a sequence of three Nightmare Dungeons, where each dungeon carries its affixes forward and makes the next stage more dangerous. Complete the full Torment chain and players eventually face the Exalted version of Astaroth. The activity therefore asks for considerably more commitment than opening one ordinary dungeon, and the Sigil represents permission to start that chain in the first place. (Blizzard's Escalating Nightmares guide)

Lose the connection halfway through and the player does not merely lose nine minutes. They potentially lose the key to the entire sequence.

War Plans Make the Disconnect More Expensive

The current player's frustration is amplified because their War Plan specifically requires Escalation Dungeon completion. War Plans were built to turn Diablo IV's increasingly crowded endgame into something resembling a coherent route: players chain together activities, complete objectives and progress the Command Table rather than wandering between Helltides, Nightmare Dungeons, The Pit and various bosses according to whichever map icon happens to look most threatening.

We have already spent quite a lot of time documenting what happens when that structure stops progressing correctly. Season 14 players have reported War Plans becoming stuck or failing to recognize completed activities, while another investigation found Escalation Dungeons themselves sometimes failing to satisfy the War Plan objective even after players clear all three floors and defeat Astaroth. More recently, some players have reached every visible maximum and still remained stuck at War Plans Rank 9/10. The September 9 case is technically different: according to this player, the War Plan cannot progress because the connection repeatedly ends the activity before the game gets a chance to register completion.

The result feels nearly identical from the player's side. The objective remains unfinished. Another Escalation Sigil is consumed. Another run begins.

Blizzard Has Already Fixed One Disconnect-Related War Plan Bug

There is a relevant precedent in Blizzard's own patch history. Patch 3.0.4 on June 10 fixed an issue where War Plan progression could become blocked if a player disconnected while claiming rewards. That does not describe the current report, which involves disconnecting during the activity itself rather than during reward collection, but it confirms that disconnect handling has previously been capable of leaving War Plan state in a bad place. (official Patch 3.0.4 notes)

Blizzard has also continued expanding the number of Nightmare Escalation options available through War Plans. The current patch notes mention additional Helltide and Nightmare Escalation choices, making reliable completion increasingly important to the system rather than less. War Plans are supposed to remove friction by letting the player create a preferred chain of activities. A repeated disconnect that consumes the activity's entry resource turns that principle inside out.

Instead of “build your ideal endgame playlist,” the affected player gets “restart track three until the network approves.”

War Plans Can Generate Sigils, but Losing Them Still Matters

Blizzard's original Lord of Hatred explanation notes that War Plans can generate an activity Sigil on the fly when the player does not already possess one. That means not every War Plan node necessarily requires farming a separate key beforehand. But Escalation Sigils remain real, consumable endgame items outside that convenience layer, and the September player specifically says they are replacing the lost ones through the Cube before retrying the objective. Blizzard also increased rewards and added additional War Plan quests around Nightmare Dungeon Escalation Sigils in Season 14, reinforcing their place in the current endgame loop. (Lord of Hatred War Plans overview)

The broader issue is not whether another Sigil can eventually be created. Diablo players can replace almost anything if sufficiently motivated. The question is whether an externally interrupted activity should consume the resource permanently when no meaningful gameplay failure occurred. Dying because an Escalating Nightmare became too difficult is part of the game. Losing access because the session vanished nine minutes after login is a very different transaction.

This Is Exactly Why Disconnect Protection Matters

Online-only ARPGs have always had an awkward relationship with consumable content. Once an activity begins, the server needs rules governing what happens if the player disappears. If every disconnect refunded everything automatically, deliberate connection drops could become an exploit whenever a run begins badly. If nothing is ever refunded, legitimate connection failures become expensive. Developers therefore have to distinguish between failures that look nearly identical from the server's perspective while producing very different experiences for the player.

Diablo IV has had this tension since launch, and the cost becomes more visible as Blizzard adds more activities behind keys, Sigils and other access items. Earlier this week, we covered players saying Longtooth can consume a valuable Mythic Tribute without delivering the expected loot. Yesterday, The Resounding Scream was still leaving some players unable to access Echoing Hatred even after obtaining rare Trace of Echoes. The mechanics differ, but the frustration is remarkably similar: obtaining the entry resource is one challenge; convincing the activity to respect that resource is becoming another.

The Player Is Asking for Better Diagnostics, Not Just a Refund

One of the more useful aspects of the report is that the player is not simply demanding thirteen Sigils back. They ask whether Blizzard can provide a server endpoint they could monitor to determine where the connection actually fails. That would allow continuous ping or route monitoring during the session and potentially reveal whether packet loss appears locally, inside the ISP route or closer to Blizzard's infrastructure.

That kind of data would be considerably more useful than the traditional technical-support ritual of restarting the router for the fifth time and hoping the demons notice. The player says they already power-cycle their network regularly, flush DNS, have no large downloads or streams competing for bandwidth and host much of their household content through a NAS. Again, none of that rules out a local problem, but it does demonstrate why more detailed connection diagnostics would help. A failure that appears at almost the same interval across repeated sessions should be measurable somewhere.

This Is Still One Player Report, Not a Server Outage

The most important caveat remains scale. Blizzard's current Technical Support forum does not show a flood of identical September reports describing disconnects precisely nine to ten minutes after login. The September 9 thread has no large collection of confirmations behind it. We therefore should not describe Diablo IV as suffering a widespread server failure based on one detailed case. The player themselves insists the problem “has to be server-side,” but that remains their diagnosis rather than a confirmed Blizzard finding.

What makes the report newsworthy is the very specific cost attached to it: six repeated session failures, approximately the same timing, thirteen lost Sigils and War Plan progression that cannot move forward because the relevant Escalation Dungeon keeps being interrupted. That is enough for a player-report story. It is not enough for “Diablo IV servers are broken.” Sanctuary already contains sufficient exaggeration without our assistance.

Thirteen Sigils Is an Expensive Way to Troubleshoot a Connection

For now, players experiencing similar behaviour should probably stop repeatedly feeding valuable Escalation Sigils into the problem until they have tested the obvious connection variables. Try an ordinary dungeon or open-world session and see whether the disconnect occurs at the same interval. Record the exact time from character login. Check Windows Event Viewer, network adapter behaviour and packet loss. If possible, test another connection temporarily. The goal is not to prove Blizzard guilty or innocent; it is to find whether the nine-to-ten-minute pattern survives outside the expensive content.

And if the same disconnect continues occurring with suspicious precision, document it before using another valuable entry item. Screenshots, timestamps and route data give Blizzard far more to work with than a pile of vanished Sigils and understandable profanity.

Diablo IV's Escalating Nightmares are supposed to become more dangerous as you descend through the chain.

For one player, the most reliable escalation currently happens about ten minutes after logging in.

Diablo 4’s Welcome Back Booster Is Still Failing Returning Players

2026-09-10T00:56:54.161-07:00

Diablo IV's Welcome Back Booster has one job, and the name is unusually honest about it: make coming back easier. You return after months away, find an Eternal character that has been overtaken by several seasons of systems, balance changes and increasingly elaborate nouns, press a button and receive a ready-made build capable of getting you back into Sanctuary without first completing an evening course in modern Diablo itemization. It is a sensible feature. Unfortunately, players have now spent nearly two years reporting variations where the Booster disappears, offers only “Decline,” completes without actually boosting anything or simply sits in the Training Grounds refusing to respond. The latest active PC thread returned to Blizzard's forum front page on September 9, with an eligible player saying their remaining Booster is visible but clicking it does absolutely nothing.

The current case originally appeared in August and became active again this week. The player says they had two Welcome Back Boosters available, used one on a Necromancer for the Vessel of Hatred campaign, then saved the second for Lord of Hatred. After returning, they correctly found that Blizzard had relocated the feature to the Training Grounds. The Booster was there. Their Eternal Necromancer and Rogue appeared to meet the stated character restrictions. But interacting with the Booster produced no menu, no error and no explanation. It simply sat there, offering returning-player assistance in approximately the same way a locked tourist information office offers directions. (Blizzard forum report)

The Welcome Back Booster Was Designed to Remove Exactly This Kind of Friction

Blizzard originally introduced the Welcome Back Booster as a way of rapidly catching Eternal characters up with Diablo IV's changing progression systems. The original version could raise one Eternal character to Level 50, provide a choice between three complete class builds, grant a full set of Legendary equipment, fill out the corresponding Skill Tree, unlock every Altar of Lilith and hand over a useful starter package including Gold, Obols, crafting materials and a Scroll of Amnesia. Vessel of Hatred owners were initially allowed to use the Booster on two characters. It was a surprisingly generous solution to a genuine live-service problem: after enough seasons, returning to an old character can feel less like coming home and more like inheriting somebody else's tax records. (Blizzard's original Welcome Back Booster guide)

The idea became even more useful as Diablo IV continued changing underneath those characters. Tempering and Masterworking were redesigned. Difficulties changed. Paragon changed. Mythic Uniques changed repeatedly. Lord of Hatred added more systems, and Season 15 is preparing another large batch of itemization changes. Our recent look at how Transfiguration changes the modern endgame gearing curve is a good example of how much a returning player can suddenly need to understand. Blizzard was right to build a shortcut through that learning wall.

The shortcut just needs to open when clicked.

Blizzard Moved the Booster to the Training Grounds for Season 11

The rules also changed substantially with Season 11. Blizzard announced that unused Welcome Back Boosters would be moved to the Training Grounds specifically to avoid unintended use. New accounts would no longer automatically receive one after Season 10 ended. However, anyone who had created an account and logged in before the end of Season 10 would retain the right to use any eligible unused Booster later, including during Season 11 and beyond. (Blizzard's Season 11 Booster changes)

That means some apparently missing Boosters in 2026 are not necessarily bugs. A genuinely new account created after the old eligibility window should not expect the feature at all. Paladin and Warlock have also had restrictions around the legacy Booster because those classes arrived after the original preset-build system was created. Eternal-versus-Seasonal status, character level and campaign progress can matter too. Diablo IV has therefore reached the point where asking “why can't I use my Welcome Back Booster?” requires first establishing whether Blizzard believes you should have one.

The August player did exactly that. They said the affected characters were Eternal, below the relevant level threshold, had completed the base-game Prologue and were Necromancer and Rogue rather than Paladin or Warlock. They also said the Booster itself remained visibly present in the Training Grounds. The issue was not discovering where Blizzard had moved it. The issue was that nothing happened when they interacted with it.

The Support Response Somehow Made the Eligibility Rules Less Clear

The support transcript included in the player's bug report creates another interesting wrinkle. One Game Master listed several restrictions and told the player that Boosters were available to accounts created “after the launch of Season 11.” That wording appears to conflict with Blizzard's published Season 11 announcement, which says new accounts starting with Season 11 are not granted a Welcome Back Booster, while accounts that logged in before Season 10 ended retain their unused entitlement. The player then explained that their characters satisfied the other restrictions, and a second Game Master ultimately directed them to file a bug report. (player's support transcript)

We should not turn one support reply into official policy. Game Masters can make mistakes, wording can be imprecise and account-specific details may not be visible in a public forum post. Blizzard's published rules are the safer reference. But the exchange perfectly illustrates the returning-player problem. This feature exists specifically for somebody who has not been keeping up with every season. If understanding whether it works requires comparing an old blog post, modern restrictions and contradictory support wording, the welcome mat has acquired rather a lot of footnotes.

This Is Not the First Way the Booster Has Failed

Historically, players have reported several different failure modes. In December 2024, one Eternal Druid player said the Booster appeared normally, but after they timed out while researching which preset build to choose, the system began auto-completing without actually delivering the boost. In early 2025, players reported opening the Booster interface, leaving without choosing a build and later returning to find that all three build options had disappeared while “Decline Boost” remained the only available choice. The same behaviour was reported again across PC, PlayStation and Xbox later that year. (auto-complete report)

Another April 2025 case involved a player who could originally see the build choices, purchased Vessel of Hatred intending to use the expanded Booster allowance and then discovered the feature had effectively stopped functioning. Their Necromancer offered only Decline, while a newly created Spiritborn had no usable Booster interaction at all. Separate players later confirmed the same “Decline only” state. (older Booster report)

There have also been examples of unused Boosters disappearing after Battle.net and Xbox accounts were linked, and players returning months later to discover a previously available entitlement was gone. None of these reports proves one universal Booster bug has survived intact since 2024. They are almost certainly several different state, UI and eligibility problems producing similar symptoms. The recurring theme is more important: the feature designed for people least familiar with the current state of Diablo IV has repeatedly produced situations that require unusually detailed knowledge of the current state of Diablo IV.

Blizzard Has Fixed Welcome Back Booster Bugs Before

This is not a forgotten feature. Blizzard has patched Booster-related problems in the past. During Season of Witchcraft, Patch 2.1.4 fixed an issue where the Welcome Back Booster quest could remain tracked as the player's primary quest even after another quest had been completed. Blizzard later redesigned how and where the Booster appears, moving it away from ordinary Journal progression precisely because accidental or unintended use had become a concern. (Diablo IV Patch 2.1 notes)

The current trouble therefore looks less like Blizzard abandoning the system and more like a feature carrying a surprising amount of legacy state. Accounts can have different entitlement histories. Some received one Booster, some two. Some already consumed one under older rules. Some characters predate major campaign changes. Expansions add classes that were never part of the original preset-build package. Then Blizzard moved the interaction itself from Kyovashad's Fated Reliquary to the Training Grounds. Every one of those transitions creates another opportunity for an account flag somewhere to become confused.

That does not excuse the player experience. It merely explains why a button whose conceptual job is “make character stronger” may secretly have a family tree.

Returning Players Are Particularly Important Right Now

The timing makes the issue more relevant than it would be during a quiet part of Diablo IV's calendar. BlizzCon begins this weekend, Blizzard has promised substantial news about Sanctuary, and the company is already using six hours of Diablo IV Twitch Drops to pull viewers back toward the game. Season 15 is also approaching with Rebirth, substantial system changes and content Blizzard deliberately kept out of the PTR. We recently argued that Season 15 has several good ideas while still carrying older Diablo IV frustrations with it. The Welcome Back Booster is almost the perfect symbol of that tension.

Blizzard wants old players to return. The next season is being designed to make returning easier. Rebirth means an existing character can enter a new season without the psychological ceremony of deleting history and starting from an empty slot. Twitch rewards encourage people who have wandered away to watch BlizzCon. Warlock is already generating enormous interest after its extraordinarily strong Season 15 PTR showing. Everything around Diablo IV currently says: come back and see what changed.

The Welcome Back Booster should be the easiest part of that invitation.

The Best Advice Is to Check Eligibility Before Assuming It Is Broken

For players returning now, the first step is therefore checking whether the account actually retained an eligible Booster under Blizzard's Season 11 rules. If the account did not log in before the end of Season 10, Blizzard says new accounts no longer receive one. If an unused Booster was legitimately retained, look for it in the Training Grounds rather than the old Fated Reliquary location. Make sure the intended character is Eternal and fits the current class and progression restrictions before concluding the interaction itself is broken.

If the Booster is visibly present, the character appears eligible and clicking produces absolutely nothing, the August report suggests submitting a bug report remains the practical route. Screenshots of the character level, Realm, Training Grounds interaction and available Booster state would be particularly useful. Diablo IV support can only do so much with “the shiny thing doesn't work,” even when that is a surprisingly accurate technical summary.

Players should also be cautious about clicking Decline merely to clear a stuck interface. Historical reports include people who said their build options disappeared after leaving the Booster selection or declining it, and because Boosters are limited legacy entitlements, experimentally pressing buttons carries more risk than it would with a repeatable quest.

A Welcome Back Feature Should Not Need a Returning Player Guide

None of this makes the Welcome Back Booster a bad idea. Quite the opposite. Diablo IV has changed so dramatically since launch that a permanent catch-up system is one of the smartest quality-of-life features Blizzard has added. A returning player should not need to reconstruct three years of patch notes before deciding whether an old Barbarian is salvageable. Give them equipment, give them a coherent build and let them discover the modern game by actually playing it.

But that simplicity disappears when the Booster itself becomes part of the archaeology. The feature has produced reports of disappearing entitlements, missing build choices, auto-completion without rewards and, now resurfacing in September 2026, a visible Training Grounds Booster that an apparently eligible player simply cannot activate.

Diablo IV's Welcome Back Booster is supposed to say:

“Welcome back. Here is everything you need to start playing again.”

For some returning players, it is still saying something slightly less useful:

“Welcome back. Please consult the documentation.”

Diablo Immortal Just Turned 5-Star Gems Into a Global Marketplace

2026-09-10T00:38:52.738-07:00

Diablo Immortal has spent four years building one of the strangest economies in modern action RPGs: part dungeon crawler, part auction house, part gemstone exchange where a single lucky Elder Rift can suddenly make somebody considerably more interested in market prices than demons. This week Blizzard has made one of the biggest changes to that economy yet. 5-Star Legendary Gems can now be bought and sold across servers and regions worldwide, excluding China. Instead of every server effectively maintaining its own isolated population of buyers, sellers and prices, the game's most valuable tradable gems are entering what Blizzard describes as its first experiment with a cross-server marketplace.

And Blizzard is making it very clear that this may not stop with 5-Star Gems. In the latest Diablo Immortal content update, the developers say they will monitor the new market for problems and abuse, and if everything works properly they will explore expanding cross-server trading to more items in the future. That turns today's change into something considerably more interesting than another economy tweak. Diablo Immortal may be testing the foundations of a genuinely global marketplace.

5-Star Legendary Gems Are No Longer Trapped Inside One Server Economy

Until now, Diablo Immortal's Market has always been deeply affected by the server you happened to inhabit. Two players could be chasing the same 5-Star Legendary Gem in different parts of the world and encounter very different supply, competition and pricing simply because their local economies had developed differently. A heavily populated server might have several copies of a gem available while a quieter one could have almost none. Sellers were similarly dependent on finding buyers inside their own market environment.

The new system breaks down that wall for 5-Star Gems. Blizzard says these gems can now be purchased and sold through the marketplace across all servers and regions worldwide, except China. That should dramatically increase the number of potential buyers and sellers participating in the same economic pool. More sellers potentially means better availability. More buyers potentially means more competition for desirable gems. What it ultimately does to prices will depend on the balance between those two forces, and it would be foolish to declare every 5-Star Gem cheaper before the market has actually had time to settle.

What we can say is that the old server lottery matters considerably less. If your server previously had three people selling the gem you wanted at heroic prices, you are no longer restricted to those three people. Sanctuary has discovered international trade. Deckard Cain would presumably require several additional bookshelves.

This Could Change the 5-Star Gem Economy Quite Dramatically

Legendary Gems sit at the centre of Diablo Immortal's long-term progression economy. 5-Star Gems are particularly important because they contribute enormous amounts of Resonance when upgraded and often contain some of the strongest build-defining effects in the game. They are also closely tied to the game's monetization systems through Legendary Crests, Platinum trading and the eternal human desire to make one number slightly larger than another.

That means liquidity matters. A player can technically own a valuable tradable gem, but its practical value depends on somebody being willing to buy it. Likewise, having enough Platinum to purchase a desired gem is not especially useful when nobody on the server is selling one. Cross-server trading should increase the chance that both sides of those transactions actually meet.

The change arrives at an interesting time for players already thinking carefully about the value of 5-Star Gems. We recently looked at the redesigned Boon of Plenty and its greater emphasis on Telluric Pearls, which remain one of the more deterministic ways of working toward specific 5-Star Legendary Gems rather than trusting Elder Rift luck. Cross-server trading adds another route toward the same goal: instead of waiting for your local market to produce the correct gem, a much larger pool of sellers can potentially supply it.

Prices Could Become More Consistent — but Not Necessarily Lower

The obvious assumption is that a larger marketplace means cheaper Legendary Gems. Possibly. It is certainly plausible that extremely expensive gems on supply-starved servers will face downward pressure once those sellers are competing against listings from many more players. Likewise, gems that were unusually cheap on one server because demand was low may become more expensive once buyers from elsewhere can reach them.

The more likely long-term result is therefore price convergence. Extreme differences between servers should become harder to sustain when players are effectively participating in a broader market. A bargain that existed only because nobody locally wanted a particular gem can now be discovered by buyers elsewhere, while an outrageous asking price supported only by local scarcity suddenly has much more competition.

There may still be substantial differences between gems themselves, of course. Meta-defining 5-Star Gems will attract more demand than unpopular alternatives. New gems can command premiums while supply remains limited. Rank, quality and upgrade history all matter. Diablo Immortal is not transforming into a perfectly efficient stock exchange overnight. It is simply removing one of the largest artificial walls between buyers and sellers.

Which is probably good news for players and mildly disappointing news for anyone who had successfully cornered the local market in magical rocks.

Blizzard Is Already Watching for Market Abuse

Blizzard knows that opening a larger market also opens larger opportunities for abuse. The developers explicitly say they will monitor the system closely for problems or exploitative behaviour and respond as quickly as possible. That warning is hardly surprising. Diablo Immortal's Market handles items connected to real-money-adjacent currencies and account progression, so unusual transfers, manipulated prices and fraudulent transactions are considerably more serious than somebody selling a yellow sword for three Gold too much.

The same update includes another anti-fraud measure. New and existing accounts will no longer be allowed to sell Normal Gems on the Market until they have completed Inferno Difficulty 1. Blizzard describes that restriction as part of its continuing efforts to detect and prevent fraudulent behaviour. It raises the entry barrier for accounts created primarily to move tradable gems through the economy and shows that the developers are thinking about market security at exactly the same time they are dramatically increasing market connectivity.

That is particularly relevant after a week where Normal Gems have already been unusually valuable. Our Winds of Fortune farming guide highlighted how the four-player Normal Gem bonus could be doubled without counting against the usual daily cap. Diablo Immortal clearly wants players trading gems. It would simply prefer those players to be actual players.

Bulk Buy Is Coming Back Too

The cross-server market is not the only economic quality-of-life change. Blizzard is also reintroducing Bulk Buy, allowing players to specify a price range and purchase larger quantities of items at multiple price points more quickly. Anyone who has spent an unreasonable amount of time repeatedly interacting with individual Market listings will understand why that matters.

Together, the changes suggest a broader effort to modernize how Diablo Immortal handles trading. One update gives 5-Star Gems an enormous shared audience, another makes purchasing large quantities less tedious and a third adds restrictions aimed at suspicious Normal Gem trading. These are not especially glamorous features compared with a new class or raid boss, but they affect systems players use constantly.

And unlike the increasingly elaborate economy surrounding Diablo Immortal's customizable wings, where players can burn thousands of Eternal Orbs chasing cosmetic variations, the Market affects almost everyone interested in serious character progression. The game may be full of monsters, but at some point every dedicated player becomes an amateur economist.

This Is Blizzard’s Test for a Much Bigger Marketplace

The most important sentence in Blizzard's announcement is not really the one confirming cross-server Gem sales. It is what comes afterward. Blizzard calls the system its “first foray into a cross-server marketplace” and says that if it works well, the team will explore expanding it to additional items.

That opens several obvious possibilities. Normal Gems could eventually join the global economy. Skill Stones, pets or other tradable categories could potentially follow depending on Blizzard's technical and economic priorities. Blizzard has not announced any of those specific expansions, so they should not be treated as confirmed plans. The significance lies in the architecture. The developers are explicitly testing whether Diablo Immortal's previously fragmented Market can operate across servers on a larger scale.

If successful, that could gradually make server choice less important to economic progression. Servers would still matter for social systems, clans, activities and local communities, but their individual market populations would become less capable of determining whether a particular item is common, impossible to find or priced like somebody accidentally added an extra zero.

The Same Update Is Also Taking Aim at PvP Crowd Control

The marketplace may be the biggest economic story, but the update contains another substantial system change that deserves attention. Blizzard has introduced a new Unstoppable Bar across all PvP modes, designed to reduce the frustration of repeatedly losing control of your character.

The bar appears beneath the player's Life bar and fills when they are affected by knockback or effects that cause a total loss of control. After being hit by one of those effects, additional qualifying effects received during the next six seconds become 30% less effective. If the player accumulates three seconds of knockback or hard crowd control within an eight-second window, they receive a 2.5-second crowd control protection buff granting temporary immunity to knockback and crowd-control effects. The protection duration cannot be extended.

In practical terms, Diablo Immortal is introducing diminishing returns for chain-CC. Being stunned once can still hurt. Being bounced between several players like a particularly expensive demonic volleyball should now become progressively harder.

Blizzard is treating this system as experimental too. The developers say they will monitor player feedback, adjust the system if necessary and may even disable it entirely if they are unhappy with how it performs. That is a fairly strong indication that September's update contains more live testing than usual. Both the marketplace and PvP changes are systems Blizzard wants to observe under real population pressure rather than simply declare finished forever.

Diablo Immortal Is Quietly Becoming Less Server-Bound

The broader trend is difficult to miss. Diablo Immortal has already expanded cross-server competition through activities like Bout of Realms, and now the economy is beginning to follow. Our recent look at the enormous Diablo Immortal block on the BlizzCon schedule raised questions about how much Blizzard plans to reveal for the game's next phase. Cross-server 5-Star Gems may offer a clue to one part of that direction: Immortal increasingly wants its population interacting as one larger player base rather than dozens of isolated server economies.

That does not mean server identity is disappearing tomorrow, and the new Market could absolutely develop problems. Larger markets can create new opportunities for manipulation, unforeseen price swings and abuse, which is precisely why Blizzard says it will be watching closely. Diablo Immortal's economy has also had enough strange technical incidents lately that players will be monitoring their valuable inventories carefully; we recently covered reports of enormous Reinforced Scrap and Enchanted Dust stacks disappearing after recent updates. Trust matters when the items involved represent months or years of progression.

But if the system works, this is a meaningful improvement. A 5-Star Gem no longer needs to find a buyer on your particular server. A player hunting that gem no longer has to hope somebody nearby happens to list one. Supply and demand suddenly operate on a much larger stage.

For years, Diablo Immortal players have travelled across Sanctuary to hunt monsters.

Now their Legendary Gems have gone international.

Diablo Immortal’s Dead Druthers Buff May Be Ignoring Necromancer Summons

2026-09-09T01:17:36.660-07:00

Necromancer builds in Diablo Immortal are built around a fairly simple professional relationship: you summon the dead, the dead do the work, and everyone agrees not to ask too many questions about employment law. A fresh September 8 Android bug report suggests one particular Bone Armor combination may be breaking that arrangement. The player says Dead Druthers correctly increases their own Attack Speed and Movement Speed while Bone Armor is active, but the same buff does not appear to reach Necromancer summons when Bone Armor has been transformed by Estranged Patron's Ward Armor essence. The player tested Spectral Mages, ordinary Skeletal Mages, Command Golem and Skeletons and says none showed the expected Attack Speed increase.

This is currently one player's controlled testing rather than a confirmed Blizzard bug, so it would be premature to declare Dead Druthers universally broken. The report is nevertheless interesting because Blizzard's own description of Dead Druthers is unusually explicit: while Bone Armor is active, the Movement Speed and Attack Speed of you and your summons are increased. Estranged Patron, meanwhile, changes Bone Armor into a warding circle that follows the Necromancer and grants nearby allies a protective shield. The September tester receives their own Dead Druthers bonus while that modified Bone Armor is running. Their summons apparently do not. (September 8 bug report)

Dead Druthers Is Specifically Designed for Summon Builds

Dead Druthers is a Necromancer Pants essence introduced as part of an older essence update and designed very clearly around minion-heavy setups. Blizzard originally described the effect as increasing both the player's and summons' Movement and Attack Speed by 10% while Bone Armor remains active. Essence progression can raise that value, which is why the September tester reports a current bonus of 19% rather than the original baseline. That distinction matters: 19% Attack Speed across an entire Necromancer army is not a small decorative bonus. Skeletal Mages, Skeletons and Golems all convert increased attack frequency into additional damage over the duration of an encounter, which means a missing speed bonus can affect the practical output of the entire build rather than one isolated animation. (Blizzard's Dead Druthers description)

It is also exactly the kind of essence Necromancer players tend to build around because summon builds work best when several mechanics amplify the same army. A single bonus affecting four different summon types is far more attractive than an effect helping only the Necromancer's own Primary Attack. If one essence turns Bone Armor into a better party-support skill while another makes Bone Armor accelerate every summon, combining the two sounds perfectly sensible. Diablo buildcraft has always been about finding two tooltips that look good separately and discovering they become mildly irresponsible when placed together.

Estranged Patron Changes Bone Armor Into Ward Armor

Estranged Patron complicates that interaction by fundamentally altering how Bone Armor behaves. Blizzard describes the Chest essence as making Bone Armor conjure a warding circle that follows the Necromancer. Allies inside that circle receive a shield that protects against total loss of control and knockback. The September player calls this Ward Armor and reports that party members standing nearby correctly receive the shield, while their summons do not show the same shield effect. More importantly for Dead Druthers, the player's own speed bonus remains active, confirming that Diablo Immortal still considers the modified skill sufficiently “Bone Armor” for Dead Druthers to affect the Necromancer.

The question is therefore what the game thinks the summons are doing. Dead Druthers does not say “summons protected by Bone Armor gain Attack Speed.” It says the player and summons gain the bonus while Bone Armor is active. If that wording is taken literally, the summons should not need their own shield or individual Bone Armor buff to qualify. Bone Armor is active on the player, Dead Druthers is active on the player, and the player's army should inherit the listed speed bonus. According to the fresh test, it does not.

The Player Tested Multiple Summon Types

The September report is more useful than a simple “my damage feels lower” complaint because the player tested several different Necromancer minions. Spectral Mages were checked. Normal Skeletal Mages were checked. Command Golem was checked. Skeletons were checked. The reported result was consistent: the Necromancer receives Dead Druthers' Attack Speed increase with Ward Armor running, while the summons do not appear to attack faster. The tester says they are less certain about Movement Speed because that is harder to measure visually, so the strongest claim is specifically about Attack Speed. (full player test)

That caveat is worth preserving. Diablo Immortal contains enough animation differences, summon AI and attack wind-ups that eyeballing small percentage changes can be misleading. A proper frame-by-frame test or combat-log comparison would be stronger evidence. But a 19% Attack Speed bonus is large enough that an experienced player should normally see a meaningful difference across repeated attacks, particularly when several summon types all appear unchanged. More independent testing would tell us whether the interaction fails universally or only under specific essence combinations.

The Ward Armor Shield May Be a Separate Clue

The same player notes that Ward Armor's visible shield does not appear on their summons either, while nearby human party members do receive it. That may be connected to the missing Dead Druthers bonus, but we should be careful here. Blizzard's Estranged Patron wording says “allies” rather than explicitly saying “you and your summons,” and games do not always classify pets and summons as normal allies for every support effect. Dead Druthers is different because Blizzard explicitly names summons in the essence description. The missing Ward Armor shield may therefore be intended while the missing Dead Druthers Attack Speed remains a genuine interaction problem — or both may stem from the same underlying Bone Armor state. We do not have enough evidence yet to choose confidently.

Diablo Immortal has accumulated plenty of examples where two individually functioning systems behave strangely when combined. We recently covered players burning thousands of Eternal Orbs through custom Wing rerolls, where the underlying feature works but the surrounding economy creates a very different experience than the simple cosmetic premise suggests. More recently, iPhone 17 owners have reported severe heat and battery drain after the engine update, another case where the interesting question is not whether the feature exists but what happens when it meets a particular hardware or system configuration.

Necromancer Summons Make Small Buff Bugs Much Bigger

A missing 19% Attack Speed bonus on one character is annoying. A missing 19% bonus across an entire summon army is potentially much more expensive in practical damage. Necromancer builds often stack summon duration, summon damage and attack-frequency improvements because each bonus multiplies the value of several active minions at once. A Golem attacking faster is good. Several Skeletons attacking faster is good. Two Mages attacking faster is also good. When all of those effects exist simultaneously, one shared Attack Speed essence can contribute considerably more than its tooltip initially suggests.

That is why summon-specific bugs have a habit of making builds feel mysteriously weak. The Necromancer itself can still cast normally. Bone Armor still activates. The Dead Druthers icon or buff may still appear on the player. Ward Armor may still protect party members. Nothing visibly collapses. The army simply performs below the number the build was constructed around. Diablo mathematics already contains enough opportunities for a build to disappoint its creator without one of the multipliers quietly deciding that skeletons are not invited.

For Now, Test Dead Druthers Before Building Around Ward Armor

Until more players reproduce the interaction, Necromancers using Dead Druthers together with Estranged Patron should treat this as something to test rather than a confirmed universal failure. The cleanest approach would be comparing summon attack frequency with ordinary Bone Armor against the same summons using Estranged Patron, while keeping other Attack Speed sources unchanged. Skeletal Mages are probably the easiest visual test because their repeated attacks can be timed over a fixed duration. If Dead Druthers clearly accelerates them under normal Bone Armor but the effect disappears when Ward Armor replaces it, that would strongly support the September report.

Players should also test without changing Dead Druthers itself. If swapping only Estranged Patron causes the summon Attack Speed bonus to disappear while the Necromancer's own bonus remains, the interaction becomes considerably easier to isolate. Additional Android, iOS and PC reports would help determine whether this is a general essence combination problem or something more platform-specific. The original report comes from a OnePlus 12 running Android 16 and Diablo Immortal version 5.0.4.

The Tooltip Is Pretty Clear About Who Should Get Faster

For now, the strongest reason to take the report seriously is simply Blizzard's own wording. Dead Druthers was not described as “you gain Attack Speed while Bone Armor is active.” It specifically included “you and your summons.” The September tester says half of that sentence continues working when Estranged Patron modifies Bone Armor and the other half apparently does not. Blizzard may ultimately clarify that the modified Ward Armor changes how summons qualify, or another player may discover an overlooked condition. But based on the published essence description, expecting the summons to become faster is hardly unreasonable.

This is currently a small report, and it should stay a small report until more evidence arrives. It does not prove Necromancer summons are broadly broken, nor that Dead Druthers fails in every setup. What it does show is one player testing four different summon types and finding the same missing Attack Speed effect whenever Dead Druthers is paired with Ward Armor.

Necromancers already went to the trouble of raising an army from the dead.

They should not also have to explain to it why everyone else got the speed buff.

Diablo 4’s Mythic Crafting Tooltip Can Promise a Sword — Then Give You a Mace

2026-09-09T01:07:53.031-07:00

Diablo IV players are accustomed to crafting systems containing a certain amount of disappointment. You bring rare materials, carefully select the recipe and press a button that costs enough resources to make the moment feel important. Sometimes the result completes the build. Sometimes Sanctuary hands you something technically valuable but spiritually offensive. That is simply Diablo. A fresh September 8 report, however, raises a slightly different problem: what happens when the crafting screen appears to promise one weapon type and the game gives you another? A Warlock player says the Jeweler specifically offered a “Mythic Unique Two-Handed Sword” craft, but the resulting Mythic was a Two-Handed Mace. The craft itself may actually be behaving exactly as Blizzard intended. The tooltip may be the part that has wandered away from reality.

The player was trying to quickly obtain The Grandfather for a new Warlock and used the Jeweler's Mythic crafting system rather than waiting for the correct drop. According to the report, the English-language recipe explicitly described the output as a Two-Handed Sword. They spent the required materials and received a Two-Handed Mace instead. Another forum user pointed out that Mythic crafting works through broader equipment slots rather than guaranteeing one exact item family, which would make the Mace a legal result. The original player's response was difficult to argue with: if the recipe is really rolling a random Two-Handed Weapon, perhaps it should say Two-Handed Weapon rather than Sword. (Blizzard forum report)

The Craft May Be Correct Even If the Tooltip Is Wrong

This distinction matters because it would be easy to turn the report into “Diablo IV Mythic crafting gives the wrong item,” which is probably not what happened. Blizzard's own explanation of Season 14's Mythic system says crafting returns a random class-usable Mythic from the same equipment slot, not necessarily the same Unique or exact subtype used to start the process. Blizzard even provides an explicit example for One-Handed Weapons, Offhands and Shields, which share a slot category: a Necromancer can use a One-Handed Weapon and receive a Focus or Shield. In other words, the system's internal idea of a slot is sometimes broader than the item label a player sees in their inventory.

That randomness has been one of Season 14's central Mythic debates. We covered it when Blizzard announced that Season 15 would already rewrite much of Season 14's Mythic crafting structure. Players were willing to grind rare materials; what frustrated them was putting a valuable item into a supposedly targeted crafting system and still receiving something fundamentally different. Blizzard's solution for Season 15 is to separate the philosophies more clearly. Jeweler crafting remains the cheaper random route. The Horadric Cube gets the expensive deterministic route. That makes sense. A slot machine can be perfectly good entertainment when the button says “slot machine.”

The Player Was Trying to Craft The Grandfather

The September 8 player says the goal was simple: their Warlock needed The Grandfather, so they went to the Jeweler and selected the recipe that appeared to offer a Mythic Unique Two-Handed Sword. They were not expecting The Grandfather with absolute certainty merely because they pressed a Grandfather-shaped button; the argument in the thread quickly became about what the category itself represented. If multiple Two-Handed Weapon families are valid outputs, then a Two-Handed Mace may be functioning correctly under Blizzard's slot rules. What becomes misleading is presenting that lottery as specifically a Sword recipe.

This is particularly important because Mythic crafting is expensive enough that players reasonably read the wording carefully. Season 14's Jeweler method uses Resplendent Sparks and specific Runes, resources that represent significant farming time and, in the case of Sparks, often the remains of Mythics players already sacrificed. We have previously looked at why players are desperate for more useful ways to spend surplus Resplendent Sparks, but “surplus” does not mean disposable. When a recipe consumes endgame currency, its possible outputs should be described with considerably more precision than a Treasure Goblin's employment contract.

Season 14 Made Every Unique Potentially Mythic

Part of the confusion comes from just how radically Blizzard changed Mythics this season. Season 14's Mythic Uniques 3.0 system transformed Mythic from a separate rarity into an item quality that can appear on every Unique. Mythic versions are always Ancestral, receive stronger Unique Powers and roll their other affixes at maximum values. They can drop naturally, come from caches or be created through the Horadric Cube and Jeweler. It is a much broader system than the old arrangement where “Mythic Unique” essentially meant a tiny collection of famous chase items such as Harlequin Crest, Ring of Starless Skies and The Grandfather. (Blizzard's Season 14 explanation)

The redesign has produced interesting buildcraft, but also enough terminology to make even experienced players occasionally stop and inspect the paperwork. There are ordinary Uniques, Mythic-quality Uniques, Iconic Mythics, Crafted tags, slot-specific random crafting, direct upgrades, Resplendent Sparks and several acquisition methods that follow slightly different rules. Some players are already arguing that Mythics no longer feel genuinely Mythic, while others welcome a system where powerful gear is something they can actively work toward rather than merely hope to see before the season ends.

Neither side benefits when the recipe description introduces another layer of ambiguity.

Season 15 Is Making the Difference Much Clearer

Blizzard's current Patch 3.2.0 PTR documentation makes the future structure refreshingly explicit. The Jeweler will continue to use Rune Crafting → Mythic Uniques, allowing players to choose a slot — Blizzard gives examples such as One-Handed Weapon or Ring — and receive a random class-specific Mythic from that slot. The Horadric Cube, meanwhile, gains Upgrade Direct Item to Mythic. That recipe is more expensive, but Blizzard describes it as a complete 1:1 transfer: put in the exact Unique you care about and receive the Mythic version of that exact item while preserving its affixes and modifications. (official Patch 3.2.0 PTR guide)

That is the direction we welcomed when Blizzard revealed that Season 15's Cube would finally preserve the Unique you actually chose. It turns the two crafting methods into understandable alternatives. The Jeweler is cheaper and random. The Cube is expensive and deterministic. Players can decide whether they want to gamble or pay extra for certainty. Diablo is allowed to contain both. In fact, the genre would become rather suspicious without at least one machine that consumes rare materials and quietly laughs.

But that clearer design also makes the September tooltip report easier to diagnose. If Jeweler output is selected from a broader weapon slot, the interface should name that broader slot. A player clicking “Two-Handed Sword” should not need prior knowledge of Blizzard's internal category structure to understand that “Sword” may include a Mace.

This Is More Than Cosmetic Wording When Sparks Are Involved

Normally, a tooltip mismatch would sit fairly low on Diablo IV's current emergency list. This week alone we have covered The Resounding Scream leaving players locked out of Echoing Hatred despite possessing multiple Traces and Nemesis portals still disappearing while players attempt to collect boss loot. Nobody loses access to an entire activity because the Jeweler says Sword and gives Mace.

They can, however, lose expensive crafting materials because they made a decision based on that wording. A player specifically chasing The Grandfather may reasonably be willing to gamble among a pool of Two-Handed Swords but unwilling to gamble across every compatible Two-Handed Weapon. Those are different probabilities. Even if Blizzard never promised the exact Mythic, the size of the possible output pool affects whether pressing the button is a sensible use of Sparks and Runes.

That becomes even more important because Diablo IV's gearing already has enough RNG layered on top of RNG. Transfiguration can create a second endgame gear plateau after the correct base item finally drops, while players have described rare 4GA items becoming disappointing after an irreversible Transfiguration result. Randomness is part of the pleasure. Hidden randomness is where the pleasure begins putting on a coat.

Diablo IV Has Already Had Mythic Crafting Confusion This Month

The Sword/Mace report is not even September's first example of players struggling to understand what Mythic crafting has produced. On September 1, another player reported spending Sparks, Runes and 50 million Gold on Jeweler and Blacksmith crafts because they believed they had received ordinary Uniques instead of Mythics. Other users pointed out that under Season 14's new system those items actually were Mythic-quality versions of ordinary Uniques. The game's modern Mythic presentation had simply made the distinction less obvious than the player expected. (September 1 crafting discussion)

That report and the new Sword/Mace complaint are not the same bug. One concerns players recognizing Mythic quality; the other concerns the apparent naming of the recipe output. Together, however, they highlight the same broader weakness: Mythics have become mechanically richer while the interface has not always become equally good at explaining them.

Season 15's direction should help. our broader Season 15 PTR assessment already identified deterministic Mythic crafting as one of the update's better ideas. The less the player has to wonder what the machine means, the more time they can spend wondering why the item they wanted still refuses to drop naturally after eighty-seven boss kills.

Grandfather Hunters Should Treat the Jeweler as Random Crafting

For now, players chasing one particular Mythic should treat the Jeweler as Blizzard describes it: random crafting within the selected slot, not direct target crafting. If the goal is simply “give me a useful Mythic Two-Handed Weapon,” the Jeweler remains perfectly reasonable. If the goal is “give me exactly The Grandfather,” Season 15's direct Cube upgrade is the much clearer system once those changes arrive.

And if the current Jeweler UI really does display “Mythic Unique Two-Handed Sword” while legally returning Two-Handed Maces, Blizzard should change the wording rather than the crafting logic. “Two-Handed Weapon” would describe the actual lottery. “Random compatible Mythic” would be even harder to misunderstand. Nobody is asking the Jeweler to become less random. We are merely asking him to label the roulette wheel properly.

Diablo players can cope with bad luck. We have nearly thirty years of evidence.

But if the game says Sword and means “Sword, Mace, or whatever the slot table feels like today,” that is not really RNG.

That is a vocabulary problem with three Resplendent Sparks attached.

Diablo 4’s Nemesis Portal Problem Is Still Here in September

2026-09-09T01:01:24.293-07:00

Diablo IV has spent several months trying to answer an unexpectedly complicated design question: how long should a player be allowed to look at loot before the game takes the next boss away? Apparently the answer is still “not as long as some players need.” A fresh September 7 bug report describes a player completing a Nemesis encounter, entering the first portal, killing both bosses inside and then watching the Greater Nemesis portal disappear while they were still collecting the loot those bosses had just dropped. If that sounds familiar, it should. We covered the same disappearing Nemesis portal problem on August 28, after months of complaints about timers, invisible expiration rules and players being forced to choose between sorting their rewards and continuing the encounter. Twelve days later, the portal is apparently still operating on the principle that hesitation is weakness.

The newest report is almost comically concise. Kill the first boss. Nemesis portal appears. Collect loot. Enter portal. Kill both bosses inside. More loot appears. Start picking it up. Greater Nemesis portal disappears. Another player responding to the report says this is connected to the timer Blizzard introduced after Nemesis Lairs were exploited, rather than a completely new bug. That explanation fits the history, but it does little to improve the player experience. Whether the portal is disappearing because of intended anti-exploit logic or unintended persistence behaviour, the practical result remains exactly what players complained about in May: Diablo gives you a mountain of loot, then starts quietly removing your opportunity to continue while you are doing the very Diablo-like activity of looking at it. (September 7 report)

This Problem Originally Arrived With a 30-Second Timer

The story began in May after Blizzard tightened Nemesis Lair behaviour around War Plans. Players suddenly started seeing a warning that the opportunity to enter the next Lair would expire in roughly 30 seconds. That was immediately controversial because Nemesis bosses can drop enough equipment to fill a substantial portion of an inventory, particularly when the player reaches a second-tier Greater Nemesis encounter after already collecting rewards from the previous boss. The original Blizzard forum thread is full of players describing portals vanishing while they salvaged in town, stood over piles of items or simply tried to pick everything up. One player watched the portal disappear after about fifteen seconds. Another said the Greater Nemesis portal vanished before they had collected even half of the double-boss reward pile. (original May reports)

The problem was especially absurd because the portal appears at precisely the moment players are supposed to stop moving. Diablo's fundamental rhythm has not changed much since 1996: kill monsters, inspect loot, equip anything useful, continue killing monsters. The Nemesis system briefly introduced a new instruction between stages two and three: stop inspecting the loot and run. Players adapted, because Diablo players will eventually optimize almost anything, including panic. Grab obvious Greater Affixes, ignore everything else, enter the portal immediately and clean up later. It works. It also makes a loot-driven activity feel like somebody has activated a fire alarm in the Blacksmith.

Blizzard Had a Real Exploit Problem to Solve

There was a legitimate reason for the restriction. Nemesis Lairs arrived through the War Plans system, and players discovered situations where the encounters could be repeatedly triggered or farmed. Blizzard's official Patch 3.0.4 notes later confirmed that Nemesis Boss Lairs could be infinitely farmed in certain scenarios, and the June 10 update fixed that behaviour alongside several other War Plan exploits and progression problems. The same patch also repaired repeatable Greed is Good portals and a Path of Coin issue involving teleporting out and back into an instance. Blizzard clearly had an entire collection of portals developing entrepreneurial ambitions. (official Patch 3.0 notes)

Closing an infinite farming exploit is obviously reasonable. The issue is whether legitimate players should still be inheriting the emergency measure months later. We recently saw almost the same philosophical problem with Treasure Breach runs that can prevent players from teleporting to town while their inventories overflow with Goblin loot. In both cases, Blizzard had a genuine exploit to close. In both cases, the protective mechanism appears capable of making normal players perform inventory gymnastics because somebody else once discovered that a portal could be persuaded to print rewards indefinitely.

The Original Timer Improved — but the Portal Problem Never Really Went Away

Players reported later in May that Blizzard had softened the original 30-second window to approximately two minutes. That was a substantial improvement. Two minutes provides enough time to grab obvious rewards and enter the next encounter without treating every Legendary item as unexploded ordnance. By Season 14, however, things became less clear. Some players no longer saw the explicit countdown at all, while others continued reporting portals disappearing after they spent too long in town or sorting rewards. That is why our August 28 article described the modern behaviour as a kind of “shadow timer”: the portal could still expire, but the urgency was not always communicated clearly enough for players to know exactly when.

The September 7 report suggests that confusion remains. The player does not describe seeing or ignoring an obvious countdown. They simply say the Greater Nemesis portal disappeared while they were looting the two bosses that preceded it. The response explaining the timer even admits uncertainty over whether the current limit is thirty seconds or a minute. That is part of the problem. If a valuable portal is deliberately temporary, Diablo IV should tell the player exactly how temporary it is. “There may be a timer somewhere; veterans remember something about it from May” is not an especially elegant user interface.

Greater Nemesis Makes the Design Conflict Worse

The Greater Nemesis stage exposes the contradiction more clearly than the first portal because the player has already committed to the chain. They entered the Nemesis Lair, completed the encounter and defeated two bosses. The reward pile belongs to that completed step. At the same moment, another portal appears offering the next stage. The player is therefore being asked to choose between evaluating rewards already earned and preserving access to rewards not yet earned.

That is particularly awkward now that Diablo IV's itemization gives players more reasons to inspect equipment. Transfiguration makes potentially valuable Greater Affix items worth considering before salvage, Mythic quality has broadened the range of desirable Uniques and players are carrying Seals, Charms and other progression items alongside ordinary equipment. Even aggressive loot filters do not make every decision instantaneous. Sometimes the correct Diablo decision really is to stand still for twelve seconds and compare two pairs of trousers.

Nemesis portals apparently regard that as a character flaw.

The Best Workaround Is Still Enter First and Think Later

Until Blizzard either removes the expiration behaviour or communicates it much more clearly, the safest strategy remains the same one players developed months ago: when a Nemesis or Greater Nemesis portal appears, enter it before doing serious inventory management. Pick up anything obviously valuable, step through the portal to establish the next area and then deal with the bags if the new instance allows a safe town trip. In a party, players have also reported using one member to hold the next instance while another finishes looting, although that is hardly a satisfying solution for solo players.

The Lost Items stash can rescue some abandoned Legendaries and Uniques, but it is not a substitute for collecting rewards normally. It has limited capacity, does not solve every material or item concern and certainly does not help players decide which Greater Affix item was actually worth preserving. We have spent much of the last week documenting strange forms of loot anxiety: players reporting entire stash tabs suddenly empty, Longtooth reportedly consuming Mythic Tribute runs without delivering the expected reward and high-tier gem salvage once again raising questions about missing progression. The Nemesis problem is less catastrophic than those. It simply makes the act of receiving loot unnecessarily stressful.

September’s Report Shows the August Story Wasn’t Finished

That is why the new report deserves a follow-up rather than another full reinvention of the story. When we wrote about disappearing Nemesis portals on August 28, the open question was whether Season 14's altered or invisible timing rules were still catching players after the original exploit fixes. On September 7, another player independently described exactly that outcome: kill bosses, loot drops, Greater Nemesis portal disappears before the looting is finished. The forum report was still active the following day.

There is still no evidence that every Nemesis portal disappears unusually quickly, and some of this behaviour may remain intentionally tied to Blizzard's anti-exploit timer rather than being a traditional bug. That almost makes the design issue easier to state. If it is intended, communicate the timer clearly and give players enough time to interact with the rewards. If it is not intended, fix the persistence. Either route is preferable to leaving players guessing how quickly they need to abandon the previous boss's loot.

Diablo IV is supposed to make players excited when another boss portal appears.

It should not make them afraid to read the item that just dropped.

Diablo 4’s Resounding Scream Quest Is Still Locking Players Out of Echoing Hatred

2026-09-09T00:45:11.328-07:00

Diablo IV's Echoing Hatred has always asked players to overcome one unusually difficult first boss: actually getting inside. Trace of Echoes is intentionally rare, and some players have spent extraordinary amounts of time waiting for one to drop. But a fresh September 9 report shows an even less satisfying version of the problem. This player has already found three Trace of Echoes. The Resounding Scream quest acknowledges the objective with a nice reassuring check mark. The Seer is standing exactly where she should be. And absolutely nothing happens.

The player says the priority quest remains stuck on “Bring the Trace of Echoes to a Seer”, except the objective is greyed out and marked complete. They cannot interact with the Seer, the nearby pedestal remains unchanged and obtaining more Traces through Kurast Undercity has not moved the quest forward. The result is not merely an untidy quest journal. The player says they remain unable to complete the associated seasonal objectives because Echoing Hatred itself never properly unlocks. This would be irritating enough as a fresh Season 14 bug. Unfortunately, players have been describing variations of precisely the same Resounding Scream soft-lock since the beginning of May.

The Trace Dropped. The Quest Updated. Then Diablo 4 Stopped Listening

Blizzard's intended sequence is straightforward by Diablo standards, which admittedly means there are fewer than nine currencies involved. Echoing Hatred is one of Lord of Hatred's major endgame activities. Blizzard describes it as a hyper-rare escalating survival challenge where players battle increasingly difficult waves of Mephisto's forces until the build, player or keyboard finally admits defeat. Access begins when an incredibly rare Trace of Echoes drops. The player takes that Trace to the Sightless Eye in Temis, offers it and gains access to Echoing Hatred.

We have already covered the first half of that problem extensively. In July, players reported going more than 90 hours without seeing a Trace of Echoes, and earlier this week we revisited the wider question of whether Diablo IV's activity keys are becoming rarer than the loot they unlock. The September 9 player has successfully cleared that hurdle three times. The problem is that the front door still refuses to open.

According to the new report, The Resounding Scream displays the Trace delivery objective as completed, yet the quest cannot progress. There is no useful interaction with the Seer and no change at the pedestal. The player has collected three Traces from Undercity runs without changing that state. It is difficult to blame bad RNG when the inventory contains multiple copies of the object RNG was supposed to provide.

Players Were Reporting the Same Checkmark in May

The oldest large bug reports date back to the first days of May. On May 1, one player said a Trace of Echoes triggered The Resounding Scream correctly, but arriving at the Seer produced no useful interaction. Other players immediately began reporting the same state: “Bring the Trace of Echoes to the Seer” showed a check mark, but nothing followed it. Restarting Diablo IV, changing difficulty, changing zones, tracking and untracking the quest and returning later did not consistently solve the problem.

A separate May 11 thread documents an even stranger failure. The player successfully handed in the Trace, watched the Seer perform the ritual and saw the Sightless Eye appear. The Eye was not interactable. After restarting the game, even that visual clue disappeared. The quest remained in the Journal but its Objective section became completely blank, the Seer could no longer be used and tracking the quest produced no destination. Other players confirmed the exact same progression state through May and June.

At that point The Resounding Scream stops behaving like a quest and begins behaving like an old Windows shortcut whose original file was deleted three months ago. The icon is still there. Clicking it merely reminds you that something used to happen.

Some Players Have Been Locked Out of the Activity Entirely

The consequences are more substantial than losing one quest reward. The Resounding Scream is the introduction to Echoing Hatred. If the Sightless Eye never becomes usable, the affected character can remain locked out of one of Lord of Hatred's headline endgame systems. Echoing Hatred was advertised alongside War Plans as a major expansion feature, and our original breakdown of Blizzard's new endgame systems focused on precisely why the mode sounded interesting: endless scaling waves, randomized enemy combinations and better rewards the longer the build survives.

For affected players, none of that matters very much. They can read about Echoing Hatred. They can find the extraordinarily rare entry item. They can even find several of them. They simply cannot complete the introduction that makes the system usable. One May player described being excluded from Echoing Hatred for weeks while continuing to find additional Traces. Another reached June with the same quest still stuck. The problem then crossed into Season 14: on July 3, a Solo Self-Found player reported that the Eye appeared during the ritual but became non-interactable, then disappeared after a restart while the blank quest remained in the Journal. A second player confirmed the same problem a week later and specifically noted that it prevented seasonal reward progression.

There Is a Player-Discovered Workaround — but It Involves Starting Another Character

The closest thing to a consistent workaround appeared in June, and it is not exactly elegant. One affected player created another character that had not yet attempted The Resounding Scream, obtained a Trace of Echoes on that character and completed the unlock successfully. Another player then tried the same approach: they created a new character, had it power-levelled to 70, transferred their equipment over, farmed until another Trace dropped and completed the quest there. Afterward, their original bugged character reportedly showed the Sightless Eye correctly and the quest appeared completed.

That is encouraging if your definition of “fix” includes create another hero and redo a meaningful chunk of progression. The player said the process cost them glyph progression and War Plan progress on the replacement character, so this is less a workaround and more a small relocation programme.

One player suspected changing difficulty after receiving the Trace may have contributed to their original bug, while others mentioned entering Temis or Echoing Hatred-related areas through somebody else's party before completing their own unlock. Those theories remain unconfirmed. The important point is that multiple affected players have experienced the bug while playing solo as well, so party interaction clearly cannot explain every case.

Blizzard Has Already Fixed a Different Sightless Eye Interaction Bug

There is one especially curious detail buried in Blizzard's June 30 Patch 3.1.0 notes. Blizzard fixed an issue where ineligible players in a party could interact with the Sightless Eye Pedestal. That was obviously incorrect and needed fixing. The current Resounding Scream reports describe almost the philosophical opposite: eligible players who possess the required item cannot interact with the system they are supposed to unlock.

To be clear, Blizzard never claimed that June fix addressed The Resounding Scream soft-lock. It concerned party members accessing the pedestal when they should not have been able to. We could not find a current public patch note documenting a comprehensive fix for the stuck Seer, blank objective or non-interactable Sightless Eye reports. The distinction matters because otherwise it would be tempting to describe this as a failed fix. It is more accurate — and perhaps stranger — to say Blizzard has already repaired one edge case around who can use the pedestal while a separate multi-month problem continues preventing some legitimate players from using it at all.

Echoing Hatred Has Accumulated an Impressive Collection of Access Problems

This is also not the first time the activity has created friction before the actual combat begins. Players have spent months arguing about Trace of Echoes rarity, prompting Blizzard to increase the drop rate of Echoing Hatred keys from Elites and Champions. That helped players who simply could not find one. Then there is the PlayStation side: PS5 players still report that the Echoing Elites trophy may count bosses while ignoring ordinary elites, turning a 1,000-enemy trophy into something that can require dramatically more runs than expected.

Those problems combine in a particularly unfriendly order. First you need the rare Trace. Then the introduction needs to function. Then you need enough additional access to run Echoing Hatred repeatedly. And if you are chasing the PS5 trophy, the tracking also needs to count the enemies the description says it counts. Echoing Hatred itself is supposed to be the hard part. Increasingly, it feels as though reaching the activity with every surrounding system behaving correctly is the qualifying round.

The Seasonal Objective Makes the Soft-Lock Worse

The September 9 player specifically says the broken quest is preventing them from completing seasonal objectives. That turns the issue from optional endgame inconvenience into progression friction. Blizzard has already made the rarity of Trace of Echoes slightly awkward by connecting Echoing Hatred to seasonal objectives; our recent look at rare activity keys argued that there is a fundamental difference between making a reward rare and making permission to play the content rare.

A quest bug creates an even harsher version. RNG can eventually produce a Trace. The September player has proved that three times. A corrupted quest state does not necessarily improve because you continue farming. It simply consumes additional rare keys while the Seer maintains the serene expression of somebody who has absolutely no intention of helping.

That is why this deserves more attention than an ordinary side quest marker failing to disappear. The affected player cannot simply ignore The Resounding Scream and access the activity another way. The quest is the doorway.

Season 15 Is Almost Here, and This Began in Season 13

The longevity is the uncomfortable part. Reports began during Season 13 in early May. They continued through the end of that season. Season 14 launched at the end of June, and another SSF player documented the same blank-objective state in July. Now, on September 9, with Season 15 approaching and players already debating whether the next season solves enough of Diablo IV's older problems, The Resounding Scream has produced another textbook report.

There is no evidence that every account is vulnerable. Plenty of players have unlocked Echoing Hatred normally, and the activity itself is obviously being completed every day. We also do not know whether the May, July and September cases all share one technical cause. A quest can reach the same broken state through several different bad triggers. But the visible outcome is remarkably consistent: Trace acquired, Seer approached, objective marked or ritual initiated, then progression stops.

A Rare Key Should Not Unlock a Broken Door

Echoing Hatred's scarcity is deliberate. Blizzard wanted finding a Trace of Echoes to feel like discovering access to something unusual and dangerous. That design can work. A rare key dropping unexpectedly in an ARPG creates exactly the sort of “one more run” excitement Diablo has lived on for decades.

What does not work nearly as well is finally obtaining that key and discovering the lock has entered a contemplative phase.

The September 9 player has found three Traces. The quest shows the delivery objective as complete. The Seer cannot be interacted with. The pedestal remains unchanged. Seasonal progression is blocked. Players were reporting the same fundamental problem in May, found a new-character workaround in June and reproduced it again in Season 14.

Echoing Hatred asks how long your build can survive against an endless army of demons.

Some Diablo IV players are still stuck on the earlier challenge: how long can they survive standing next to the Seer?

Diablo 4’s BlizzCon Twitch Drops Will Take Six Hours to Unlock

2026-09-09T00:27:25.858-07:00

BlizzCon returns this weekend, and Blizzard has found a traditional way to make sure Diablo IV players remain close to a screen while Sanctuary's future is revealed: three new Twitch Drops requiring six hours of total viewing to collect them all. Blizzard's newly published Diablo guide for BlizzCon 2026 confirms that viewers can earn a Dagger after two hours, an Axe after four and a Two-Handed Mace after six. The campaign runs from September 12 through September 15, giving players several days rather than forcing everyone to sit through six uninterrupted hours while attempting to explain to their families that this is technically weapon acquisition.

The timing is unusually good for Blizzard because this is not shaping up to be a routine Diablo convention. The company says the BlizzCon Opening Ceremony will reveal “extensive plans” for the future of Sanctuary, Saturday includes a full Diablo Developer Update, and Sunday brings the dedicated Diablo IV: What's Next presentation. As we already discussed in our look at Diablo IV's unusually important BlizzCon schedule, Blizzard deliberately kept some Season 15 content out of the PTR because it wanted to reveal it at the convention. So if you were going to spend six hours watching Diablo streams anyway, Blizzard has now thoughtfully attached three sharp objects to the experience.

Here Are the Three Diablo 4 BlizzCon Twitch Drops

According to Blizzard's official BlizzCon 2026 Diablo preview, the Twitch Drop campaign begins on September 12 at 10:00 a.m. PDT / 7:00 p.m. CEST and ends on September 15 at 9:59 a.m. PDT / 6:59 p.m. CEST. View any eligible stream in the Diablo IV category during that window and your cumulative watch time progresses toward three cosmetic weapon rewards:

2 total hours: Serrated Skean Dagger
4 total hours: Corroded Cleaver Axe
6 total hours: Tintinnabulation Two-Handed Mace

You therefore need six hours total to collect the complete set. The important word is total. Blizzard does not require six hours for each reward, meaning this is one cumulative six-hour progression track rather than eighteen hours of concentrated Diablo broadcasting. You can also switch between eligible Diablo IV channels without losing progress, so nobody is required to swear lifelong allegiance to one streamer just because the Dagger meter has reached 73%.

Watching several streams simultaneously does not accelerate the process, however. Blizzard specifically says Drop progress cannot be earned faster by running multiple eligible channels at once. Background streams or inactive browser tabs may also fail to contribute toward the viewing requirement, so the old strategy of opening twelve Twitch tabs, muting civilization and returning six hours later is not officially endorsed by the Horadrim.

You Do Not Need to Own Diablo 4 to Earn the Drops

One useful detail is that you do not need to own Diablo IV or Lord of Hatred to earn progress toward the Drops. A Battle.net account linked to Twitch is enough to participate. That makes the campaign available to people who are simply watching BlizzCon to see whether this is finally the moment that convinces them to return — or perhaps buy the game for the first time.

That audience could matter more than usual. We recently looked at Diablo IV's unusually quiet Steam population heading into Season 15, with the obvious caveat that Steam represents only one part of the total player base. BlizzCon is Blizzard's best opportunity this year to create a new spike of interest, and the company has deliberately preserved several announcements for the weekend rather than revealing everything during the PTR. Free cosmetics will not revive a seasonal population by themselves, but they are a fairly efficient way to make sure potential returning players are paying attention when the larger announcements arrive.

Do Not Watch on Your Smart TV If You Want the Drops

There is one particularly important practical warning. Blizzard says Twitch Drops can be earned through a PC or Mac web browser and the Twitch apps on Android or iOS. Twitch applications on game consoles, Smart TVs and other television apps do not support the Drops. That means sitting down for the entire BlizzCon Opening Ceremony on the living-room television may produce an excellent large-screen view of whatever Blizzard announces and precisely zero progress toward your Serrated Skean.

Players should also make sure their Twitch and Battle.net accounts are linked before relying on the campaign. Once a reward has been earned, it must be manually claimed either from the stream or through Twitch's Drops Inventory. Blizzard says earned rewards can expire seven days after being claimed if a Battle.net account has not been connected, which is a surprisingly bureaucratic way for a demonic dagger to disappear.

Six Hours Should Be Easy During This BlizzCon

Ordinarily, six hours of required Twitch viewing could feel slightly aggressive for three cosmetic weapons. This weekend, however, Diablo alone has enough programming to make the requirement fairly easy to hit naturally. Saturday's Opening Ceremony begins at 10:15 a.m. PDT, followed later by the Diablo Developer Update and The Art of Darkness: Behind Diablo IV's Cinematics. Sunday then brings Diablo IV: What's Next at 11:00 a.m. PDT, along with additional Diablo programming and creator streams throughout the show.

There is also rather more mystery surrounding those panels than usual. Blizzard has already told us Season 15's PTR was intentionally incomplete, something that helped fuel our recent look at the possibility that hidden Season 15 content could point back toward Westmarch and Malthael. Separately, Blizzard and CD Projekt Red have described Geralt's Diablo IV appearance as the beginning of a wider Witcher partnership and promised more information at BlizzCon. None of that guarantees a particular reveal, but it does mean people are likely to be watching the broadcasts for reasons slightly more substantial than collecting an axe with an unpleasant corrosion problem.

The nostalgia side is unusually strong too. the original Diablo will be playable at BlizzCon alongside Diablo II and Diablo III, adding another curious piece to this year's continuing Diablo 1 remaster speculation. And somewhere behind the convention curtain there is still the unresolved question of whether Blizzard deliberately saved a Diablo IV Switch 2 announcement for BlizzCon after skipping Gamescom. Six hours may therefore vanish surprisingly quickly.

There Is Also a Separate Diablo Twitch Badge

Blizzard is running another Twitch promotion alongside the weapon Drops, although this one is not free. Between September 12 and September 26, viewers can earn a special Diablo 30th Anniversary Twitch chat badge by purchasing one subscription to a creator streaming in an eligible Diablo category. Diablo II: Resurrected, Diablo III, Diablo Immortal and Diablo IV all count. The badge is separate from the three Diablo IV weapon Drops, so buying a subscription does not replace the six-hour viewing requirement, and watching six hours does not award the badge.

That distinction is worth remembering because Blizzard has attached quite a few digital rewards to BlizzCon this year. Attendees who correctly link their BlizzCon Pass to Battle.net can receive applicable viewership rewards through the event system, while everyone watching remotely needs to follow the normal Twitch Drop requirements.

BlizzCon Weekend Starts September 12

For European Diablo players, the useful number is therefore 7:00 p.m. CEST on Saturday, September 12. That is when Twitch Drop progress begins. Two hours gets the Serrated Skean, four gets the Corroded Cleaver, and six finishes the set with Tintinnabulation. You have until early evening on September 15 to complete the requirement, and you can spread the viewing across different eligible Diablo IV channels and multiple days.

More importantly, those six hours coincide with what may be Diablo IV's most consequential BlizzCon since launch. Season 15 still has deliberately hidden content, Rebirth is finally returning to simplify the seasonal reset, Blizzard is promising broader plans for Sanctuary, and Sunday's What's Next panel has been positioned as the place where at least some of the missing pieces finally become visible.

So the requirement is six hours.

Considering how much Blizzard appears to be saving for this weekend, the larger danger may be accidentally watching twelve.

Diablo 4’s Xbox Friends List Has Been Broken Since Season 14

2026-09-08T02:00:11.003-07:00

Diablo IV contains an impressive selection of creatures designed to make players feel alone. Demons crawl from the ground. Entire villages have been murdered before you arrive. Mephisto spends an extraordinary amount of time explaining why trusting anyone is probably a mistake. Xbox players have apparently discovered a more efficient system: simply make the Friends and Clan lists forget who is online. Players say Diablo IV's Xbox social interface has been behaving incorrectly since the beginning of Season 14, with friends appearing offline, Clan rosters showing empty or unnamed entries and chat messages disappearing. A Blizzard forum thread that began in July received another detailed confirmation on September 7, meaning some Xbox players have now been reporting the same problem for more than two months.

This is not merely somebody discovering that one friend had sensibly gone outside. Multiple Xbox Series X players describe the same recognizable pattern. When Diablo IV starts, friends and Clan members who were already online frequently appear offline or do not appear at all. Players who log in after the affected Xbox user can begin appearing normally, and some lists gradually populate after the game has been running for a considerable period. One player says the same Diablo IV account and Clan work normally when played on Steam Deck, which makes an Xbox-specific Diablo IV or Battle.net presence synchronization problem a reasonable suspicion. Blizzard has not publicly confirmed that diagnosis, so for now it remains player evidence rather than an official technical explanation. (Blizzard forum thread)

The September 7 Report Says the Bug Has Lasted All Season

The newest update came on September 7 from an Xbox player who says the problem has existed since the beginning of Season 14. When they log into Diablo IV, Clan members who were already playing show as offline. If somebody logs in afterward, that person appears correctly. Clan chat can also fail to display messages. Crucially, the player says they use the same Battle.net account and the same Clan on Steam Deck, where existing online members display normally. That comparison removes quite a few ordinary explanations such as an empty Clan, inactive friends or incorrect Battle.net relationships. The social information exists. Diablo IV can display it. This particular player says the Xbox version simply does not display it properly. (September 7 update)

The player also says normal Xbox troubleshooting has not solved the problem and asks whether it will finally be fixed before Season 15. That is a reasonable question at this point. Season 14 is approaching its end, Season 15 is already carrying a sizeable list of player hopes and unresolved complaints, and social functionality is not exactly an experimental endgame mechanic. Diablo IV launched with parties, Clans and cross-platform play more than three years ago. Knowing whether your friend is online should ideally be somewhat less complicated than calculating whether a Transfiguration roll improves a four-Greater-Affix amulet.

The First Reports Appeared Around the Start of Season 14

The main Xbox thread began on July 11, but the original poster said the problem had already been happening for roughly two weeks. Two Xbox Series X consoles using two different accounts were reportedly affected despite extensive troubleshooting: restarting the router, checking NAT, clearing the Xbox cache, hard-resetting the consoles and verifying account status did not help. Other Xbox users quickly joined the thread. One said the issue began with Season 14 and described their Clan list as empty when logging in, only gradually filling as people came online afterward. Another said communicating with friends had become difficult enough that they were texting or calling people outside the game to discover whether they were actually playing. (original Xbox report)

A separate July 2 thread contains an even larger collection of similar reports. Players describe completely blank Friends and Clan lists, faceless entries with missing names, online players showing offline and extremely long delays before the interface catches up. One user said that after leaving Diablo IV running for around 45 minutes, only six or seven friends had finally appeared. Another could receive party invitations from somebody who was not visible in their Friends list at all; after playing together for around twenty minutes, that person eventually appeared. Several Xbox players said Battle.net's mobile app or other platforms showed the social information correctly while Diablo IV on Xbox did not. (second Xbox social thread)

There is something wonderfully old-fashioned about needing a telephone to discover whether somebody is online in a game connected permanently to the internet.

Clan Rosters Can Show 150 Members — and Apparently Nobody in Them

The Clan side of the bug may be even stranger. A July 29 Xbox Series X report describes a full Clan showing 150/150 members while the actual roster contains empty slots and everybody appears offline. According to that player, the situation had persisted for more than a month despite multiple Diablo IV patches. Another user replied that many players were experiencing the same behaviour, and the original reporter included screenshots intended to demonstrate the empty roster. (Clan roster report)

That distinction is important because this does not look like ordinary connection loss. The game can apparently know that the Clan contains 150 people while simultaneously failing to populate those people's identities and presence correctly. Some affected users also report missing Clan chat messages, which suggests the problem may involve more than one visual list. Again, we should be careful not to diagnose Blizzard's backend from forum behaviour alone. But the player's repeated Steam Deck comparison is useful: same account, same Clan, working social data on Steam Deck, broken or delayed data on Xbox.

Blizzard Has Already Patched One Friends List Issue This Season

Blizzard's own patch notes make the timeline slightly more interesting. Patch 3.1.1 on July 14 included a specific fix for the Friends list: the Solo Self-Found icon could fail to appear on a player's profile in the Friends list, and Blizzard corrected it. That proves the social interface was receiving attention during Season 14. The same patch fixed several other multiplayer issues, including a bug where only one party member could receive Tower rewards. But the current public patch notes contain no matching fix for the broader Xbox Friends/Clan presence problem described in these threads. (official Diablo IV patch notes)

That makes for an unfortunate contrast. The game can now correctly show whether somebody is Solo Self-Found. Some Xbox players would first like it to correctly show whether that somebody exists. We covered the Tower fix at the time because Solo Self-Found and multiplayer systems depend on Diablo IV being very clear about who is participating and under which rules. The same principle applies here. Presence information seems mundane compared with loot tables or class balance, but it is the front door to actually playing with other people.

This Hurts Diablo More Than It Would Hurt a Purely Solo Game

Diablo IV can certainly be played alone, and plenty of people prefer it that way. But Blizzard has increasingly built systems that reward or encourage group activity. Boss farming is faster with coordinated groups, parties can share difficult encounters, Clans organize seasonal play and Battle.net cross-play exists precisely so friends are not separated by hardware. We have already covered how earlier co-op bugs made Season 12 party play considerably more awkward than it needed to be, and Ultimate Nemesis groups have had their own problems with party members completing the encounter without receiving equal loot.

Those are gameplay bugs. The Xbox social problem happens before gameplay begins. If friends appear offline, Clan members cannot easily see who is available, messages disappear and party invitations become unreliable, players need external apps simply to arrange the activity Diablo IV already supports internally. Discord can solve much of that, of course. So can WhatsApp. So can leaning out of a window and shouting toward your friend's house. None of those should really be required because the Xbox social panel has entered an existential crisis.

One Player Says Blizzard Support Told Them the Issue Was Known

There is one potentially encouraging detail, although it needs a clear caveat. A player in the main thread says they opened a support ticket and received a response from a Game Master stating that Blizzard was aware of the issue and encouraging players to continue posting on the forums. We cannot independently verify that private support response, and Blizzard does not appear to have made an equivalent public statement in the patch notes or forum thread. It should therefore be treated as a player's account of their support conversation rather than formal confirmation from Blizzard. (Blizzard forum thread)

If accurate, though, it would explain why the reports have continued without affected users finding a reliable local fix. Many have already performed the standard console rituals: restart everything, clear cache, toggle cross-play, log out, log back in, inspect NAT settings and stare accusingly at the router. One user reported temporary success after disabling cross-play options, restarting the Xbox, re-enabling them and restarting again, but other reports continued afterward. There is no evidence that this sequence is a universal workaround.

This Does Not Look Like the July Xbox Outage

It is also useful to separate the social bug from broader Xbox service problems. Microsoft experienced an Xbox outage in late July that temporarily affected Diablo IV access for some players, and those service problems were subsequently resolved. The Friends/Clan issue predates that outage and persisted after Xbox services returned to normal. Players in the relevant forum discussion explicitly noted that the social-list problem had already been occurring beforehand. That makes the July outage a poor explanation for a bug reportedly lasting throughout Season 14.

Yesterday we looked at another strange piece of the Microsoft/Diablo relationship in Xbox's coming 15-hour Cloud Gaming limit and the fact that Diablo IV still is not normally available through Microsoft's own cloud service. Today's problem is considerably smaller in corporate terms but more immediate for people already playing on Xbox. Microsoft owns Blizzard. Battle.net provides Diablo's cross-platform social layer. Xbox provides the hardware and network. Somewhere in that impressively well-funded chain, some players say the list showing who is online has spent an entire season needing several minutes — or considerably longer — to remember.

Season 15 Is a Good Deadline for Something This Basic

Season 15 provides a natural point for Blizzard to resolve the issue, assuming the reports describe a reproducible Xbox-side bug. New seasons bring returning players, fresh characters and the inevitable flurry of messages asking who is playing what class. Warlock already looks capable of attracting plenty of Season 15 attention, while Blizzard has deliberately withheld some seasonal surprises for BlizzCon. It would be unfortunate if Xbox players returned for all of that and discovered that every member of their Clan had apparently chosen the same build: Offline.

There is still no evidence that every Xbox player experiences the problem, and reports vary in severity. Some lists eventually populate. Some players can still accept direct invitations. Others describe friends remaining invisible, Clan chat becoming unreliable or party joining timing out entirely. What matters is the consistency of the core behaviour across multiple independent reports since late June and July, followed by another detailed confirmation on September 7.

Diablo IV’s Social Tab Should Not Be the Hardest Boss in the Party Finder

Compared with disappearing stash items, broken damage multipliers or a Secret Cow Level quest that can stop before producing its required key, a broken Friends list sounds almost quaint. Nobody loses a Mythic. Nobody's Hardcore character dies. No boss consumes an expensive Tribute. But multiplayer games depend on a layer of invisible infrastructure that only becomes noticeable when it stops working. Friends lists are part of that infrastructure. Clan rosters are part of it. Presence synchronization is boring right up until everybody you know apparently vanishes.

Xbox players began describing this problem around the start of Season 14. They reported it throughout July. It remained in August. On September 7, a player using the exact same account on Steam Deck said Xbox still shows existing online Clan members as offline while the Steam Deck displays them correctly.

Season 15 is nearly here.

It would be nice if the Friends list arrived before it.

Diablo 4 Players Are Reporting Entire Stashes Suddenly Disappearing

2026-09-08T01:46:50.937-07:00

Diablo IV players spend an extraordinary amount of time deciding what deserves to live in the stash. Mythics go in. Greater Affix items go in. Interesting Uniques go in. Perfectly ordinary equipment that might become useful after three future balance patches also goes in, because Diablo players are nothing if not optimistic archaeologists of their own bad decisions. The arrangement generally works because there is one reassuring assumption beneath all of that hoarding: when you open the stash tomorrow, the things you put there yesterday will still exist. A pair of fresh September reports are making that assumption slightly less comfortable.

On September 8, a returning PC player reported logging into Diablo IV during Lord of Hatred and finding their entire stash empty. Two days earlier, another PC player said a stash tab suddenly became empty while moving keys between characters. Neither report currently has enough independent confirmation to establish a widespread stash-loss bug, and returning players in particular can sometimes encounter completely legitimate seasonal-transfer rules that make old items disappear after the Withdraw Only window expires. But the new complaints are uncomfortably similar to a much more detailed May report where a Season 13 player said all stored items and purchased additional stash tabs vanished while their character remained in the same active season. That older report became active again on September 8. (September 8 report)

A Player Returned on September 8 to Find the Stash Empty

The newest report is straightforward. The player says they had not played for a while, returned during Lord of Hatred and discovered that everything in the stash was gone. They explicitly linked their experience to an older thread titled “Seasonal Stash completely empty + purchased tabs gone after finishing Lord of Hatred campaign,” saying they had already replied there without receiving an answer. There are important unanswered questions — most notably which realm and season originally held the missing items — so this specific case cannot yet be confidently labelled a bug. If the equipment was left behind in an expired seasonal Withdraw Only stash, the disappearance could be expected behaviour rather than deleted account data.

That distinction matters. When a Diablo season ends, seasonal items are transferred through temporary storage rather than preserved forever in an infinitely expanding warehouse beneath Kyovashad. Players who stay away long enough can lose unclaimed seasonal items once that transfer window expires. So “I came back after months and my old seasonal stash is empty” is not automatically proof that Blizzard misplaced anything. What makes the September report worth watching is that it points directly toward another case where the normal seasonal explanation does not fit nearly as comfortably.

The May Player Says Everything Vanished During the Same Season

On May 1, shortly after Lord of Hatred and Season 13 launched, a PC player described creating a Seasonal Paladin, finishing the campaign, farming equipment and filling their stash. They then took a single day away from the game. When they returned and created a Warlock, the Paladin's stash was completely empty. According to the report, all stored items had disappeared and all purchased extra stash tabs were gone, leaving only the default storage. Equipped gear remained on the Paladin, and the character was still correctly marked Seasonal. The player says they restarted the client, switched characters and even completely reinstalled Battle.net and Diablo IV. Nothing restored the missing storage. (original May report)

That case is much harder to explain through ordinary season rollover because the player explicitly says the disappearance occurred inside the current Season 13 after only a day away. There was no old seasonal transfer waiting to expire. There was no character migration to Eternal. The stash simply appeared to reset while the seasonal character itself remained intact. We cannot independently verify the contents of the player's account, and Blizzard has not publicly confirmed what caused the report, but the details are specific enough to make it considerably more concerning than an ordinary returning-player misunderstanding.

A Separate September 6 Report Says One Stash Tab Emptied Too

There is also a second current report from September 6. Another PC player says they were moving a collection of keys to another character when an entire bank tab suddenly became empty. The post is extremely brief and currently lacks the detail needed to determine exactly what happened, but its timing is interesting: within two days, one player reports an individual stash tab emptying and another reports returning to find the entire stash gone. (September 6 report)

That still does not make this a widespread September epidemic. Two fresh reports are two fresh reports. Diablo IV has millions of accounts, and a bug headline should not quietly transform “two people on the forum” into “Sanctuary has eaten everybody's inventory.” But because the consequences are potentially so severe, even isolated reports deserve considerably more attention than something like a cosmetic animation flickering for half a second. Losing a stash can mean losing months of accumulated Uniques, crafting candidates, Mythics, boss materials and the small mountain of “maybe someday” equipment every veteran player insists is strategically essential.

The Stash Is Already Doing Far More Work Than It Used To

The timing is particularly uncomfortable because Diablo IV's stash has become increasingly important as the game has added systems. Lord of Hatred brought Talismans, Seals, Charms, War Plans and additional layers of equipment progression. Season 15 is preparing even more build experimentation, while Transfiguration gives players another reason to keep potentially useful Greater Affix items instead of immediately salvaging them. The stash is no longer just somewhere to keep two spare helmets and an embarrassing collection of gems. It is increasingly the archive behind the entire account.

That is why we noted during our Season 15 PTR review that inventory bloat is becoming a design problem of its own. Every new form of buildcraft introduces another category of things players reasonably want to preserve. Even when the stash works perfectly, deciding what stays has become one of Diablo IV's unofficial endgame activities. When a player believes an entire tab has vanished, “perhaps we needed more storage space” suddenly becomes a less urgent philosophical debate.

Diablo IV Has Had Several Strange Loot-and-Stash Problems Recently

September has already given players a remarkable selection of ways for loot management to become unexpectedly stressful. We recently covered Treasure Breach runs where players can receive more loot than they can carry while town teleporting remains unavailable. A separate report described boss rewards apparently skipping the ground and appearing directly in the Lost Items stash. And just two days ago, a PS5 player reported high-tier gem progression disappearing after salvage, raising uncomfortable memories of an older gem-fragment bug Blizzard had already patched.

Those incidents almost certainly do not share one underlying cause. One concerns teleport restrictions, another Lost Items behaviour, another gem conversion and the newest reports concern stored inventory. Connecting them technically would be pure speculation. What they do have in common is player trust. Diablo is a game about obtaining things. If the game tells you something dropped, moved, salvaged, transferred or entered storage, players need absolute confidence that the item state being shown is real. An ARPG can survive the Butcher killing you. It becomes considerably harder to enjoy if the filing cabinet develops predatory instincts.

Some “Missing Stash” Reports Are Actually Normal Seasonal Behaviour

This is also why anyone discovering an empty stash should check the obvious explanations before assuming account data has been deleted. First confirm whether the missing equipment was seasonal or Eternal. If it belonged to a previous season, consider how long it has been since that season ended and whether its Withdraw Only stash was ever emptied. Check every relevant character and realm, restart Battle.net and verify that the game has connected to the correct account. A surprisingly large amount of apparent missing-item drama in seasonal ARPGs eventually turns out to involve progression transfers rather than vanished server data.

But those explanations do not neatly cover the May Season 13 report, where the player says their stash disappeared while the same season was still active. Nor do they obviously explain the September 6 player who says one tab emptied while transferring items between characters. Those are the cases Blizzard needs to investigate if the reports are accurate, because they involve storage disappearing during normal account use rather than after an old season's cleanup window.

Do Not Panic — But Screenshots Are a Very Good Idea

There is currently no evidence that Diablo IV players should begin emptying their stashes or moving everything onto characters. In fact, frantic inventory rearrangement would probably create more opportunities to accidentally salvage or discard something than it would solve. The reports are still too limited for that. What experienced players may reasonably want to do is keep occasional screenshots of important stash tabs, particularly Mythics, perfect Greater Affix items and other difficult-to-replace equipment. Screenshots will not restore an item, but they provide considerably better information for a support or bug report than “I definitely had some very good trousers somewhere.”

The same applies to newly purchased stash tabs. If a player notices tabs or stored items disappearing, document the account state before changing characters repeatedly, purchasing replacement tabs or moving other gear around. The more precisely players can identify what vanished and what action preceded it, the easier it becomes to distinguish a genuine storage bug from seasonal transfer behaviour or a UI problem.

Diablo Is About Losing Characters — Not Filing Cabinets

Diablo has always been unusually comfortable with loss. Hardcore characters can vanish permanently because somebody became overconfident around a boss. Valuable crafting resources can disappear because the Occultist disagreed with your preferred affix fifteen times in succession. Players can apparently even lose a Mythic Tribute when Longtooth decides not to provide the corresponding loot. Those experiences may be painful, but at least there is supposed to be a game mechanic behind them.

A stash is different. It is the place where Diablo tells you the things you are not currently using are safe.

The September 8 returning-player report still needs more context and may ultimately have a perfectly normal seasonal explanation. The September 6 empty-tab report needs considerably more detail. But the May case — an active Seasonal character, one day away, items and purchased tabs apparently gone — remains difficult to explain away, and that thread has now returned to the surface months later.

For the moment, this is something to watch rather than a reason to panic.

Because Sanctuary is allowed to take your life.

It really should leave the stash alone.

Diablo 4 Players Say One Sorcerer Build Is Doing as Little as 1/20th of Its Intended Damage

2026-09-08T01:33:21.700-07:00

Diablo IV's Sorcerer has received plenty of numerical help lately. Blizzard has buffed damage, adjusted Intelligence scaling and spent much of 2026 sanding down individual skills that were not behaving quite as advertised. Unfortunately, there is an old problem with making the numbers bigger: first the numbers have to actually turn up. Players testing Spark's Electric Blast upgrade together with Vox Omnium say two separate damage bonuses are still failing, leaving one potentially interesting Sorcerer setup doing a fraction of the damage its tooltips suggest. The original controlled testing put the combination at roughly one-eighth of its expected output. A new September 6 comment goes further, with another player calculating that their complete build would produce only around one-twentieth of its intended damage once all the missing multipliers are considered.

That 1/20 figure is not an official Blizzard measurement, and it should not be treated as proof that every Electric Blast build loses exactly 95% of its damage. It is one player's calculation for a specific build. What is considerably easier to document is the underlying problem: multiple Sorcerer players have independently tested Electric Blast and Vox Omnium since May and reported that Electric Blast does not receive its advertised 50% bonus damage, while Electric Blast Sparks triggered through Vox Omnium apparently fail to receive the staff's Basic Skill damage multiplier. Those reports have survived Patch 3.1.1, Patch 3.1.2 and several months of Sorcerer changes. In a game where Blizzard is preparing another substantial global Sorcerer buff for Season 15, that creates a slightly awkward question: how useful is more damage if one of the builds cannot collect the damage it already has?

Electric Blast Is Supposed to Turn Spark Into One Big Hit

Spark normally deals its damage across several hits. Electric Blast changes that behaviour by combining the damage into a single explosion and, according to the skill description, increasing that damage by 50%. The attraction is easy to understand. Turning several small Spark hits into one larger blast can interact differently with effects built around individual hits, and it gives Sorcerer players another way to construct a Basic Skill build rather than simply returning to whichever established endgame setup happens to own this month's largest spreadsheet.

Player testing suggests the consolidation works. The 50% bonus does not. One July tester gave a deliberately simple example: if ordinary Spark produces four hits of roughly 500 damage each, Electric Blast should combine the 2,000 base damage and then apply its 50% increase, producing around 3,000. Instead, the tester reported an Electric Blast around 2,000 — the four attacks had become one, but the advertised bonus had apparently disappeared. An earlier May bug report described the same issue, and further testing in July again found Electric Blast performing approximately like ordinary Spark rather than the upgraded version described by the tooltip. (Blizzard forum report)

On its own, that would already make Electric Blast an unattractive upgrade. Losing a 50% multiplier is not the sort of thing an endgame build casually compensates for with a slightly nicer pair of boots. Unfortunately, Vox Omnium appears to add another missing number on top.

Vox Omnium Appears to Trigger Spark — Without Its Big Damage Bonus

Vox Omnium is designed to turn Core Skill casts into additional Basic Skill attacks. When the appropriate elemental interaction is present, the staff triggers a Basic Skill and applies a substantial damage increase to that triggered attack. This should make something like Electric Blast Spark particularly interesting: use the Core Skill to trigger Spark, allow Vox to massively amplify that Spark and then let Electric Blast consolidate the attack into one large hit. It sounds like exactly the sort of odd little build engine Diablo IV's Unique items are supposed to encourage.

The attack itself does trigger. The damage bonus apparently does not. The July 28 bug report says Sparks generated by Vox Omnium still appear normally but do not benefit from the Unique's bonus damage when Electric Blast is selected. The tester calculated that combining the missing Electric Blast multiplier with the missing Vox bonus leaves this specific interaction producing roughly one-eighth of the damage expected from the tooltips. They also noted the rather painful consequence for Mythic Vox Omnium: improving the Unique's multiplier does not meaningfully help Electric Blast if that multiplier is not being applied in the first place. (current bug thread)

That is a familiar type of Diablo IV problem. We recently covered Paladin's Hallowed Ground apparently displaying a perfectly functional upgrade while two of its actual benefits fail controlled testing, while Leoric's Crown and Soul Splinters produced an enormous defensive number on the Season 15 PTR that did not survive contact with the Training Dummy. Diablo IV's tooltips increasingly describe extremely complicated mechanical contracts. The difficulty begins when only one party honours them.

The New September Calculation Says a Full Build Can Lose Even More

The thread became active again on September 6 when another Sorcerer player argued that the original one-eighth estimate can actually understate the practical loss. Their reasoning is that a real build does not stop at Electric Blast and Vox Omnium. Diablo IV multiplies effects through numerous layers of gear, skills and conditional bonuses, so removing a multiplier early in that chain can also reduce the value of everything built around it. For the setup this player had calculated before discovering the bugs, the final result was approximately 1/20 of what they expected the finished build to produce.

Again, that does not establish “Electric Blast deals 5% damage” as a universal Diablo IV fact. Different gear, different Vox rolls and different supporting effects will produce different totals. The useful part of the comment is the broader point: missing build-defining multipliers can hurt considerably more than their individual tooltip percentages suggest once the entire build has been constructed around them. The same player says other Spark variants interact with Vox correctly and can make each individual Spark tick hit roughly five times harder than their Electric Blast version.

That difference is exactly why this is more interesting than a generally weak skill. If every Spark setup performed poorly, Blizzard could simply decide Spark needs a buff. Here, players are reporting that the alternative variants work with Vox while Electric Blast specifically does not. That points toward a mechanical interaction rather than ordinary balance. We saw something similar when Sorcerer's Ice Shards Enchantment could apparently stop triggering partway through a dungeon. The class had not suddenly become weaker because monsters gained hidden resistance to frozen architecture. One part of the machinery had simply stopped moving.

Players Have Been Reporting Electric Blast Problems Since May

The timeline makes the current report harder to dismiss. A dedicated Electric Blast thread appeared on May 9 reporting that the 50% increased damage did not apply. By July 7, controlled testing had linked the same problem to Vox Omnium and identified the missing Unique damage bonus. Another report on July 14 said both issues remained in Patch 3.1.1. On July 28, the tester reposted the problem for Patch 3.1.2 and calculated the one-eighth damage result. That same thread was still receiving new discussion on September 6. (earlier Patch 3.1.1 report)

Blizzard has not ignored Sorcerer bugs during this period. Quite the opposite. May's Patch 3.0.2 contained a substantial Sorcerer bug-fix list, including fixes for Meteor, Fireball, Chain Lightning, Ice Shards, Hydra and several other interactions. Blizzard specifically fixed Vox Omnium causing triggered Basic Skills to miss their intended targets and also fixed Crackling Energy failing to trigger when combined with Electric Blast. In other words, both Vox Omnium and Electric Blast have already been touched by official bug fixes this year. The current player reports concern different parts of those mechanics — the damage multipliers themselves. (official Diablo IV patch notes)

That distinction is important. It would be inaccurate to say Blizzard previously announced that this specific Vox/Electric Blast damage bug was fixed. The May patch addressed Vox targeting and Electric Blast's Crackling Energy interaction. The missing 50% and Vox damage bonuses are player-reported problems that continued afterward. Blizzard repaired two rooms in the house. The current complaint is that the electricity is still off in the kitchen.

This Is Exactly What Sorcerer Players Were Worried About Before Season 15

The timing is particularly interesting because Blizzard's Season 15 PTR gives Sorcerer a significant global boost. The class's Core Stat scalar is being raised from 1.25 to 1.625, increasing the damage Sorcerers gain from Intelligence. That is meaningful and should lift many builds automatically. But when we covered the Season 15 Sorcerer changes in August, one of the main community concerns was already that larger global numbers do not solve skills and interactions that simply fail mechanically.

Vox Omnium and Electric Blast are almost too perfect an example. Suppose Blizzard gives the Sorcerer another healthy percentage of general damage. Excellent. That percentage then enters a build where players say one advertised 50% bonus is absent and Vox Omnium's major multiplier is absent as well. The Sorcerer technically received the buff. The broken interaction politely eats around it.

We have seen that pattern elsewhere this season. Talisman set bonuses have reportedly vanished mid-combat until players refresh the affected state, while Cataclysm Druids have reported boss damage collapsing until an encounter transition effectively resets the build. These are far more damaging to build diversity than an ordinary 10% balance discrepancy because they discourage experimentation. A player can spend hours assembling an unconventional setup, discover it performs terribly and conclude the concept is bad without ever realizing the game is refusing to apply part of the concept.

Vox Omnium Should Be Exactly the Kind of Unique Players Build Around

That is the real shame here. Vox Omnium is an interesting Unique precisely because it invites experimentation. It does not merely say “Core Skills deal more damage.” It encourages the Sorcerer to connect Core and Basic Skills, find elemental relationships and exploit effects attached to the triggered attacks. That is much healthier item design than equipping a staff because 427 is larger than 381.

Players are still experimenting with Vox despite the reported problems. A recent community discussion around a four-Greater-Affix copy shows people continuing to search for Basic/Core combinations that can make the staff work, and another Sorcerer thread notes that some other Spark variants appear to interact correctly with Vox. That makes Electric Blast's failure particularly unfortunate. It is not simply making a mediocre Unique weaker. It is potentially removing one branch from an item whose entire purpose is giving players branches to explore.

Diablo IV's current gearing already contains enough barriers before a strange build becomes viable. Transfiguration can add another RNG wall after the correct endgame item finally drops, Greater Affixes have to land on useful stats, and Mythic versions add another layer of rarity. When somebody finally assembles the correct equipment, the reward should be discovering whether their theory was clever. Discovering that the tooltip's multiplication never entered the calculation is considerably less satisfying.

For Now, Electric Blast Players Should Test Before Investing Heavily

There is no official Blizzard confirmation of the current damage bug and no documented workaround in the active forum thread. Sorcerer players interested in Vox Omnium and Electric Blast should therefore test the interaction themselves before committing expensive crafting resources. The Training Dummy makes this relatively straightforward: compare ordinary Spark against Electric Blast under controlled conditions, then compare naturally cast Spark with the Spark triggered through Vox Omnium. Remove as many unrelated modifiers as possible, keep Critical Strikes and conditional buffs under control and record several hits rather than trusting one damage number.

If Electric Blast produces approximately the combined base Spark damage without the expected 50% increase, that reproduces the first player report. If Vox-triggered Electric Blasts then fail to scale with the Unique's listed Basic Skill bonus while another Spark variant does, that reproduces the second. More independent tests would be useful, particularly across different Vox Omnium qualities and current Patch 3.1.2 setups.

Because right now the strangest thing about this Sorcerer build is not that somebody calculated it at one-eighth of its expected damage in July or one-twentieth in September. Diablo mathematics can always produce increasingly alarming fractions if given enough time.

The stranger part is much simpler:

players have been reporting the same missing damage since May, and Electric Blast is still apparently waiting for the electricity.

Diablo 4’s Demonbinder Mount Armor Has Been Broken for Four Months

2026-09-08T01:22:38.705-07:00

Diablo IV contains a great many complicated systems. Damage multipliers interact with Paragon nodes, seasonal mechanics interact with equipment, and endgame builds can require enough arithmetic to make a tax return feel refreshingly tactile. Demonbinder Mount Armor has discovered a more elegant way to malfunction: the cosmetic drops, you pick it up, and the game simply refuses to let you own it. Players have been reporting the problem since the beginning of May, with some earlier owners saying Demonbinder actually disappeared from their collections in late April. Four months later, one of the largest active bug threads on Blizzard's Diablo IV forums was still receiving activity on September 7.

The main Demonbinder bug thread now contains more than 60 replies and close to 6,000 views. Players across PC and PlayStation describe essentially the same experience: Demonbinder drops, often from Grigoire or the Hall of the Penitent, but using the item does nothing. It remains in the inventory or stash instead of being consumed and added to the Stable's Mount Armor collection. Some players have found two copies. Others have collected three. One particularly patient player reported having five Demonbinders sitting in the stash. At that point it stops being a cosmetic reward and begins resembling an unusually specific storage problem.

Demonbinder Drops Normally — Then Refuses to Unlock

The basic failure is remarkably consistent. A player defeats Grigoire, sees Demonbinder appear among the rewards, picks up the Mount Armor and attempts to use it. The usual sound or interaction may occur, but the cosmetic is not consumed and nothing new appears in the Stable. Players have tried restarting Diablo IV, relogging, moving the cosmetic through the stash, switching between mouse and keyboard and controller, and simply waiting for the game to reconsider its position. None of those methods appears to provide a reliable fix.

The first large thread began on May 5 when a PC player said Demonbinder had dropped but could not be added to their collection. They checked whether it had perhaps already been unlocked under another name and found nothing. More importantly, Demonbinder itself did not appear among the Mount Armor entries available to collect. Other players immediately confirmed the same behaviour, including somebody who had obtained the cosmetic from the Hall of the Penitent. By May 23, the original poster had accumulated five copies without being able to learn a single one. ([us.forums.blizzard.com](https://us.forums.blizzard.com/en/d4/t/cannot-add-demonbinder-mount-armor-to-collection/250329))

It is difficult to imagine a cleaner demonstration of a broken reward loop. Kill boss. Receive cosmetic. Cosmetic does not unlock. Kill boss again. Receive same cosmetic. Cosmetic still does not unlock. Continue until stash begins looking like Demonbinder's regional distribution warehouse.

Some Players Say They Already Owned Demonbinder — Then It Vanished

The stranger part actually predates those unusable drops. On April 28, a separate player reported that Demonbinder had disappeared from their Mount Armor collection despite previously owning and regularly using it with the Brimstone horse. Other players quickly confirmed that they remembered having Demonbinder unlocked and could no longer find it. Within days, that same thread began attracting players who had newly obtained the cosmetic and discovered they could not learn it either. ([us.forums.blizzard.com](https://us.forums.blizzard.com/en/d4/t/demonbinder-mount-armor-no-longer-appearing-in-collections/246533))

That combination suggests something more interesting than a simple broken “Use” button. We cannot see Diablo IV's internal collection data, and Blizzard has not publicly explained the cause, so it would be premature to declare exactly what went wrong. But players reporting that an existing collection entry disappeared at approximately the same time new Demonbinder items became impossible to register raises the obvious possibility that the underlying cosmetic entry itself became disconnected or unavailable. The physical reward still exists in the loot table. The Stable appears to have forgotten what it is supposed to do with it.

This fits uncomfortably well with the broader cosmetic problems we have already been tracking. Earlier this year, Diablo IV's Wardrobe began producing another round of transmog and cosmetic complaints, including problems with mounts, trophies and appearances. We also covered players unable to claim the Herald of Hatred pet despite the reward appearing available. Those are not necessarily the same technical bug, but they live in the same rather untidy cupboard: Diablo IV occasionally seems less reliable at remembering cosmetic ownership than it is at remembering how many demons you killed three months ago.

The Bug Is Not Limited to PC

Although Blizzard's largest thread sits in the PC Bug Report section, console players have reported the same problem. A PlayStation-tagged thread from May 3 describes Demonbinder refusing to unlock on console as well as PC, with additional players confirming the issue. Another European forum report from June says a PS5 player received the cosmetic but could not use the item to add it to their account. That makes this considerably harder to dismiss as a local installation issue or one corrupted PC client. ([us.forums.blizzard.com](https://us.forums.blizzard.com/en/d4/t/demonbinder-mount-armor/249287))

Reports continued through July and August. Players were still obtaining Demonbinder from Lair Bosses at the end of July and discovering that it could not be learned. On August 7, one player noted that they had received another copy in Season 14 after already reporting the same problem in Season 13. On August 17, yet another player said a freshly dropped Demonbinder remained stuck in their stash because right-clicking it did nothing. The main Blizzard bug index now shows the original thread with activity as recently as September 7.

Cosmetic Bugs Matter More When Cosmetics Are Part of the Endgame

It is tempting to rank Demonbinder somewhere below a broken Unique, missing Paragon Points or a quest that prevents progression entirely. Nobody loses damage because their horse is insufficiently intimidating. But Diablo IV deliberately treats cosmetic collecting as one of its long-term reward systems. Bosses drop mount trophies and bardings, seasons offer appearances, the shop sells elaborate armor sets, events hand out cosmetics and players spend hundreds of hours gradually filling their collections. Once the game turns cosmetics into rewards, those rewards need to remain collectible.

We saw the opposite side of that equation recently when some Diablo IV players began finding surprise free cosmetics in their personalized shops. A free weapon appearance is fun because the act of receiving it creates permanent ownership. Demonbinder currently performs only the first half of that transaction. The game congratulates you on the drop and then apparently asks you to keep the receipt in your stash indefinitely.

It also creates an ugly incentive around repeat drops. Normally, seeing a cosmetic you already own is largely irrelevant. With Demonbinder, affected players may not technically own it according to the Collection, so another copy looks like another chance to finally unlock the appearance. Then it fails. Then another drops. Before long, the player is preserving multiple copies because nobody knows whether salvaging or discarding them could mean losing the cosmetic permanently if Blizzard eventually repairs the collection state.

There Is No Reliable Workaround Yet

The community has tried the obvious fixes. Restarting the game has not consistently worked. Relogging has not consistently worked. Controller versus mouse makes no difference in the reports we found. Moving Demonbinder into and out of the stash does not suddenly remind Diablo IV that it is Mount Armor. Obtaining another copy also appears useless for many affected accounts. Players who already owned Demonbinder before it disappeared seem to have even fewer options because there is nothing meaningful they can do to recreate the original unlock.

For now, the safest approach is probably to keep at least one unusable Demonbinder in the stash rather than throwing it away. That is not an official Blizzard recommendation, and we cannot guarantee a future fix would require the item to remain present. It is simply the cautious response when the game has successfully awarded a cosmetic but failed to register that award permanently. Inventory space is annoying. Farming the cosmetic again after a fix would be more annoying.

Diablo IV's inventory has already been asked to babysit enough broken rewards recently. Yesterday we looked at Charm Slots that can visibly exist while refusing to accept Charms, while Treasure Breach players have been forced to choose which loot to leave behind when town teleporting fails. Demonbinder contributes its own wonderfully modest variation: please reserve one stash slot for the horse armor you already earned but are not currently allowed to possess.

Four Months Is a Long Time to Keep a Horse Waiting

The scale of Demonbinder's forum history is what makes the problem worth revisiting now. This is not one player who misread a tooltip. The largest thread has accumulated dozens of confirmations, nearly 6,000 views and reports stretching through multiple seasons. Separate threads cover PlayStation, missing previously unlocked copies and new drops that cannot be consumed. The bug has survived from spring into September with no visible Blizzard response or documented fix that we could find.

That does not make Demonbinder the most serious bug in Diablo IV. A Secret Cow Level quest that can stop before delivering the Hadopelagic Key is considerably more damaging to progression. A broken defensive item can kill characters. Missing rewards can affect actual power. Demonbinder merely prevents your horse from wearing an especially nice piece of armor.

But four months is an impressively long time for something this simple to remain broken. The boss knows how to drop Demonbinder. The player knows how to pick it up. The inventory knows how to store it.

Only the Collection seems unaware that Demonbinder exists.

Diablo 4’s Secret Cow Level Quest Is Still Soft-Locking Players Months Later

2026-09-08T01:12:46.698-07:00

For decades, Diablo's Secret Cow Level survived on a wonderfully simple joke: there is no Cow Level. Diablo IV eventually decided this was far too straightforward. There is now most definitely a Cow Level, there is an impressively elaborate hidden quest leading to it, there are obscure relics, sins, braziers, suspicious birds and one particularly important key — and some players are still discovering that the final secret may simply be that the quest refuses to continue.

A fresh Diablo IV bug report from September 7 describes a Seasonal Solo Self-Found player becoming soft-locked while trying to obtain the Hadopelagic Key, an essential item needed to continue toward Neyrelle's Hand and eventually unlock the Secret Cow Level. According to the player, all three required relics have already been burned, but the key never dropped. They say they have tried numerous ways of resetting the progression state, including creating additional characters, without success. This would already be an unpleasant end to one of Diablo IV's longest and strangest secret hunts. The more interesting part is that players have been reporting almost exactly the same failure since May.

The Hadopelagic Key Comes Very Late in a Very Long Cow Quest

Anyone who has actually completed Diablo IV's modern Cow Level puzzle will understand why losing progress here hurts. The road toward Neyrelle's Hand involves following the Outcast's Journal, manipulating the Holy Cedar Tablet in Kyovashad, completing several separate sin-related puzzles and collecting three unusual relics. Father's Chains comes from the Pride path, Mother's Rose belongs to the Anger section, and the Hierophant's Skull is obtained during Fear after following a Large Crow through Skovos. Each relic is burned at a corresponding Signal Brazier. Once all three have been successfully offered, the Hadopelagic Key is supposed to drop. That key then opens the Locked Wooden Coffin associated with the Greed portion of the puzzle, eventually giving access to Neyrelle's Hand.

This is not a two-minute side quest where restarting means killing three Fallen and walking back to town. It is an intentionally obscure treasure hunt whose pleasure comes from gradually untangling Blizzard's ridiculous little bovine conspiracy. When it works, that absurdity is part of the charm. We already celebrated the wonderfully stupid Cow King's Crown when players finally reached Diablo IV's Secret Cow Level, because Diablo is at its best when its solemn gothic horror occasionally remembers that this series once asked heroes to fight an army of halberd-wielding cattle.

When the quest breaks two steps before the prize, however, the mystery loses some of its romance.

The September 7 Player Says All Three Relics Were Already Burned

The newest report is particularly useful because it rules out one of the most common explanations players discovered earlier in the year. The Seasonal SSF player says they have already burned all three items required for the key, yet no Hadopelagic Key appeared. Without it, they cannot access the coffin that leads toward Neyrelle's Hand, effectively stopping their normal Cow Level progression. They also say they tried dozens of variations intended to clear the stuck quest state, including attempts to reset progression and starting new characters. Those additional characters reportedly fail to drop Mother's Rose, leaving the player with no obvious clean route back through the chain.

That last detail matters because one early May report initially appeared to have found the solution. A player who failed to receive the key later discovered that they had burned different relics on different characters. After repeating the missing steps on a single character, the Hadopelagic Key appeared. That suggests at least some apparent soft-locks were really the result of hidden character-specific progression flags rather than a broken quest. Unfortunately, other reports quickly complicated that explanation. PS5 and PC players subsequently said they had performed the entire sequence on one character, burned the Hierophant's Skull correctly and still received no key.

Players Have Reported the Same Failure Since May

The oldest dedicated Hadopelagic Key thread we found began on May 4. The first player could obtain the Hierophant's Skull but had problems completing the brazier interaction. Over the following weeks, more players described a nastier version: the skull burned successfully, disappeared from inventory and produced no key. Returning to obtain another skull did not necessarily help because the brazier would then refuse to accept it. One PS5 player said they relogged, changed difficulty, restarted the process and eventually obtained another skull, only to remain stuck. Another PC player described the same sequence on June 21: first skull burned, no key, second skull obtained, brazier no longer usable.

By August 10, the original May thread was still receiving fresh reports. That matters because we have already covered another part of this same Cow Level progression mess. Our August look at the Secret Cow Level's Anger soft-lock focused on Mother's Rose, Amazon Training gear and hidden quest-state problems that could trap players earlier in the chain. The new September report appears to be further along. The player says the three offerings are finished. The game simply does not produce the item that should acknowledge that they are finished.

Diablo IV has therefore managed the impressive trick of potentially giving the same extremely long secret quest more than one place where progression can wander into the woods and decline to return.

One Strange Workaround Suggests the Quest Flags Can Get Confused

There is at least one particularly interesting player workaround, although nobody should treat it as a guaranteed fix. A May player described completing portions of the quest across a Sorcerer and Paladin, burning the skull and receiving no key. They then removed their Talismans, reacquired the Amazonian equipment needed for the Anger sequence, obtained another Mother's Rose and burned that relic again. At that point, the Hadopelagic Key finally dropped — even though the skull had been the previously completed step. The player suspected that the game had remembered part of their earlier progress but failed to register the overall sequence cleanly.

That is anecdotal rather than an official solution, and the same forum thread includes players for whom similar attempts did nothing. Still, it illustrates why these reports are so frustrating to diagnose. A hidden quest is already built around invisible rules. If the invisible rules themselves become inconsistent, players have no reliable way to tell whether they have misunderstood the puzzle or whether the puzzle has misunderstood them.

That distinction has become a recurring Diablo IV problem. We have seen players complete Rank IX requirements while different parts of the game disagreed about whether the objective was finished, and older Eternal characters have similarly been labelled as being in Lord of Hatred's endgame while remaining locked out of endgame systems. In each case, the player has done the visible thing. Somewhere beneath the visible thing, another checkbox appears to have gone on holiday.

This Is Worse Than Ordinary Bad RNG

It is important to distinguish the Hadopelagic Key reports from ordinary complaints about rare drops. Diablo is built on randomness. Sometimes the sword does not drop. Sometimes the boss gives you three pairs of trousers and a personal insult. That is the agreement we all signed years ago. The Hadopelagic Key is different because it is supposed to be a progression reward for completing specific puzzle steps. Guides documenting the completed quest consistently describe the key dropping after the third relic is burned; it is not presented as something players should farm repeatedly until probability eventually becomes sympathetic.

That makes the fresh SSF report particularly ugly. In multiplayer, some Cow Level progression can potentially be bypassed or assisted through other players who have already unlocked pieces of the puzzle. Solo Self-Found exists specifically to remove that safety net. If the character's own quest state becomes trapped, “find somebody whose game works” rather defeats the point of the mode.

Diablo IV Has Fixed Quest Blockers Before

There is nothing inherently mysterious about the solution. Blizzard has repeatedly patched progression blockers when it can isolate them. Earlier this year, Hotfix 2 fixed a progression blocker in A Taste of Power, while we later saw Blizzard repair Rathma becoming stuck during A Blade's Weight. We also covered another April quest problem where players reported the Crooked Staff, Rusted Bell and Jabbering Gemstone sequence refusing to progress. Quest bugs happen. What matters is whether the game can recognize the damaged state and provide players with a route back.

The Hadopelagic Key reports suggest that route remains unreliable. There is no obvious current Blizzard patch note documenting a comprehensive fix for this specific Cow Level progression state, and the latest September 7 player is still reporting the same basic failure that appeared in May: required offerings completed, key absent, progression stopped.

The Secret Cow Level Should Be Difficult to Find — Not Difficult to Make Function

There is something charming about Diablo IV making its Cow Level absurdly elaborate. Secret areas should feel secret. The community spent years following dead ends, counting cows, inspecting suspicious items and treating every strange Blizzard asset as evidence in an agricultural conspiracy. Lord of Hatred finally rewarding that obsession with a genuine questline was exactly the sort of long-form Easter egg Diablo deserves.

But there is a meaningful difference between obscurity and malfunction. Asking players to follow a crow, burn relics representing sins, fish a coffin out of a forgotten campaign location and eventually assemble objects in the Horadric Cube is wonderfully ridiculous. Asking them to repeat parts of that process because the key failed to appear is merely ridiculous.

The September 7 report does not prove that every Cow Level quest is broken, and some historical cases were clearly solved by completing all required steps on the same character. But multiple PC and PS5 players have reported genuine no-key situations even after apparently satisfying that requirement, with reports stretching from May into September. For players affected by it, Diablo's oldest joke has therefore evolved once again.

There is a Cow Level.

There is even a key.

The game just occasionally forgets to give it to you.

Diablo 4’s Charm Slot Bug Is Still Leaving Players Unable to Equip Charms

2026-09-07T01:17:21.294-07:00

Diablo IV's Talisman system is supposed to be pleasantly simple. Equip a Seal, unlock a collection of Charm slots, drop your favourite Charms into them and begin constructing another elaborate little machine of bonuses, set effects and damage multipliers. Blizzard's own explanation is almost suspiciously cheerful: Seals can unlock up to six slots, and players can simply move Charms in and out whenever they wish. Some players have discovered an additional step that was not mentioned in the brochure: occasionally the game may decide those beautifully visible Charm slots are purely decorative. A fresh PlayStation report from September 7 says a Warlock player can no longer equip any Charms after removing the ones they already had, continuing a problem that players have been documenting since the beginning of July — and one Blizzard specifically attempted to fix in August.

The new report is short but painfully familiar. The player says they had already tried various solutions, eventually removed the few Charms that were still equipped, and then discovered that none could be put back. At that point the character was left with no usable Charms at all. One isolated forum post would not normally justify sounding the Sanctuary alarm, but almost the exact same sequence appears repeatedly in older PC, Xbox and PlayStation reports: Charms work, a Seal is changed or Charms are removed, the slots remain visibly open, and clicking a Charm produces either nothing or a brief equip animation before the item quietly returns to the inventory as though embarrassed by the entire affair.

Charms Are Not a Small Side System Anymore

This matters because Lord of Hatred made the Talisman a genuine part of character building rather than another seasonal trinket destined for the museum when the calendar changes. Blizzard describes the system as a new buildcrafting layer where a central Seal unlocks Charm slots and the Charms themselves add affixes, powers and set bonuses. More powerful Seals can unlock additional slots, while matching Set Charms can activate two-, three- or larger-piece bonuses. In other words, the Talisman sits alongside gear, skills, Paragon and the other systems players now use to squeeze another increasingly unreasonable percentage of damage out of Sanctuary's wildlife.

That makes losing access to the slots considerably more serious than a tooltip displaying the wrong number. We have already seen how Transfiguration can turn an otherwise excellent piece of Diablo IV gear into another endgame RNG decision, but at least the item still works when equipped. With the Talisman reports, players can have the Seal, have the Charms, see the slots and still be unable to connect the three. It is the ARPG equivalent of owning a television, a remote control and electricity while somebody has quietly removed the concept of HDMI.

The Original Reports Appeared at the Beginning of July

The problem was already well documented by July 1. One PC player reported having a working Horadric Seal that correctly unlocked three Charm slots alongside another Seal that visually displayed five open slots but refused to accept a single Charm. Other players soon described the same behaviour with Rare and Legendary Seals. A particularly large July 4 thread focused on the Vigorous Horadric Seal of Swiftness: affected copies were missing the usual “Unlocks X Charm Slots” line, yet equipping them still made the UI display apparently available slots. Those slots were not actually functional, and Charms that had already been equipped could lose their bonuses.

The most dangerous part was removing Charms while troubleshooting. Several players discovered that once a Charm came out, it would not necessarily go back in. One seasonal player began with three functioning Charms despite having a four-slot Seal, upgraded to a Legendary Seal, removed everything to rebuild the setup and then found themselves unable to equip any Charms at all. The same player later reported reproducing a related failure on a second character after changing difficulty during the Lord of Hatred campaign. They eventually got the original three-slot Seal recognized again, but swapping to other Seals caused the system to stop acknowledging the equipped Charms properly.

That is the sort of bug that encourages a special form of Diablo superstition. Do not touch the Seal. Do not change difficulty. Do not remove the third Charm. Do not look directly at the Talisman during a full moon. Once players begin treating an equipment interface like an unexploded artillery shell, something has gone slightly wrong.

Blizzard Actually Patched Charm Slot Problems in August

Unlike some long-running Diablo bugs, this one has an important official milestone. In Patch 3.1.3 on August 12, Blizzard explicitly listed a fix for an issue where certain Talismans did not unlock Charm slots when equipped. The same patch also corrected the Seal of the Diamond Mind's Charm-slot count, fixed item-power displays for Seals and Charms and made several additional Talisman adjustments. So Blizzard clearly knew there were problems around the system and shipped changes intended to repair them.

The awkward part is what happened next. On August 12 itself, a PC player reported that a Legendary Seal still visually opened its fifth slot but would not accept a Charm, specifically noting that the issue had existed before the update and had not been resolved for them. On August 16, another Legendary Seal report appeared. By August 25, players in that thread were describing Rare and Legendary Seals that refused to accept Charms, deactivated existing set bonuses when equipped and remained unusable even after finding newer working Seals. One player eventually salvaged the broken copies after concluding that freshly dropped replacements could work while the older affected items remained defective.

That does not necessarily mean Blizzard's August fix failed completely. It may have corrected one cause of non-functional Charm slots while leaving another behind, or it may have prevented newly generated items from inheriting a particular defect without repairing every existing Seal. Diablo bugs have an unfortunate fondness for family trees. What we can say is that player reports of unusable Charm slots continued after the patch that explicitly addressed unusable Charm slots.

The September Report May Not Be Exactly the Same Bug

The September 7 Warlock report deserves one important caveat. The player does not identify which Seal they are using, whether its tooltip is missing the Charm-slot line or whether changing difficulty, campaign state or another action preceded the failure. We therefore cannot confidently say that this is precisely the same defective-Seal bug reported in July. It could be a separate Talisman state problem producing the same visible result. The sensible conclusion is narrower: a player is still reporting the inability to equip any Charms in September, after months of similar reports and after Blizzard's August Charm-slot fix.

There is evidence for more than one failure mode. Some July players could use Magic Seals perfectly while Rare and Legendary versions failed. Others found that newly acquired Seals worked while older ones remained broken. An August PlayStation thread described clicking Charms, hearing the equip sound and seeing the item briefly grey out without it ever entering the slot; an Xbox player confirmed the same behaviour. Another August PC report described finishing the campaign, removing the existing Charms to rearrange them and then being unable to equip anything except the central Seal.

The UI is especially misleading because a broken Seal may visually show its slots as open. A player naturally assumes an empty slot means “put item here.” Diablo IV occasionally interprets it as more of a conceptual suggestion.

A Broken Talisman Can Remove a Major Chunk of Build Power

The practical damage depends on the build. Individual Charms can provide useful affixes on their own, but the larger loss comes from set bonuses. Blizzard deliberately designed matching Charms to reward partial and complete collections, meaning a character can be balanced around effects that disappear when the Talisman stops recognizing what is equipped. One July PC player reported having all three different pieces of a Practiced Technique set inserted, yet the tracker remained at 0/3 and neither the two-piece nor three-piece effects activated. The same player also experienced the separate problem where the game frequently refused to socket those Charms at all.

That distinction matters in modern Diablo IV because builds increasingly behave like interconnected mechanisms rather than piles of independent stats. We saw precisely that with Arcadia's reported healing-to-Rally-to-Fortify failure on Paladin: when one link in the chain stops functioning, the entire build can feel mysteriously weaker. It is also why Warlock's extraordinary Season 15 PTR performance depends on much more than simply finding a weapon with a large number printed beneath it. Skills feed demons, demons feed other effects, items amplify those effects and the Talisman sits happily beside all of it adding yet another layer of multiplication. Unless, naturally, it decides today is a non-working day.

Do Not Remove Working Charms Just to Test the Bug

The recurring detail across several reports gives us one practical warning: if your Charms are currently equipped and functioning, do not remove them merely to investigate whether your Seal is affected. Multiple players have reported being able to remove Charms but not put them back. If a new Seal appears suspicious — particularly if its tooltip does not correctly state how many Charm slots it unlocks — keeping the current functioning setup intact while testing a different Seal cautiously may save considerable frustration. Some players have reported success by switching back to a working lower-rarity Seal, while others found new replacement Seals that behaved normally, but there is no universal workaround supported across all reports.

That caution is particularly sensible before difficult content. Diablo IV already offers enough ways to lose an evening without voluntarily dismantling a working build. Players have reported Longtooth consuming Mythic Tribute runs without producing the expected loot, Treasure Breach can leave players deciding which loot must remain on the dungeon floor, and Wendigo Brand is still attracting reports that its temporary Maximum Life stacks can drain Current Life when they expire. Sanctuary remains committed to ensuring that even inventory management contains a modest element of danger.

Blizzard’s Own Description Makes the Failure Hard to Miss

The irony is that Blizzard's official Talisman instructions could hardly be clearer. Apply a Seal. Unlock Charm slots. Drop Charms into the open slots. Change them whenever you wish. That is the design. There is no hidden progression requirement saying a visible slot may reject an otherwise valid Charm, and there is certainly no intended mechanic where removing a functioning Charm permanently converts the slot into architectural decoration.

Blizzard already tried to fix at least one version of this problem on August 12, which is encouraging because it means the underlying issue is recognized rather than merely living in forum archaeology. The less encouraging part is that players were still reporting broken Seals after that patch, and on September 7 a PlayStation Warlock player says they have now reached the worst version of the failure: no Charms can be equipped at all.

When an Empty Slot Isn’t Actually an Empty Slot

There is a peculiarly Diablo quality to this bug. The game has spent years becoming more sophisticated, adding increasingly intricate systems for crafting, itemization and character optimization. Even access to certain endgame activities now has its own rarity discussion, while the gearing process can involve Greater Affixes, Transfiguration, Seals, Charms, Mythics and enough overlapping bonuses to make an accountant quietly close the spreadsheet and go outside.

And after all of that complexity, the problem occasionally comes down to something wonderfully primitive:

There is an empty box on the screen, and the game will not let you put the thing in the box.

Blizzard said in August that certain Talismans failing to unlock Charm slots had been fixed. Reports continued later that month. Now another player is unable to equip Charms on September 7. We do not yet know whether the newest case shares the exact same cause, how many current characters are affected or whether a particular Seal remains responsible. But if you currently have a functioning Talisman setup, perhaps admire it from a respectful distance until we know more.

In Diablo IV, demons are supposed to resist your build.

The equipment screen really does not need to join them.

Diablo 4’s Arcadia Pants Still Aren’t Fortifying Properly Six Months Later

2026-09-07T01:08:00.035-07:00

There are few things more authentically Diablo than finding the Unique your build needs, equipping it, admiring the carefully assembled machinery of affixes and synergies — and discovering that one of the important bits apparently forgot to come to work. That is where some Diablo IV Paladin players once again find themselves with Arcadia, the Unique Pants built around Rally, healing and Fortify. A fresh PlayStation report from September 6 says Arcadia is still failing to provide the expected Fortify when healing, and the same player reports similar trouble with the Kel Rune. The unpleasant part is not merely that a Paladin defensive interaction may be broken. Players first reported Arcadia's healing behaviour back in March.

That gives this particular pair of trousers an unusually respectable bug history. The original PC report appeared on March 13, additional Paladins confirmed the behaviour, another detailed report surfaced in July, and now the complaint has returned in September. Diablo IV has changed considerably during that period. Fortify itself has been redesigned, Paladin balance has been adjusted, Blizzard has fixed numerous class interactions and Wendigo Brand has demonstrated that defensive items occasionally develop surprisingly offensive opinions about their owners. Arcadia, meanwhile, continues attracting reports that its central mechanic simply does not behave as advertised.

Arcadia Is Supposed to Turn Healing Into More Rally

Arcadia is a Paladin Unique whose entire identity revolves around a pleasing little defensive loop. Rally Fortifies the Paladin for a percentage of Maximum Life, while recovering a sufficient portion of Maximum Life is supposed to generate another Rally charge. Healing therefore feeds Rally, Rally feeds Fortify, and the Paladin gets to behave like a heavily armoured perpetual-motion machine powered by refusing to die. At its best roll, Arcadia's Rally can Fortify for 8% of Maximum Life, making the pants particularly attractive for builds that recover health frequently and want to convert that recovery into additional defensive resources.

The design is especially relevant because Blizzard has fundamentally changed what Fortify does. Under the current system, Fortify is no longer simply another Damage Reduction condition. Blizzard describes it as an additional reservoir of Life: Fortify can stack up to Maximum Life, and when the character is below full health, some of that reservoir is consumed to heal the player over time. You are considered Fortified whenever any Fortify remains. That makes reliable Fortify generation an active part of survivability rather than a decorative number tucked beneath the health globe. We recently saw a similar lesson with Diablo IV's Toughness number and why apparently enormous defenses can still mislead players against Lilith. Defensive systems are only useful when the game systems producing them actually fire.

The New September Report Says Arcadia and Kel Both Fail

The newest report comes from a PlayStation player on September 6. According to the post, Arcadia Pants and the Kel Rune are not providing Fortify from the expected healing interaction. The player specifically highlights Paladin builds using Judgement or Disciple skills, arguing that those setups already have relatively limited convenient Fortify options and therefore feel the failure particularly hard. It is currently a single fresh console report, so this should not be interpreted as evidence that every Arcadia or Kel setup is universally broken. But Arcadia itself comes with considerably more history than one forum post.

The earliest thread we found dates to March 13. A PC player reported that Arcadia was not properly registering healing and therefore was not initiating its Fortify/Rally interaction. Another player confirmed the problem several days later and said the failure made their Paladin noticeably squishier because Arcadia was central to the defensive setup. That thread remained active months later. Then on July 2, another PC player submitted a separate report saying only part of Arcadia's Unique power appeared to work: Rally itself could provide Fortify, but recovering health was not generating the Rally charge described by the item. In their words, that failure effectively broke the build.

This Is Exactly the Kind of Bug That Makes a Build Feel Wrong Before You Know Why

Arcadia is not a spectacular meteor, giant demon or enormous damage number. It is plumbing. Good buildcraft contains a surprising amount of plumbing. One mechanic creates healing, another watches the healing threshold, Arcadia grants Rally, Rally creates Fortify, Fortify becomes reserve health, and suddenly the character can stand somewhere it absolutely should not be standing while a demon the size of a farmhouse becomes increasingly annoyed. Remove one connection and nothing necessarily explodes. The build merely becomes worse in a way that can take an evening to diagnose.

That is what makes these bugs particularly frustrating. A player can reasonably assume the problem is their Paragon board, insufficient healing, a missing temper, poor Fortify Generation or simply harder content. Diablo IV now contains enough overlapping character systems that troubleshooting can resemble electrical work conducted during a thunderstorm. We have recently covered how Transfiguration adds another layer of RNG to otherwise excellent endgame items and how Horadric Gems can turn something as mundane as repairing equipment into a surprisingly expensive mistake. Arcadia belongs to the same family of problems: the tooltip tells you what the machine should do, while the actual machine may have other plans.

Arcadia Has Been Reported Broken Since March

The timeline is the strongest part of this story. March brought the initial PC complaint. July brought another player independently describing the healing-to-Rally portion of Arcadia as non-functional. September now brings a PlayStation report involving Arcadia again, this time alongside Kel. Blizzard's current patch notes contain plenty of Paladin fixes and balance changes — including adjustments to Holy Damage display, Oaths, Blessed Shield, Shield Charge, Heaven's Fury and Paladin sets — but we could not find a documented Arcadia fix addressing these healing reports in the current public notes. Blizzard has also recently standardized Arcadia's guaranteed affixes around Primary Core Stat and Maximum Life, showing that the item itself is certainly still being actively maintained as part of the modern loot pool.

That does not prove the underlying problem has remained completely unchanged for six uninterrupted months. Diablo bugs can disappear, reappear or depend on surprisingly specific combinations of skills, equipment and platforms. The March, July and September reports may also be triggering different parts of the same interaction. What we can say is simpler: players have repeatedly reported Arcadia failing around its advertised healing/Rally behaviour over a six-month period, and on September 6 somebody is still reporting it.

The Kel Report Could Point to Something Broader

The inclusion of Kel is what makes the newest complaint worth watching. If only Arcadia were involved, the obvious suspicion would remain the Unique's internal trigger. A player now claiming that Kel also fails to provide expected Fortify around healing raises the possibility that the problem could sit deeper in the interaction between healing and Fortify generation rather than in Arcadia alone. At present, however, there is not enough evidence to make that leap confidently. We have one fresh report linking the two, while Arcadia has a much longer paper trail.

That distinction matters. Diablo IV players have become understandably good at connecting dots, particularly after years of unusual item interactions, but two dots are not yet a constellation. For now, the safe conclusion is that Arcadia has multiple historical reports and Kel has been named alongside it in the latest PlayStation complaint. If more Paladins begin reproducing both failures across PC and console, then the story becomes considerably more interesting.

Paladin Really Doesn’t Need Its Defensive Gear Becoming Optional

The timing is also awkward for Paladin players because Blizzard has continued making targeted balance changes to the class. Recent patch notes increased several Paladin damage values and adjusted Oaths because Blizzard explicitly felt some Judicator builds were underperforming. That sort of numerical tuning matters, but a class can receive all the percentage buffs in Sanctuary and still feel terrible if a defensive interaction underneath the build does not trigger consistently. A 20% damage increase looks lovely in patch notes. It is slightly less impressive while your character is face-down beside Duriel because the trousers did not understand the assignment.

That becomes even more noticeable in a game where builds are increasingly defined by specific item engines rather than broad collections of good stats. The same principle is why Warlock's Season 15 power has attracted so much attention: the strongest builds are not merely piles of damage percentages; they are interconnected systems where demons, resources, skills and equipment continually feed one another. Paladin deserves the same reliability. If Arcadia is meant to turn healing into Rally and Rally into Fortify, every link in that chain needs to work.

For Now, Test Arcadia Before Building Around It

There is no documented universal workaround for the current reports. Paladin players using Arcadia should therefore verify the interaction themselves before assuming Fortify and Rally generation are functioning correctly. Find a safe area, take controlled damage, recover enough Life to cross Arcadia's stated threshold and watch Rally charges and Fortify directly. If the expected charge does not appear, swapping Arcadia out may be preferable to spending the next several hours wondering why the build suddenly feels made of attractive cardboard.

That advice is particularly important before pushing difficult endgame content or Hardcore. Diablo IV already has enough legitimate ways to kill a character. Longtooth can reportedly consume valuable Mythic Tribute runs without providing the expected reward, Treasure Breach can leave players surrounded by loot they cannot conveniently take back to town, and now a defensive Paladin Unique with reports stretching back to March is again being accused of forgetting part of its job.

Six Months Is a Long Career for a Pair of Broken Pants

Arcadia is exactly the kind of Unique Diablo IV should have more of. Its effect encourages players to connect healing, Rally and Fortify into a recognizable build identity rather than simply choosing whichever trousers contain the largest number. That makes it more interesting — and also makes any failure of the effect much more damaging. When a generic stat is slightly wrong, you lose efficiency. When the engine of a Unique stops working, you lose the reason for wearing the Unique at all.

Players were complaining about Arcadia's healing interaction in March. Another player reported the second half of its effect failing in July. A new PlayStation report on September 6 says Arcadia still does not Fortify correctly around healing and adds Kel to the complaint. We do not yet know whether both problems share the same underlying cause, nor whether every platform and build can reproduce them.

But after six months of Arcadia reports, Paladin players could reasonably ask for one fairly modest Unique effect:

When the pants say Rally, the pants should Rally.

Xbox Is Limiting Cloud Gaming to 15 Hours a Month — Diablo 4 Players Still Can’t Use It Anyway

2026-09-07T01:01:29.640-07:00

Microsoft has announced that Xbox Cloud Gaming is getting monthly playtime limits this November, with Game Pass Ultimate subscribers receiving 15 hours of cloud play, Premium getting 10 and Essential just five. Once those hours are gone, players will be able to buy additional cloud time through the Xbox Store. It is the sort of announcement that immediately makes anyone playing a large live-service RPG start doing uncomfortable arithmetic. Fifteen hours of Diablo IV is enough time to level a character, reorganise the stash three times, decide the build guide was wrong, return to the original build and discover it is somehow Sunday evening.

There is, however, a peculiar detail for Diablo players: Diablo IV still is not normally available through Xbox Cloud Gaming in the first place. Microsoft owns Blizzard. Diablo IV is included with Game Pass Premium and Ultimate. Xbox has spent years describing cloud gaming as a central part of its “play anywhere” strategy. Yet if you want to stream Diablo IV rather than install it, Microsoft's own cloud service remains conspicuously absent from the list of straightforward options. In other words, Xbox is introducing a 15-hour limit on a service Diablo IV players have spent more than two years waiting to properly use.

Xbox Cloud Gaming Gets a Clock in November

Microsoft announced the changes on September 3 in an official Xbox Wire update. Beginning in November, Game Pass Ultimate will include 15 hours of monthly cloud gaming, Premium will include 10 hours and Essential will include five. At present, eligible subscribers can stream without those monthly hour caps. Microsoft acknowledges that this is a meaningful change, although it expects only around 4% of Game Pass subscribers to be affected by actually reaching the limits. Players who do reach them will be able to purchase additional cloud playtime, with pricing and market-specific details promised before the system goes live.

For most people, Microsoft may be right. Someone occasionally streaming a smaller game onto a television or phone may never notice. Diablo IV is not really built like that, though. Seasonal Diablo is an enthusiastic consumer of evenings. We recently looked at how some players believe finishing the Premium Reliquary alone can add another 20–30 hours of progression after the main seasonal content. Meanwhile the endgame now contains Nightmare Dungeons, Helltides, Lair Bosses, Kurast Undercity, Infernal Hordes, War Plans and numerous other activities, even if an alarming number of those roads eventually lead back to The Pit. Fifteen hours is not a Diablo season. Fifteen hours is the period before a dedicated Diablo player begins describing the character as “coming together.”

There Is Just One Problem: Diablo IV Still Isn’t on xCloud

The funny part is that Diablo IV players do not currently need to worry about consuming those 15 Xbox Cloud Gaming hours with Diablo IV, because the game still does not appear as a normal Xbox Cloud Gaming title. This is not a new omission. When Diablo IV originally joined Xbox Game Pass in March 2024, we pointed out the same strange distinction: it was available through Game Pass on Xbox and PC, but not through xCloud. More than two years later, Microsoft's current Diablo IV store listing still advertises console and PC access rather than cloud play, and an April 2026 Blizzard forum discussion shows players were still asking why a game owned by Microsoft could not simply be streamed through Microsoft's own service.

The answer goes all the way back to Microsoft's acquisition of Activision Blizzard. To secure regulatory approval for the deal, Microsoft restructured the acquisition and transferred major cloud streaming rights for Activision Blizzard's existing games and games released over the following 15 years to Ubisoft. Outside the European Economic Area, Ubisoft received exclusive rights; within the EEA, the arrangement is non-exclusive because of Microsoft's separate European regulatory commitments. Microsoft explained at the time that the arrangement meant it would not simply control Activision Blizzard cloud distribution exclusively through Xbox Cloud Gaming. Regulators got competition. Lawyers got several extremely satisfying folders. Diablo players got GeForce NOW.

You Can Play Diablo IV in the Cloud — Just Not the Obvious Microsoft Way

None of this means Diablo IV cannot be streamed. NVIDIA added the game to GeForce NOW in 2024, later added Battle.net support and by late 2025 had introduced automatic Battle.net sign-in for supported Blizzard games including Diablo IV. NVIDIA's current paid cloud plans themselves use a monthly playtime model, but with 100 hours available to Performance and Ultimate members rather than Xbox's coming 15-hour Ultimate allowance. So the curious situation in 2026 is that someone who wants to stream Microsoft's Diablo game can use NVIDIA's cloud infrastructure quite happily, while the Xbox-branded cloud option remains the awkward one.

That matters more as Blizzard prepares for another major seasonal transition. BlizzCon's upcoming Diablo IV: What's Next presentation is expected to reveal content deliberately held back from the Season 15 PTR, while Season 15 is finally introducing Rebirth so existing characters can be recycled into a fresh seasonal start. Diablo IV is becoming easier to pick up again every few months. That makes being able to instantly stream it to a browser, television or handheld device an increasingly sensible fit for the game.

A 15-Hour Limit Would Be Very Noticeable in Diablo IV

If Diablo IV eventually does arrive properly on Xbox Cloud Gaming, the new limits would immediately become much more interesting. Fifteen hours on Ultimate works out to roughly half an hour per day over a 30-day month. Ten hours on Premium is twenty minutes per day. Five hours on Essential is ten minutes, which is approximately enough time to log in, inspect the inventory and remember why you logged out yesterday. Obviously nobody plays Diablo in perfectly measured daily portions, but the comparison illustrates how quickly a monthly cloud allowance can disappear inside a game designed around repeated seasonal progression.

It would also create a peculiar difference between installed and streamed play. Microsoft is not limiting how long Game Pass subscribers can play an installed copy of Diablo IV. The new restriction applies specifically to cloud gaming. An Ultimate subscriber could therefore spend hundreds of hours playing Diablo locally but potentially be asked to buy additional time after 15 hours if the exact same character were being streamed. Cross-progression makes the transition between devices technically elegant; billing makes it slightly more medieval.

Microsoft Says Only 4% of Subscribers Should Be Affected

The important caveat is Microsoft's own estimate that around 96% of Game Pass members will never hit these limits. Cloud gaming remains supplementary for most subscribers rather than their primary way of playing. If someone streams for an hour during lunch twice a month or occasionally uses a television while the main console is occupied, 15 hours may be entirely adequate. The people likely to notice are precisely those who have embraced Microsoft's original promise most enthusiastically: players using cloud streaming as a genuine replacement for local hardware rather than an occasional convenience.

That is why Diablo IV makes such an interesting example even though it is not yet part of Xbox Cloud Gaming. Diablo is almost perfectly designed to test whether monthly cloud allowances feel generous or restrictive. It is persistent, seasonal, cross-platform, grind-heavy and unusually good at convincing sensible adults that one more dungeon at 23:40 is an entirely defensible lifestyle choice.

Diablo IV Has Been Waiting Outside the Cloud Door Since 2024

Microsoft's November changes therefore create two separate questions for Diablo players. The first is whether 15 hours would ever be enough if Diablo IV finally joined Xbox Cloud Gaming. For anyone seriously participating in a season, probably not. The second is considerably stranger: when does Diablo IV actually get there?

The game joined Game Pass in March 2024. Microsoft owns Blizzard. Xbox Cloud Gaming now supports more than a thousand owned games through its broader streaming programme. Yet in September 2026, Diablo IV remains a title you can install through Xbox, install through the Xbox PC ecosystem and stream through competing cloud services, while Microsoft's own cloud platform still cannot offer the obvious version of the experience.

So Diablo IV players can relax about Xbox's new 15-hour monthly limit for the moment.

You cannot run out of Diablo IV xCloud hours if Microsoft still will not give you any.

Diablo 4 Fixed a Treasure Breach Exploit — Now Players Can’t Carry All the Loot Home

2026-09-07T00:52:06.303-07:00

Diablo IV has managed to create an unusual problem for an action RPG: too much loot and no legal way to take it home. Players are once again reporting that Treasure Breach Nightmare Dungeons can prevent them from teleporting to town, leaving inventories completely full while valuable equipment, Seals and Charms continue piling up on the floor.

The restriction appears to be connected to Blizzard's earlier efforts to stop Treasure Breach and Path of Coin instances from being repeatedly reset for effectively unlimited Goblin farming. That exploit absolutely needed fixing. The awkward part is that months later, affected players say the solution still prevents perfectly ordinary trips to the Blacksmith and stash — even after the Goblin area has been cleared and its boss defeated.

Treasure Breach gives you a dungeon full of loot.

Then apparently asks whether you brought enough pockets.

A September Player Had to Leave Valuable Loot Behind

The newest bug report describes a Treasure Breach run where a Goblin portal appeared while the player's inventory was already full.

The obvious solution was to teleport to town, clear the bags and return.

Diablo IV refused.

The player entered the Goblin Dungeon instead, collected more loot and tried again.

Still no teleport.

They then cleared the Goblin Dungeon completely, including the final boss and its swarm of Treasure Goblins.

Still no teleport.

The result was exactly what you would expect when an ARPG showers a player with items while simultaneously disabling the system designed to store them: valuable drops had to remain on the ground.

The player later returned to the main Nightmare Dungeon, completed that as well and found that town teleport was still unavailable. Their eventual workaround was to physically leave the dungeon, teleport from outside, empty the inventory as quickly as possible and rush back before the instance closed.

It worked.

In the same way climbing through a bathroom window works when your front door is broken.

This Started With a Very Real Infinite Goblin Exploit

The current restriction did not appear for no reason.

Back in April and May, players discovered that certain War Plan-generated Nightmare Dungeons with the Treasure Breach modifier could be repeatedly reset without losing the modifier. As long as the final dungeon boss remained alive, players could clear the Treasure Goblins, reset the dungeon and run the same Goblin-rich layout again.

A separate Path of Coin interaction was even more exploitable. Players discovered that teleporting to town from the Goblin realm and returning could create another fresh instance. With the correct sequence of portals and dungeon transitions, the reward area could effectively be repeated over and over.

Players themselves reported these behaviours as exploits. One May bug report explicitly described the Treasure Breach as being repeatable “as many times as you like” provided the final War Plan boss remained alive.

That is obviously not what Blizzard intended.

Treasure Goblins are generous.

Infinite Treasure Goblins are monetary policy.

Blizzard Patched the Repeatable Portal in June

Blizzard addressed several related issues in Patch 3.0.4 on June 10.

The patch specifically fixed an issue where the Greed is Good portal could be activated multiple times in the same Nightmare Dungeon instance. Blizzard also corrected a Path of Coin problem where teleporting out and returning could leave the player unable to escape.

Those are real fixes to real bugs.

What Blizzard's notes do not explicitly say is that town teleport should simply remain disabled throughout Treasure Breach and Path of Coin content.

Yet on June 12 — almost immediately after the patch — players began reporting exactly that behaviour.

One player described being unable to teleport out to salvage the huge volume of gear, Seals and Charms dropping inside the dungeon. Another confirmed the same issue. A third pointed out an especially unfortunate interaction: an older bug could make the Curious Coin portal itself unusable, while the new teleport restriction simultaneously removed the usual workaround of going to town and returning.

Blizzard closed one escape route.

Sometimes the actual exit was broken too.

The Same Complaint Continued Through July and August

If this were simply temporary fallout from the June patch, it would not be particularly interesting in September.

But the reports continued.

On July 7, another player finally obtained a Treasure Breach Sigil, triggered the Goblin portal and discovered midway through the loot explosion that their inventory was full. They could not teleport out of the Goblin area, and leaving it caused the portal to close. They also reported being unable to town-portal from the parent Nightmare Dungeon while the Treasure Breach modifier was active.

The player summarized the problem rather neatly: the game was “raining down” loot while preventing them from collecting a large portion of it.

Another player confirmed the behaviour the following day.

Then on August 8, someone returned to the same thread to say the restriction was still present and argued that Blizzard needed to fix the underlying reset problem rather than maintaining what players increasingly saw as a “bandaid fix.”

Now it is September.

The bandaid has apparently developed tenure.

Treasure Breach Is the Worst Possible Place to Disable Town Trips

The restriction would be less absurd inside an ordinary dungeon.

Treasure Breach is specifically designed around an unusual concentration of Treasure Goblins. Blizzard's own Season 13 documentation describes the modifier very simply: a number of Treasure Goblins invade the dungeon.

Treasure Goblins drop things.

Rather a lot of things.

And if the additional Path of Coin/Goblin Retreat area appears, the amount of loot increases again.

That means the activity most likely to fill your inventory is also one of the activities where players report losing the ability to empty it.

It is difficult to invent a cleaner conflict between two game systems.

The Problem Is Worse Because Diablo 4 Has More Things to Pick Up Now

Lord of Hatred did not exactly simplify Diablo IV's inventory ecosystem.

Players now juggle ordinary equipment alongside Seals, Charms, Nightmare Sigils and various other progression items. Blizzard has made improvements to storage and loot filtering, but a dense Treasure Breach can still fill a character remarkably quickly.

That is especially true if the player is actually inspecting Greater Affixes rather than immediately treating every non-Mythic item as decorative gravel.

We have already seen how War Plans can produce strange friction elsewhere. Season 14 players have reported War Plans failing to recognize completed activities, while others remain stuck at Rank 9/10 despite finishing every objective.

Treasure Breach is a slightly different problem.

The activity works.

The rewards work.

The problem is physically getting the rewards into storage.

A Temporary Stash Would Solve Most of the Frustration

Players have suggested several ways Blizzard could preserve the anti-exploit restrictions without forcing everyone to abandon loot.

The simplest would be a temporary stash or salvage NPC inside Treasure Breach and Path of Coin areas. If players cannot return to town because leaving and re-entering risks recreating the old instance-reset exploit, bring basic inventory management into the instance instead.

Another option would be allowing town teleport only after the relevant Goblin encounter has been completed. Once every reward has spawned and the instance can no longer regenerate its Goblins, there is considerably less reason to prevent players from leaving and returning.

Blizzard could also make abandoned Legendary, Unique and other high-value items reliably flow into the player's missed-item stash, although that is less elegant when dozens of potentially useful drops are involved.

The proper solution, of course, is making re-entry preserve the completed instance without resetting the rewards.

That is slightly more complicated than putting a chest beside the boss.

It is also why game developers get the larger desk.

Stopping an Exploit Shouldn’t Turn Normal Players Into Casualties

There is no argument that the old infinite Treasure Breach behaviour should have remained in the game.

Players could repeatedly generate Goblins and rewards from content intended to be consumed once. Blizzard was right to close it.

The issue is what happens after an exploit has been closed.

If the protective measure also prevents ordinary players from using a town portal for months afterward, the exploit has effectively left behind a tax on everyone who never exploited it in the first place.

That is especially noticeable because Treasure Breach Sigils and suitable War Plan setups are not something every player sees constantly. Finding one should produce the pleasant Diablo reaction:

“Excellent, Goblins.”

Not:

“Excellent, I hope I emptied my inventory first.”

Five Months After the Exploit, Players Still Want Their Town Portal Back

The timeline is becoming difficult to dismiss as a temporary workaround.

Infinite Treasure Breach and Path of Coin loops were reported in April and May.

Blizzard patched repeat portal activation in June.

Players immediately reported that they could no longer teleport out to manage inventory.

The same complaint appeared again in July.

Again in August.

And now again in September.

The anti-exploit logic may be doing exactly what Blizzard wanted: players are certainly not resetting the Goblin dungeon by teleporting to town anymore.

They are too busy deciding which pieces of loot they can afford to leave on the floor.

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

2026-09-07T00:43:16.051-07:00

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

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

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

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

Wendigo Brand Is Supposed to Reward Constant Killing

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

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

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

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

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

The ring gives you more health.

Then eventually asks for some of it back with interest.

A Fresh PS5 Report Shows the Same Problem on September 7

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

They kill monsters.

The stacks increase.

Maximum Life rises.

No problem.

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

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

Players Reproduced It Without Enemies Attacking Them

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

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

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

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

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

The Warlock Makes the Bug Much Easier to Trigger

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

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

Normally, that is fantastic synergy.

Warlock gets the damage.

Warlock gets the Maximum Life.

Warlock keeps feeding the ring with disposable demons.

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

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

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

A Hardcore Player Says the Ring Nearly Killed Their Character

The bug becomes considerably less amusing in Hardcore.

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

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

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

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

Few players begin troubleshooting with:

“Perhaps my Maximum Life ring has turned hostile.”

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

Blizzard Said It Was Investigating in July

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

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

Additional confirmations arrived through May and June.

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

That was nearly seven weeks ago.

Then the Season 15 PTR opened.

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

Now it has surfaced again on PlayStation.

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

The Ring’s Description Makes the Bug Particularly Misleading

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

Some Diablo items are deliberately dangerous.

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

Wendigo Brand is different.

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

There is no health-drain clause.

No “lose Current Life when stacks expire.”

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

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

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

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

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

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

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

The Safest Fix Right Now Is Unfortunately Removing the Item

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

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

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

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

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

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

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

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

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

Wendigo Brand was reported in April.

Players repeatedly reproduced it.

A Hardcore character nearly died from it.

Blizzard said in July that the team was investigating.

The Season 15 PTR reproduced it again.

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

That is an impressive survival record.

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