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

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.

Read More

Diablo 4 Players Are Reporting Entire Stashes Suddenly Disappearing

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.

Read More

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

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.

Read More

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

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.

Read More

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

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.

Read More

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

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.

Read More

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

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.

Read More

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

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.

Read More