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

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.”

Read More

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

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.

Read More

Diablo 4 Player Says Repeated Disconnects Have Eaten 13 Valuable Sigils

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.

Read More

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

 

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.”

Read More

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

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.

Read More

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

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.

Read More

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

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.

Read More