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

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

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

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

Treasure Breach gives you a dungeon full of loot.

Then apparently asks whether you brought enough pockets.

A September Player Had to Leave Valuable Loot Behind

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

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

Diablo IV refused.

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

Still no teleport.

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

Still no teleport.

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

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

It worked.

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

This Started With a Very Real Infinite Goblin Exploit

The current restriction did not appear for no reason.

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

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

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

That is obviously not what Blizzard intended.

Treasure Goblins are generous.

Infinite Treasure Goblins are monetary policy.

Blizzard Patched the Repeatable Portal in June

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

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

Those are real fixes to real bugs.

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

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

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

Blizzard closed one escape route.

Sometimes the actual exit was broken too.

The Same Complaint Continued Through July and August

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

But the reports continued.

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

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

Another player confirmed the behaviour the following day.

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

Now it is September.

The bandaid has apparently developed tenure.

Treasure Breach Is the Worst Possible Place to Disable Town Trips

The restriction would be less absurd inside an ordinary dungeon.

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

Treasure Goblins drop things.

Rather a lot of things.

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

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

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

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

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

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

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

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

Treasure Breach is a slightly different problem.

The activity works.

The rewards work.

The problem is physically getting the rewards into storage.

A Temporary Stash Would Solve Most of the Frustration

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

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

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

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

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

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

It is also why game developers get the larger desk.

Stopping an Exploit Shouldn’t Turn Normal Players Into Casualties

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

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

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

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

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

“Excellent, Goblins.”

Not:

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

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

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

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

Blizzard patched repeat portal activation in June.

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

The same complaint appeared again in July.

Again in August.

And now again in September.

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

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

Read More

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

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

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

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

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

Wendigo Brand Is Supposed to Reward Constant Killing

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

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

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

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

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

The ring gives you more health.

Then eventually asks for some of it back with interest.

A Fresh PS5 Report Shows the Same Problem on September 7

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

They kill monsters.

The stacks increase.

Maximum Life rises.

No problem.

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

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

Players Reproduced It Without Enemies Attacking Them

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

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

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

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

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

The Warlock Makes the Bug Much Easier to Trigger

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

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

Normally, that is fantastic synergy.

Warlock gets the damage.

Warlock gets the Maximum Life.

Warlock keeps feeding the ring with disposable demons.

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

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

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

A Hardcore Player Says the Ring Nearly Killed Their Character

The bug becomes considerably less amusing in Hardcore.

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

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

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

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

Few players begin troubleshooting with:

“Perhaps my Maximum Life ring has turned hostile.”

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

Blizzard Said It Was Investigating in July

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

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

Additional confirmations arrived through May and June.

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

That was nearly seven weeks ago.

Then the Season 15 PTR opened.

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

Now it has surfaced again on PlayStation.

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

The Ring’s Description Makes the Bug Particularly Misleading

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

Some Diablo items are deliberately dangerous.

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

Wendigo Brand is different.

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

There is no health-drain clause.

No “lose Current Life when stacks expire.”

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

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

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

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

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

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

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

The Safest Fix Right Now Is Unfortunately Removing the Item

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

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

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

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

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

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

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

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

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

Wendigo Brand was reported in April.

Players repeatedly reproduced it.

A Hardcore character nearly died from it.

Blizzard said in July that the team was investigating.

The Season 15 PTR reproduced it again.

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

That is an impressive survival record.

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

Read More

Diablo Immortal Players Report iPhone 17 Overheating After the Engine Update

Diablo Immortal's new engine is supposed to make Sanctuary prettier. On some iPhone 17 devices, players say it may also be making the phone considerably warmer.

A growing iOS bug report now contains two separate iPhone 17 owners describing unusually high temperatures after Diablo Immortal's recent engine update. The original player says their phone becomes noticeably hot within three minutes of launching the game and reaches roughly 40°C externally after around 30 minutes, even while running Diablo Immortal on Low Quality. A second iPhone 17 owner joined the thread on September 5 saying they had experienced exactly the same problem after updating, together with extremely heavy battery drain.

That does not establish that Diablo Immortal's new engine is definitely responsible. Two reports are still a very small sample, and Blizzard has not confirmed a thermal-performance issue affecting iPhone 17 devices. But the matching hardware, timing and symptoms make this more interesting than one potentially faulty phone.

The First iPhone 17 Starts Heating Up in Under Three Minutes

The original bug report was posted on August 26 by a player using a standard iPhone 17 rather than the Pro or Pro Max model.

According to the player, the phone previously became only slightly warm during Diablo Immortal sessions. After installing the recent engine update, however, it began getting noticeably hot in less than three minutes.

The player says they tested the game using Low Quality settings and still measured an exterior phone temperature of roughly 40°C after about half an hour. Closing Diablo Immortal caused the device to begin cooling almost immediately.

They also updated the phone to iOS 26.6.1 without seeing any improvement and specifically asked Blizzard to investigate CPU/GPU load and thermal performance after the engine update.

One hot phone could be hardware.

Then another one appeared.

A Second iPhone 17 Owner Reports the Same Problem

On September 5, another player replied that they had exactly the same overheating issue on another iPhone 17 and that it had also started after the update.

The second report adds another concern: battery life.

The player says Diablo Immortal drained the phone's battery completely in approximately three hours. They report battery health at 89% and argue that the drain is far heavier than they would expect from the device.

Battery runtime depends on brightness, graphics settings, network conditions, background activity, battery health and numerous other variables, so three hours should not be treated as a controlled benchmark.

Still, overheating combined with unusually rapid battery drain is exactly the sort of pattern you would expect if CPU or GPU load has increased substantially.

Whether that increase is actually coming from the new engine remains the unanswered part.

The New Diablo Immortal Engine Is a Major Visual Upgrade

Blizzard has described September's engine update as a substantial technical overhaul rather than a minor graphics patch.

The update reworks visual effects for nearly 100 Legendary Affixes, improves lighting and shadows across more than ten environments, reduces excessive lighting effects and changes ground and water materials. Blizzard allowed players to begin downloading the engine update ahead of the full September launch and even offered 10 Legendary Crests for completing the preparation early.

That is a lot of rendering work being touched at once.

It does not automatically mean the game should suddenly overheat modern hardware. Blizzard's own community team said in August that engineers did not expect currently supported devices to become incompatible because of the engine change.

But compatibility and efficiency are not quite the same thing.

A phone can technically run a game while using more power, generating more heat and draining its battery faster than it did before.

The Engine Rollout Has Already Produced Other Technical Reports

The iPhone complaints also arrive during a period where players are still working through several post-update technical changes.

An Android player using a Galaxy S25+ recently reported that the phone's Back button stopped behaving correctly after the engine update. Instead of closing menus such as the map or inventory, it reportedly minimizes Diablo Immortal and returns the user to the Android home screen. Interestingly, that player says a second phone that had not received the engine update still behaved normally.

We also recently covered players reporting large crafting-resource stacks disappearing around recent Diablo Immortal updates. In that case, as here, there is no confirmation that the engine update itself caused the problem.

These reports should not be combined into one giant “the new engine broke everything” theory. A missing resource stack, Android navigation behaviour and iPhone thermal performance can have completely unrelated causes.

What they do show is that a major technical migration creates a lot of surfaces where strange behaviour can appear.

40°C on the Outside Does Not Tell Us the Internal Chip Temperature

There is another important distinction in the original report.

The player's roughly 40°C measurement refers to the external temperature of the phone. It does not tell us the actual internal temperature of the processor or battery, and it does not by itself demonstrate dangerous overheating.

Modern phones routinely become warm during sustained 3D gaming, particularly when the GPU is being heavily utilized. Devices also have thermal-management systems designed to reduce performance before internal temperatures become unsafe.

The unusual part of this report is therefore not simply “phone gets warm while playing videogame.”

It is the player's claim that the behaviour changed dramatically immediately after the engine update, persists at Low Quality, begins within minutes and is now being independently reported by another owner of the same phone model.

That is what makes it worth investigating.

Lower Graphics Settings May Not Be Enough

The first player's attempt to solve the issue by switching to Low Quality apparently did not prevent the heat buildup. If that report is representative, simply lowering visible graphical quality may not reduce whatever workload is producing the problem.

Players experiencing similar behaviour can still try the usual steps: cap frame rate, reduce resolution and graphical settings, close background applications, avoid charging while playing and make sure both iOS and Diablo Immortal are fully updated.

But if the phone becomes unusually hot within minutes compared with its behaviour before the engine update, repeatedly pushing the device through long sessions purely to see whether it improves is probably not the most useful form of troubleshooting.

A reproducible bug report containing the exact device, iOS version, graphics settings, frame-rate setting and approximate time until the device becomes hot is considerably more useful to Blizzard.

We Need More iPhone 17 Reports Before Calling This an Engine Bug

At the moment, the evidence is suggestive rather than conclusive.

One iPhone 17 owner reports rapid heating, approximately 40°C exterior temperature after 30 minutes and immediate cooling when Diablo Immortal closes.

A second iPhone 17 owner says the same overheating started after the update and reports severe battery drain.

Blizzard has officially rolled out a major engine overhaul involving lighting, materials and visual effects.

Those facts make a connection plausible.

They do not prove it.

If more iPhone 17 users begin reproducing the same behaviour — particularly with comparable settings and before/after measurements — this will become much easier to classify as an optimization problem rather than two unhappy phones.

For now, the new engine is certainly making Diablo Immortal look different.

A couple of iPhone 17 owners would simply prefer it to stop making their phones feel different too.

```

Read More

Diablo 4’s Transfiguration Fixes the Gear Plateau — Then Creates a New One

Diablo IV's Transfiguration system solves one of the oldest problems in an ARPG surprisingly well: eventually, almost everything that drops becomes rubbish.

Once your character is wearing strong Greater Affix gear, another ordinary one- or two-GA item usually has all the emotional impact of finding a receipt in your pocket. Transfiguration changes that. Suddenly those imperfect items can become experiments. Fix the affixes, put the item through the system and see whether an unexpected result turns something merely good into something genuinely exciting.

That is a much healthier loot loop.

Unfortunately, players are beginning to argue that Transfiguration eventually creates a second gear plateau of its own. Once your equipment becomes strong enough, finding the correct upgrade is no longer sufficient.

The upgrade also needs to survive — and ideally win — another layer of RNG.

Transfiguration Makes 1–2 GA Items Interesting Again

A new community discussion makes a very good case for why the system works so well during most of character progression.

Before Transfiguration enters the equation, a reasonably developed character quickly reaches the point where one- and two-GA items barely deserve inspection. Maybe the Greater Affix landed on the wrong stat. Maybe the remaining affixes are mediocre. Maybe your existing item is simply good enough that replacing it would require an improbably perfect drop.

Transfiguration gives those items another purpose.

You can take a piece that is close but not quite right, clean up the fixable parts of it and then gamble on Transfiguration producing an outcome strong enough to move the build forward.

And because the starting item was not priceless, losing the gamble does not hurt very much.

That is excellent risk-versus-reward design.

A mediocre item becomes interesting because it has potential rather than because Blizzard simply increased how often perfect equipment falls from the sky.

The Problem Begins When Your Next Upgrade Is Already Extremely Rare

Eventually, however, the relationship changes.

Imagine your current item is already excellent. Finding a replacement may require the correct item type, several useful Greater Affixes and the exact combination of stats your build needs.

That item is already rare.

Now Transfiguration asks another question:

Did the rare upgrade also get the right Transfigure outcome?

If the answer is no, an item that looked like a meaningful upgrade can suddenly become worse than the equipment you were already wearing.

This is the point raised in the current player discussion. Transfiguration feels great when it is an optional attempt to turn common high-end drops into something better. It feels considerably worse when your only realistic upgrades require succeeding at Transfiguration after already winning the loot lottery.

The system stops extending the gear chase.

It becomes the gear chase.

A Great 2 GA Item Can Compete With a Much Rarer Drop

Part of the problem may actually sit underneath Transfiguration rather than inside it.

The argument being made by players is that Diablo IV's current gear curve can feel surprisingly flat at the top. A well-rolled two-GA item may already provide most of the practical value of a considerably rarer three- or four-GA drop.

Transfiguration can then bridge much of the remaining difference.

That is wonderful for accessibility. You do not need astronomically rare equipment in every slot to build an extremely strong character.

It also changes how exciting the rarest natural drops feel.

If the magnificent four-GA item still needs the correct Transfiguration result to beat the aggressively manipulated two-GA item you already own, its rarity begins to feel disconnected from its value.

Finding something extraordinarily rare should probably create at least a brief period where you are happy.

Diablo has enough opportunities for disappointment afterward.

Transfiguration Is Supposed to Be a Choice

This is where risk-versus-reward systems become tricky.

For Transfiguration to be interesting, there needs to be a reason not to use it.

If every good item should automatically be Transfigured because the possible gain massively outweighs the danger, then the decision is not really a decision. It becomes another mandatory crafting stage between finding an item and considering it finished.

The current forum argument describes exactly that pressure. An extremely rare item should theoretically create a moment where the player asks:

Do I keep this fantastic drop as it is?

Or do I risk it for something even better?

That is a proper Diablo decision.

But if the possible Transfiguration bonus is strong enough that not taking the gamble feels objectively wrong, the answer has effectively been chosen for you.

You put the item into the machine.

You hope.

And occasionally you learn a valuable lesson about attachment.

This Is Similar to Diablo 4’s Wider RNG Problem

We touched on the same underlying issue in our recent look at why Season 15's good ideas are still colliding with familiar Diablo IV problems.

Randomness belongs in Diablo. Without uncertain drops, an ARPG becomes a shopping list with skeletons in the aisles.

The problem comes when too many independent RNG checks sit on top of one another.

First the correct item needs to drop.

Then the right Greater Affixes need to appear.

Then the editable parts of the item need to cooperate.

Then Transfiguration needs to land correctly.

Any one of those systems can make loot interesting.

Stack enough of them together and a genuine upgrade can become statistically impressive long before it becomes enjoyable to pursue.

The Rarest Drops Need to Feel Stronger

One possible solution is not to make Transfiguration safer.

It is to make naturally exceptional gear more exceptional.

If the difference between a strong two-GA item and an incredible four-GA item were larger, players would have a genuine reason to protect the rarer drop. A four-GA item could already be so valuable that risking it through Transfiguration becomes an optional act of greed rather than the obvious final crafting step.

That would also help address a complaint we have seen repeatedly around Diablo IV's loot systems: players want truly rare items to feel genuinely exciting again.

Rarity alone is not enough.

The rare thing has to be meaningfully better than the almost-rare thing.

But Making Rare Gear Stronger Creates Another Problem

Of course, Diablo IV cannot simply make four-GA equipment dramatically stronger without consequences.

If the performance gap becomes enormous, players begin feeling that their characters are incomplete until every slot contains a near-impossible drop.

That conflicts directly with the faster, more accessible progression philosophy Blizzard has been moving toward.

We recently asked whether Diablo IV is slowly moving back toward Diablo III's seasonal power model. A large part of that model depends on allowing ordinary seasonal players to assemble functional, extremely powerful builds without spending three months waiting for one specific helmet.

Blizzard therefore has two competing goals:

Make rare loot exciting enough to chase.

But do not make rare loot so mandatory that everyone else feels unfinished.

Transfiguration currently sits directly between those goals.

The System Works Best When You Can Afford to Lose

Ironically, Transfiguration may already be an excellent system for most of Diablo IV.

Its strongest moment is when you find an item that would previously have been vendor food and think:

Maybe.

That one word keeps loot interesting long after your build becomes established.

Throwing expendable one- and two-GA items into a high-risk crafting system gives otherwise forgettable drops another life. Sometimes they brick. Sometimes they become spectacular. Either outcome is acceptable because the original item was not precious.

The system becomes frustrating only when the item underneath it is already so rare that losing the gamble feels like losing several evenings of progress.

Diablo 4 Has Moved the Plateau Rather Than Eliminated It

That may ultimately be Transfiguration's biggest achievement and its biggest weakness.

It successfully pushes Diablo IV's gear plateau much further into the endgame.

More drops remain relevant.

More items deserve inspection.

More imperfect gear has the possibility of becoming useful.

All of that is good.

But once a character finally reaches the new plateau, upgrades can become dependent on winning two lotteries instead of one:

find the exceptional item, then hit the exceptional Transfiguration.

Blizzard probably does not need to remove that risk.

Risk is why the system is interesting.

The better question is whether Diablo IV's rarest natural drops are strong enough that players sometimes feel comfortable saying:

No. This item is already good enough. I'm keeping it.

Because if every piece of perfect gear still needs one final visit to the gambling table, Transfiguration has not eliminated the gear plateau.

It has simply built a casino on top of it.

```

Read More

Diablo 4 Players Say Longtooth Can Eat a Mythic Tribute Without Dropping Loot

Diablo IV's Kurast Undercity is built around a fairly straightforward transaction. You spend a valuable Tribute, make the run more difficult, kill the boss and receive better or more targeted rewards. It is one of those arrangements where the player is generally expected to provide the danger and the game is expected to provide the loot.

Longtooth may currently be forgetting his half of the deal.

Two fresh bug reports from September 5 describe players using Mythic Tributes in the Undercity only for the final Longtooth encounter to fail in ways that leave the Tribute consumed and the player with no reward. In one case, Longtooth reportedly froze after being killed and continued his spinning animation indefinitely. In another, a player says they killed him twice using Mythic Tributes and received no drops at all.

These are player reports, not confirmation from Blizzard that every Longtooth run is affected. But Mythic Tributes are valuable enough that even an occasional failure is considerably more painful than the average boss deciding to behave strangely.

Longtooth Apparently Died Without Actually Dying

The clearest new report comes from a player who used a Mythic Tribute for an Undercity run on September 5.

According to the bug report, Longtooth reached the end of the fight but then became stuck instead of completing his death sequence. His whirling animation continued, the encounter never properly resolved and no loot appeared.

The player attempted to teleport out of the Undercity and return.

Longtooth was still there.

Still spinning.

Still refusing to acknowledge the minor administrative detail that his health bar had reached zero.

The Mythic Tribute, meanwhile, had already been spent.

The player understandably asked either for the Tribute back or for the Mythic reward they believed the run should have produced.

A Second Report Says Two Mythic Tribute Runs Dropped Nothing

Another bug report appearing the same day is even more direct. Its title states that the player killed Longtooth twice while using Mythic Tributes and received no drops at all.

That does not necessarily prove both reports share the same technical cause. One describes a boss death sequence becoming stuck. The other describes completed kills that apparently failed to produce loot.

But from the player's perspective, the distinction is not terribly comforting.

In both situations:

• a Mythic Tribute was consumed
• the player completed or effectively completed the Longtooth encounter
• the expected reward did not arrive

That is the part that matters.

Mythic Tributes Are Supposed to Make Undercity Runs Worth More

Tributes are not ordinary dungeon keys. Blizzard designed them as modifiers that let players deliberately influence an Undercity run and its rewards.

Higher-quality Tributes increase both the challenge and the potential spoils, creating a simple risk-reward relationship: spend something valuable, accept a more demanding run and receive something better if you succeed.

That relationship becomes especially important at the Mythic tier.

Players do not casually throw Mythic Tributes into every run. They are exactly the sort of resource people save for the right character, difficulty and farming session because the expected payoff can be extremely valuable.

Which makes a boss animation bug considerably more expensive than it sounds.

If an ordinary dungeon boss freezes, you lose a few minutes.

If Longtooth freezes after accepting a Mythic Tribute, you may lose the ticket as well.

This Is Not Diablo 4’s First Undercity Tribute Problem

Unfortunately, this is also not the first time players have reported the Undercity consuming Tributes without delivering what they expected.

Back in April, we covered players completing Undercity Tribute runs and receiving almost nothing. One Mythic Tribute run reportedly ended with a single blue item, while another player said an Armaments Tribute produced literally no loot.

Then in July, the problem became even stranger. We looked at Undercity bonus chests that could consume Tributes and open completely empty. Players also reported Mythic Armaments chests refusing to open despite apparently meeting their requirements.

Those older issues may not be technically related to the current Longtooth reports.

But they create a larger confidence problem around the same system.

Players need to know that when they spend a rare Tribute, the reward pipeline is reliable.

Longtooth Has Had Bugs Before

The boss itself also has some history.

Blizzard has previously fixed an issue where Longtooth could temporarily become invisible during a particular attack. That does not establish any connection to the current death-animation problem, but it does show that the encounter has required technical fixes before.

The new report appears to involve something different: the game recognizes enough of the boss's defeat to stop normal combat progression, but not enough to finish the encounter and release the rewards.

That is a particularly nasty category of bug because the player has already done everything correctly.

You entered the activity.

You spent the Tribute.

You completed the objective.

The game simply forgot the final verb:

pay.

There Is No Obvious Workaround Once the Tribute Is Spent

The September report also demonstrates why this bug is difficult for players to protect themselves against.

Teleporting away and returning did not fix Longtooth.

There is no reported method for reclaiming the Tribute from the run.

And unlike a bad random drop, this is not something another five minutes of farming necessarily replaces.

The only cautious advice at the moment is therefore frustratingly simple: be careful with Mythic Tributes until we know whether the Longtooth problem is isolated or reproducible.

That does not mean everyone should stop running the Undercity. Two reports do not establish a widespread failure rate, and most players may complete Mythic Tribute runs without encountering anything unusual.

But if you only have one particularly valuable Tribute left, there is no prize for volunteering it to quality assurance.

The Cost of a Bug Matters as Much as the Bug

Diablo IV has bugs. Every large live-service game does.

The interesting question is often not simply how frequently a bug appears, but what the player loses when it does.

A visual glitch costs almost nothing.

A stuck boss might cost several minutes.

A stuck boss after consuming one of the game's more valuable targeted-farming resources can cost substantially more.

That is why these new reports deserve attention even before we know how widespread the problem is.

Longtooth does not need to break every run to become dangerous.

He only needs to eat the Mythic Tribute you were actually saving.

```

Read More

Diablo 4 Players Say Activity Keys Are Becoming Rarer Than the Loot They Unlock

Diablo IV is supposed to have rare loot. That is rather central to the whole arrangement. Kill demons, open chest, receive seventeen things you do not want and occasionally make an undignified noise because something genuinely special appeared.

But some players are increasingly frustrated by a different kind of rarity: the items required to access the content where the interesting rewards are supposed to come from. Fresh complaints around Trace of Echoes and Crux of the False Prophet are reopening an old Season 14 argument, with players reporting enormous differences in how often these activity keys appear. Some have several sitting in storage. Others say they can play high Torment levels regularly for weeks — or even multiple seasons — without seeing one.

That raises a useful design question. Rare loot gives you something exciting to chase.

Should access to the activity itself be equally rare?

Trace of Echoes Is Supposed to Be Extremely Rare

There is one important point to establish immediately: Blizzard did not accidentally describe Trace of Echoes as an ordinary drop.

When Echoing Hatred was originally revealed alongside Lord of Hatred, Blizzard described it as a hyper-rare endgame event. To enter it, players first need an “incredibly rare” Trace of Echoes, which can then be offered to the Sightless Eye in Temis.

Once inside, Echoing Hatred becomes an escalating survival challenge with randomized enemies, multiple bosses and better rewards the longer you remain alive.

That sounds great.

Finding the door has proven rather more controversial.

Some Players Say They Have Not Seen One in Two Seasons

The extreme variation in player reports has been visible throughout Season 14.

One particularly persistent player has reported across several Blizzard forum discussions that they have not received a single Trace of Echoes in two seasons. Other players have reached Paragon 250 or higher without one, while some report finding several during the same period.

In one July discussion, a player at Paragon 262 said they had found none during the current season despite receiving seven or eight during the previous one. Another reported zero across characters around Paragon 235 and 260. Someone else had already found three.

That is RNG doing what RNG does.

The difficulty is that the result is not merely the difference between getting a Mythic and getting another pair of trousers.

One group gets to play an endgame activity.

The other group does not.

We previously covered players reaching very high Paragon levels without seeing a Trace of Echoes, and the same complaints continue to appear months later.

The Season Journey Makes the Rarity More Awkward

Trace of Echoes becomes particularly irritating because Echoing Hatred has also been tied to seasonal progression.

Players have pointed out that the Season Journey asks them to complete a sufficiently high tier of Echoing Hatred. That turns an intentionally rare activity into something sitting on a checklist beside objectives the player can actually choose to pursue.

You can improve a build.

You can run a boss.

You can clear a Pit tier.

You cannot make an incredibly rare random key appear through force of character.

Several players have therefore suggested giving at least one Trace of Echoes through Season Journey progression, with random drops remaining available for additional runs. That would preserve the event's rarity without allowing pure RNG to determine whether someone gets to experience one of Lord of Hatred's advertised endgame systems at all.

It is a fairly elegant compromise.

Make repeat access rare.

Do not make first access theoretical.

Crux of the False Prophet Has a Similar Problem

Trace of Echoes is not the only key causing frustration.

Crux of the False Prophet is used for Mephisto's high-end Tormented Echo rewards. Players have complained about its drop rate since Lord of Hatred launched, including reports of dozens of Greater Lair Boss runs without seeing one.

Again, experiences vary dramatically.

Some players report accumulating several Cruxes through Whisper Caches, Undercity runs and bosses. Others say the drops suddenly become extraordinarily scarce for long periods.

One particularly revealing June report came from a player who said they had found more than 40 Mythics, 12 Mythic Crux keys and more than 20 Mythic Tributes while receiving only a single Trace of Echoes — and that Trace then disappeared before they could properly use it.

That comparison illustrates the weirdness rather neatly.

At a certain point, the key to the activity can feel rarer than items Diablo IV otherwise treats as the pinnacle of the loot chase.

Rare Keys Work Better When the Content Is Repeatable, Not Invisible

There is nothing inherently wrong with rare access items.

Diablo has always used keys, organs, materials and other forms of friction between ordinary farming and special encounters. Building toward an Uber fight can make that fight feel more significant.

The difference is whether the player can meaningfully work toward the access requirement.

If ten known materials are required, you can farm ten materials.

If a boss requires a key with identifiable sources and a sufficiently predictable drop rate, you can target those sources.

If the requirement is simply an extraordinarily rare world drop, the strategy becomes:

continue existing near monsters and hope.

That is less compelling when the reward behind the key is not merely loot, but an entire mode.

Blizzard Has Already Adjusted Rare Endgame Access This Season

There is precedent for Blizzard deciding that access has become too restrictive.

During Season 14, the development team responded to progression feedback by increasing Mythic Tribute availability and adding Superior Lair Keys to repeatable reward sources. Blizzard has also adjusted various Lord of Hatred drop rates as player behaviour exposed bottlenecks that looked very different on live servers than they did on paper.

That is worth remembering when looking at Trace of Echoes.

The original concept — an extremely rare ticket into a mysterious survival event — sounds exciting.

But Diablo IV now has enough overlapping endgame systems that players do not necessarily interpret “you may never see this activity all season” as mystery.

Sometimes they interpret it as content they paid for but did not roll correctly enough to play.

Mythics Should Be Rare. Game Modes Are More Complicated.

The broader argument here is not that Diablo IV should shower everyone with every valuable resource.

We have just spent months watching the opposite debate, with some players worrying that Mythics have become too predictable and Diablo IV needs genuinely rare chase items again.

Those positions are not contradictory.

A rare item is exciting because most players know the item exists, know where it can come from and continue playing while hoping to receive it.

A rare activity key can instead mean the player never experiences the activity whose reward structure was supposed to create that excitement.

One is a chase.

The other can become a locked door with a lottery machine where the handle should be.

Diablo 4 May Need a Guaranteed First Key

The cleanest solution may therefore be the one players have already suggested.

Keep Trace of Echoes rare as a repeat drop.

Keep Crux of the False Prophet valuable.

Keep high-end encounters feeling like something more significant than another waypoint on the map.

But give players at least one deterministic path into the activities — perhaps through the Season Journey, War Plans or a sufficiently difficult guaranteed objective.

After that, RNG can resume its normal duties.

Rare loot is one of the reasons Diablo works.

Rare permission to play Diablo is a slightly stranger reward system.

```

Read More