Diablo 4 Players Say Some Pit Enemies Are More Dangerous Than the Boss

The Pit is supposed to get dangerous as Diablo IV players climb higher. That is rather the point of putting numbers on the entrance and making each one increasingly unpleasant. But a fresh community discussion is raising a slightly different complaint: what happens when one ordinary enemy inside the Pit feels dramatically more dangerous than everything else around it, including the boss waiting at the end? One player pushing above roughly Pit 85 says two particular enemy encounters and one crowd-control effect are producing exactly that experience, with attacks capable of shredding characters that otherwise survive the rest of the dungeon comfortably.

In the increasingly active Diablo IV forum discussion about high-Pit enemy tuning, the player singles out the Demonic Shade as one offender. According to their report, the enemy can reach the character and apply an effect that causes Life to rapidly drain away, while also being durable enough that simply deleting it before the mechanic activates is not always practical. The player's Necromancer can apparently escape the effect with Blood Mist, but the larger complaint is not that the Shade has a dangerous ability. It is that this one ordinary monster can suddenly demand considerably more defensive attention than almost anything else in the same Pit.

The Golden Bubble Enemy May Be Even Worse

The second complaint concerns enemies surrounded by what the player describes as a golden bubble. The exact monster type can vary, but one version reportedly launches a small earthquake-style ground attack capable of dealing enormous damage. According to the player, the enemy can fire these repeatedly, sometimes sending close to ten attacks before pausing. Staying close does not appear to prevent the behaviour, at least in their testing, and the result is an ordinary encounter that can become considerably more lethal than the Guardian waiting at the end of the run.

That distinction matters. Diablo IV absolutely needs dangerous normal enemies. If every monster between the entrance and the boss exists only as decorative experience points, the Pit becomes a jogging simulator followed by one actual fight. Elite affixes, positioning threats and dangerous monster families are what stop high-end dungeon pushing from becoming completely mechanical.

But difficulty also needs some internal logic.

If the player can survive the boss, ignore most elite attacks and move through the rest of Pit 90 without serious danger, then one otherwise unremarkable enemy suddenly producing several times that threat can feel less like progression and more like somebody accidentally moved a decimal point.

There Is Also a Rock That Apparently Hates Freedom

The third mechanic mentioned in the discussion is a summoned rock that binds the player while draining Life. The player argues that the object itself can require too much damage to destroy, particularly when it appears alongside the elite that summoned it and whatever else the dungeon has already placed on screen. In isolation, being forced to quickly destroy a binding object is perfectly reasonable encounter design. Combined with high-Pit damage scaling and multiple overlapping enemies, it can turn into the familiar Diablo IV problem of knowing exactly what is killing you while still having approximately half a second to do anything useful about it.

That problem has surfaced repeatedly this year. We previously looked at why Diablo IV players increasingly argue that one-shots are as much a visual-clarity problem as a damage problem. Falling swords, poison pools, earthquakes, elite effects and player abilities can all occupy the same patch of ground. The enemy mechanic may technically be avoidable, but that becomes considerably less comforting when locating it requires archaeological excavation beneath six other spell effects.

Other Players Say This Is Simply What High Pit Looks Like

Not everybody agrees that these enemies need adjustment. Several replies make the obvious counterargument: if a character is being killed in Pit 90, perhaps Pit 90 is currently too high for that character's defenses. One player argues that the attacks are not guaranteed one-shots and can be mitigated with sufficient Life, Armor, Resistance and Damage Reduction. Another points out that high-end Pit pushing eventually forces players into exactly this problem anyway. Push enough damage to beat the timer and defenses begin disappearing from the build. Keep enough defense to comfortably tank everything and eventually the character no longer has enough damage to advance.

That is a fair argument.

The Pit is not supposed to remain comfortable forever.

At some level, every character should reach a point where Sanctuary politely explains that the next number belongs to somebody with better gear, a stronger build or a considerably more unhealthy relationship with Greater Affixes.

The Question Is Whether the Difficulty Curve Is Consistent

This is where the current complaint becomes more interesting than “monster hurt me, please nerf monster.” The player specifically argues that almost nothing else in the same Pit presents comparable danger. Their objection is not that the entire tier is overwhelming. It is that certain monsters appear to punch far above the difficulty around them.

We have seen similar discussions around Spawn of the Damned apparently deleting Hardcore characters around Helltide Hellworms, although that case involves a different activity and potentially different underlying behaviour. We have also looked at why enormous Toughness values do not necessarily protect players against mechanics designed around specific encounter rules. Diablo IV contains plenty of situations where the dangerous thing is supposed to be dangerous.

The important question is whether the game communicates that difference clearly.

A giant boss winding up a screen-filling attack tells the player something unpleasant is about to happen.

An ordinary man walking over and touching you before your health begins evaporating communicates slightly less.

The Pit Needs Dangerous Monsters, Not Random Difficulty Spikes

There is a useful middle ground here. Blizzard does not need to turn every Demonic Shade into a training dummy. High-Pit players should encounter monsters that change their behaviour, force movement and occasionally make them abandon the usual rotation. That variety is healthy.

What probably deserves scrutiny is whether individual enemy abilities scale proportionally with the rest of the dungeon.

If one effect becomes dramatically stronger than the Pit Guardian at the same tier, Blizzard can adjust that ability without making the entire mode easier. If the real issue is defensive gearing, the game could do a better job showing players what damage type or modifier actually killed them. A clearer death recap would make that distinction much easier to diagnose.

Right now, both possibilities produce the same result:

the character is dead, the player stares at the screen, and somebody on the forum says they should have equipped more Damage Reduction.

Sometimes the Scariest Thing in the Pit Is Not the Boss

The current reports do not establish that Demonic Shades or golden-bubble enemies are bugged. They do not prove every build experiences the same damage, and the complaints mostly concern fairly high Pit levels where extreme scaling is expected. This remains player feedback rather than a confirmed Blizzard issue.

But the growing discussion highlights a useful rule for Diablo IV's endgame.

Hard content should be hard.

Dangerous monsters should exist.

And the highest Pit levels should eventually tell every build to go home.

But when the player can comfortably survive the dungeon boss and then gets vaporized by Steve from Accounting standing three rooms earlier, the difficulty curve may deserve another look.

Read More

Diablo 4 Players Want Lilith and Mephisto Out of the Season Journey — Others Say That’s the Point

Diablo IV has a recurring seasonal tradition that has nothing to do with demons, loot or accidentally salvaging the item you meant to keep. Every few months, players eventually reach the difficult end of the Season Journey, see Echo of Lilith and Mephisto waiting on the checklist, and begin arguing about whether pinnacle bosses belong there at all. Season 14 has reached that moment again. A renewed forum discussion is asking Blizzard to remove Lilith and Mephisto from mandatory Season Journey progression, while other players are pushing back with an equally simple argument: if the Season Journey is supposed to measure character progression, eventually asking the character to kill something difficult seems rather reasonable.

The awkward part is that both positions make sense.

Season Rank Is Supposed to Get Harder

Blizzard deliberately rebuilt Diablo IV's seasonal progression around Season Rank. Instead of simply filling pages with miscellaneous objectives until a bar reaches the end, advancing through later ranks requires increasingly serious character milestones. Blizzard described the redesigned system as a more challenging version of the Season Journey where Capstone-style objectives test your progress through Diablo IV's difficulty tiers.

Season 14 takes that philosophy to its logical conclusion. Current in-game Season Journey data places Echo of Lilith on Torment VIII as the gate into Rank VIII, while Echo of Mephisto on Torment X sits between Rank VIII and IX. By the time the game asks for those kills, Blizzard is no longer checking whether you remembered to salvage twenty swords or complete a Helltide. It is asking whether the character you have spent the season building can defeat major endgame bosses.

On paper, that feels entirely appropriate.

Diablo is, after all, a game about making a character increasingly unreasonable until Hell files a formal complaint.

Lilith Is Where the Argument Gets Messier

Echo of Lilith has never been an ordinary damage check. Her encounter asks players to understand mechanics that can punish mistakes regardless of how impressive the character sheet looks. We recently saw that very clearly when a player entered the Lilith encounter with roughly 1.2 million Toughness and still discovered that the headline defensive number did not make the mechanics disappear.

That distinction matters because some players do not object to the Season Journey becoming difficult. They object to one specific boss becoming a recurring seasonal exam when her fight behaves very differently from most of Diablo IV.

One player in the current discussion argues that Lilith and Mephisto create severe friction for people who simply want to complete seasonal progression. Another says these encounters disproportionately reward particular builds and therefore encourage people to abandon their own setup and copy a meta build long enough to remove the boss from the checklist.

Other players strongly disagree. One says an A-tier build killed Lilith within roughly twenty hours and Mephisto later without requiring anything extraordinary. Another argues these boss fights are among the only objectives in the Season Journey that remain remotely challenging once a character has accumulated serious endgame gear.

Remove every difficult requirement, the argument goes, and the Season Journey stops being a journey.

It becomes paperwork with demons.

Mephisto Adds a Different Kind of Friction

Mephisto is complicated for another reason because Diablo IV's high-end content increasingly mixes character power with access requirements. We have repeatedly covered players arguing that some endgame activity keys are becoming rarer than the rewards behind them. That matters whenever seasonal progression points toward activities whose first obstacle is not necessarily the boss, but getting the game to let you fight it properly.

Echoing Hatred has been the clearest example. Some players have reached extremely high Paragon levels without seeing the required Trace of Echoes, while others have found several. More recently, players who actually obtained the Trace have reported being locked out by the Resounding Scream quest anyway.

This is where seasonal checklists become dangerous. A difficult objective is fair because the player can improve. Upgrade gear. Learn mechanics. Change a skill. Practice the encounter.

An objective controlled by unreliable access or progression bugs is something else entirely.

You cannot outplay a door that refuses to open.

Maybe These Bosses Belong in the Optional Objectives

One of the more sensible compromises in the current discussion is not to remove Lilith and Mephisto completely. Keep them inside the Season Journey, but make them part of the optional high-end objectives rather than hard progression gates.

That would allow Blizzard to preserve meaningful seasonal challenges for players who enjoy pushing toward complete mastery while letting less competitive players finish the fundamental seasonal progression through alternative objectives. Diablo IV already uses that philosophy at Rank IX, where players choose from a larger collection of demanding endgame tasks rather than completing every single item on the page.

Unfortunately, even that system has occasionally suffered from its own problems. We previously covered players completing the required Rank IX objectives only to find the Gilded Laurel reward still refusing to unlock. Diablo IV is remarkably capable of turning a checklist into endgame content all by itself.

A Season Journey Needs to Decide Who It Is For

The deeper issue is similar to the Torment XII argument Diablo players are having right now. Blizzard needs clearer boundaries between ordinary seasonal progression and aspirational endgame.

If the Season Journey represents the basic path through each season, requiring pinnacle bosses becomes questionable. A player can experience the seasonal story, systems, loot and most of the endgame without ever needing to prove they can kill Lilith on Torment VIII.

If Season Rank is instead meant to certify that a character has genuinely progressed from fresh seasonal wanderer to powerful endgame build, difficult boss gates make considerably more sense.

Blizzard appears to favour the second interpretation.

Some players clearly favour the first.

That disagreement is not going away simply by changing Lilith's health bar.

Diablo Needs Challenges, But Not Every Challenge Needs to Be Mandatory

There is a danger in overcorrecting here. Diablo IV should absolutely have objectives that some players cannot complete on the first evening. It should contain bosses that force builds to improve and mechanics that occasionally require moving away from the glowing red thing rather than calculating whether enough Barrier can make standing inside it a lifestyle choice.

A seasonal progression system with no meaningful resistance becomes pointless.

But optional challenges exist for exactly this reason.

Let the Season Journey guide players through Sanctuary. Let difficult bosses prove that a build has matured. Let the very hardest objectives offer extra cosmetics, titles or prestige for people who want everything.

The question is not whether Echo of Lilith and Mephisto deserve to be difficult.

They do.

The question is whether everybody completing a Diablo IV season needs to pass the same final exam.

Sanctuary already has plenty of demons.

Perhaps the checklist does not need to become one too.

Read More

Is Torment 12 Supposed to Be Farmable? Diablo 4 Players Can’t Agree What Endgame Means Anymore

Diablo IV players have found a surprisingly philosophical question hiding behind twelve increasingly angry difficulty settings: what is Torment XII actually supposed to be? Is it the normal destination for a finished seasonal character, a comfortable farming tier that most reasonable builds should eventually reach, or is it Diablo IV's maximum world difficulty precisely because Blizzard expects plenty of builds to struggle there? A new community debate has managed to produce passionate arguments for all three answers, which is impressive considering the game helpfully placed the number twelve directly after eleven.

The discussion began with a forum post arguing that Torment XII has become unnecessarily hostile to off-meta builds. The player describes T12 as something that should function as a comfortable farming tier rather than an elite challenge comparable to the highest Pit levels. Several replies immediately challenge that premise. Torment XII is not a middle difficulty. It is literally the highest standard World Difficulty currently available, and some players argue that reaching it comfortably should require a highly developed character rather than simply be another checkbox on the seasonal journey.

Both sides have a point.

Which may be Blizzard's real problem.

Blizzard Has Always Called Torment Endgame

When Blizzard originally rebuilt Diablo IV's difficulty structure, it described Torment as the point where “the endgame truly begins.” Higher Torment levels were connected to increasingly demanding Pit clears, with stronger enemies balanced against better chances for high-quality rewards. The fundamental idea was easy enough to understand: campaign and leveling difficulties prepare the character, Torment begins the endgame, and increasingly powerful builds can climb further.

Lord of Hatred dramatically extended that ladder. As we covered when Blizzard first discussed expanding Diablo IV all the way to Torment XII, the intention was not simply to create eight additional versions of the same health sponge. The expanded difficulty range was supposed to let more activities scale further into the endgame rather than forcing every powerful character into a tiny number of challenge modes.

That makes Torment XII unquestionably endgame.

It does not necessarily tell us whether everybody is supposed to farm it.

Maximum Difficulty and Normal Farming Are Not the Same Thing

This distinction gets lost surprisingly quickly in Diablo discussions because players naturally treat the highest visible number as the destination. If twelve exists, twelve must be where the character eventually lives. Anything below it can start feeling unfinished, even if the game remains perfectly playable and rewarding there.

But one of the strongest replies in the current discussion makes a simple counterargument: T12 is the maximum difficulty. If an experimental homebrew build comfortably destroys everything there without requiring serious gear optimization, glyph progression or intelligent build choices, then what purpose does the difficulty ladder actually serve?

That does not mean only three leaderboard builds should function at T12. Build diversity matters enormously in an ARPG, and a difficulty system becomes very dull if reaching its upper tiers means opening a tier list and copying whatever currently has the largest multiplication symbol. But there should probably be some distinction between “this build works” and “this build effortlessly farms the hardest normal difficulty in the game.”

Otherwise Torment XII is not really Torment XII.

It is Torment X wearing two more numbers.

Torment X May Be the More Important Line

Several players in the discussion argue that Torment X feels like the more natural farming benchmark. By that point, a character has progressed very deep into Diablo IV's systems, and much of the ordinary reward structure is already available. T11 and T12 can then function more like optimization territory for players who want to squeeze additional performance from their builds rather than mandatory destinations for everybody.

Blizzard's own reward adjustments have occasionally reinforced that distinction. In July, Blizzard changed Mythic Tribute of Armaments so Torment XII guarantees a Mythic item, while Torment X received a greatly increased chance instead. That is a meaningful reward for tackling the highest difficulty, but it also creates a useful choice. A player who can reliably farm T12 gets certainty. A player whose build performs comfortably in T10 can accept the lower difficulty and a less certain reward rather than spending twice as long fighting every elite pack.

That is what a healthy difficulty ladder should do.

Higher difficulty should be desirable.

It should not necessarily be compulsory.

Off-Meta Builds Complicate Everything

The original complaint is really about build diversity. The player argues that Torment XII punishes creative or unusual setups too heavily and turns the highest farming tier into territory dominated by meta builds. Other players strongly disagree, with several claiming they have taken distinctly off-meta builds into T12 through better gear, upgraded glyphs and careful optimization.

That disagreement is difficult to settle because “off-meta” can mean almost anything.

One player's off-meta build is a carefully constructed alternative using strong interactions nobody happened to put in an S-tier guide. Another player's off-meta build is six skills they enjoy, a suspicious collection of affixes and the firm belief that Blizzard should respect their artistic vision.

Those are not the same problem.

Diablo IV should support experimentation. It should allow players to discover strange interactions and build around skills because they are fun rather than because a spreadsheet ranked them first. But build freedom cannot reasonably mean every possible collection of skills must clear every difficulty at the same speed. At some point, difficulty has to test whether the build actually functions.

The difficult question is where that point should sit.

The Pit Already Provides a Different Kind of Challenge

This is where Diablo IV's endgame structure becomes increasingly messy. If T12 is supposed to be aspirational, what is the Pit for? If Pit 150 is the true extreme challenge, why should ordinary open-world farming become restrictive several layers earlier? Then there is the Tower, leaderboard pushing, Echoing Hatred and high-end boss content, all competing to represent different versions of “the endgame.”

We recently looked at how the Tower struggles to separate pure skill from gear quality and Transfiguration RNG. Echoing Hatred creates another level of exclusivity because some players have spent enormous amounts of time simply trying to obtain access to the activity. Diablo IV now has several overlapping ladders, each supposedly answering a slightly different question about how powerful a character has become.

The problem is that the game does not always explain those questions particularly well.

Tower asks how far you can push competitively.

Pit asks how high your build can scale.

Echoing Hatred asks whether you can survive a specialized pinnacle challenge.

Torment determines the difficulty of much of the ordinary world.

Those roles make sense individually.

Together, they can make “endgame” mean practically everything after breakfast.

T12 Probably Should Be Difficult

There is one fact the current argument cannot completely escape: Torment XII is the highest standard difficulty in Diablo IV. Calling it a basic mid-tier farming level feels difficult to defend when eleven easier options exist underneath it.

That does not excuse bad class balance. If a handful of builds obliterate T12 while equally well-constructed alternatives hit an artificial wall several tiers earlier, Blizzard should investigate the gap. The purpose of difficulty should be to reward stronger characters and better builds, not to quietly announce which six skills the designers remembered to tune that season.

But a maximum difficulty should also be allowed to say no.

Not every fresh level-cap character needs to reach it.

Not every homebrew build needs to speedfarm it.

And not reaching Torment XII does not mean the character has somehow failed to enter Diablo IV's endgame.

The Real Problem Is That Diablo 4 Has Too Many Definitions of Finished

This may be why the forum argument is more interesting than another build-balance complaint. Diablo IV increasingly lacks one obvious answer to the question: when is a character finished?

Is it when you reach T10?

When you unlock T12?

When you can farm T12?

When you clear Pit 100?

150?

When you enter the Tower Top 100?

When Echoing Hatred finally stops treating your build like a clerical error?

The answer is probably supposed to be whichever goal the player enjoys pursuing. That flexibility is one of Diablo's strengths. But it also means Blizzard needs clearer boundaries between ordinary progression, optimized farming and genuinely aspirational content.

Torment XII can be difficult without being mandatory.

Torment X can be useful without being failure.

And an off-meta build can be perfectly viable without being entitled to demolish the hardest world setting at jogging speed.

The number twelve is not a graduation certificate.

Sometimes it is simply another demon-filled door you have not kicked open yet.

Read More

Diablo 4 Players Don’t Want More Loot. They Want Drops to Feel Exciting Again

Diablo has spent nearly thirty years teaching players one extremely simple reflex. Something rare hits the floor, your brain makes a small happy noise, and whatever you were supposed to be doing for the next ten minutes is immediately forgotten. Diablo IV certainly does not suffer from a shortage of things hitting the floor. Season 14 has thrown Mythics, Iconic Mythics, Uniques, Ancestrals, Charms, Seals, Transfiguration possibilities and enough crafting materials at players to make Sanctuary's janitorial staff eligible for hazard pay. Yet a fresh community discussion is circling around a much less comfortable question: why do so many of those drops no longer feel particularly exciting?

The conversation started with a Diablo IV forum post comparing Season 13's item chase with the Mythic-heavy systems introduced afterward. The original poster says Season 13 kept both them and their friends playing significantly longer because hunting exceptional gear felt rewarding, while Season 14's Mythic changes had the opposite effect. That is one player's experience, not population data, but the replies quickly arrive at a broader criticism we have heard throughout this season: Diablo IV may have increased access to powerful loot while simultaneously weakening the emotional value of finding it.

More Mythics Did Not Automatically Create a Better Chase

Season 14's launch demonstrated the problem almost immediately. Mythics were supposed to form the heart of the season's endgame, but low drop rates, restrictive crafting and several broken reward paths made the system feel miserable. Blizzard reacted quickly. As we covered when Patch 3.1.1 significantly improved Season 14's loot economy, Mythics became easier to obtain, Iconic Mythics became less ghostly and several reward sources started behaving properly.

Then Blizzard went further. The one-crafted-Mythic equipment restriction was removed during Season 14, drop rates increased again and Torment XII eventually received a guaranteed Mythic reward from Mythic Tribute of Armaments runs.

The result solved one problem.

Players could get Mythics.

It created another question: what exactly is a Mythic supposed to feel like once purple items stop being mythical?

A Rare Color Is Not the Same Thing as a Rare Feeling

One reply in the current discussion describes ordinary Uniques as little more than transitional equipment until their Mythic versions appear. That gets remarkably close to the heart of the issue. If the eventual destination is simply the same item at Mythic quality, then the original Unique can stop feeling like a prize and start feeling like unfinished paperwork.

That is particularly awkward because Blizzard spent Season 14 trying to protect Unique identity. We previously looked at the decision to give Uniques two guaranteed thematic affixes after PTR feedback raised concerns that randomized stats were making supposedly special items feel like ordinary Legendaries wearing expensive shoes.

The intention was sensible. A Unique should have a personality.

But personality matters considerably less if the player immediately looks at it and thinks, “Fine, now where is the purple version?”

The Other Extreme Is Not Better

This does not mean Diablo IV should return to a world where Mythics are so rare that most players only encounter them in screenshots posted by somebody with 900 hours and suspiciously flexible employment. Another active discussion this weekend shows how divided the community remains. Some players want Season 14's generous Mythic crafting to continue, while others argue that the so-called “purple rain” effectively ended their gear progression because characters could become covered in Mythics too quickly.

That distinction matters.

The solution is probably not simply less loot.

It is also not simply more loot.

Diablo needs progression where each step still has somewhere meaningful to go. A good Unique should be exciting. An exceptional Ancestral version should be more exciting. A Mythic should feel extraordinary. And obtaining one should open another interesting decision rather than merely changing the color of the item while adding another round of numerical optimization.

Season 15 Is Already Trying to Repair Part of This

Blizzard clearly knows Season 14's Mythic design did not land cleanly. The official Season 15 PTR overview says Mythics are being simplified again, with Blizzard explicitly citing player feedback. The current random Horadric Cube transformation is being replaced by a direct upgrade path that preserves the Unique item you actually chose.

We have already covered why preserving the original Unique makes considerably more sense than throwing it into a Mythic raffle. If you put a specific Unique into the Cube, Season 15 intends to give you the Mythic version of that item rather than a completely unrelated piece occupying the same slot.

That is better control.

But control and excitement are not necessarily the same thing.

Make everything completely deterministic and Diablo risks becoming a shopping list. Add too much randomness and the game becomes a casino where every loss asks for another three hours of farming. Shower players in Mythics and the rarest gear becomes routine. Starve them of Mythics and most of the system may as well not exist.

Somewhere between those extremes is the thing Diablo has always been very good at when it works:

the possibility that the next monster might drop something you genuinely want to stop and look at.

That Is the Loot Problem Blizzard Still Has to Solve

Diablo IV has spent three years improving the machinery around loot. Target farming has become more sophisticated. Boss tables are clearer. Crafting offers more control. Mythics have expanded. Greater Affixes, Tempering, Masterworking, Transfiguration and the Horadric Cube all provide ways to keep developing an item after it appears.

That machinery is impressive.

But the machine cannot become more exciting than the thing coming out of it.

The current community argument is useful because it moves the conversation away from raw drop percentages. Players are not universally asking Blizzard to increase Mythic rates again. They are not universally demanding another nerf either. What many of the complaints have in common is simpler.

They want finding an item to matter again.

Not after three Cube recipes, four rerolls and a Transfiguration spreadsheet.

When it hits the ground.

Because Diablo can have all the endgame systems in Sanctuary.

If nobody gets excited when the loot drops, something considerably more important than the drop rate is broken.

Read More

Diablo 4 Player Says a 400-Hour Top 100 Push Was Cut Short by the Tower Closing

There are casual Diablo IV players, there are dedicated Diablo IV players, and then there are people who have spent roughly 400 hours in a single season calculating whether another piece of gear can move them eighteen places up a leaderboard. One Season 14 player says they belong firmly in the third category. After climbing as high as global rank 119 on the Spiritborn Tower leaderboard before slipping to rank 167, they spent the final stretch theorycrafting, farming and assembling a completely new gear setup for one last attempt at the Top 100. Then they logged in and discovered the Tower was closed.

The player is understandably not delighted. In a new Diablo IV forum post about the Tower closure, they say the shutdown arrived without a clear in-game warning or visible countdown and effectively ended their competitive Season 14 push before they expected it to end. They describe having a build hitting around 424 trillion damage, with further theoretical scaling available, and believed the new setup was capable of getting them inside the Top 100.

Whether it actually would have done so is unknowable now.

Which is rather the problem.

400 Hours Came Down to One Final Push

The player says they had invested close to 400 hours during Season 14, with the Tower becoming the main purpose of that grind. They had already reached rank 119 globally, then slipped to 167 as other players improved their own runs. Rather than accepting the drop, they started rebuilding specifically for another attempt. New gear. More optimization. More calculations. More farming. The sort of endgame behaviour where Diablo stops being a game about killing demons and quietly becomes a spreadsheet that occasionally screams.

The stated goal was simple: finish inside the Top 100.

That matters more in Season 14 because the Tower is no longer merely a beta experiment. Blizzard officially moved Tower and Leaderboards out of Beta and attached meaningful ranking rewards to them. Players can earn rewards for participating, reaching Tower Tier 100 and finishing inside the Top 1,000, Top 500, Top 100, Top 10 or rank #1, with Halo cosmetics and Prestige Titles tied to performance.

We already looked at why that changes the conversation in our article asking whether Diablo IV's Tower leaderboard measures player skill or simply better RNG. Once Blizzard puts exclusive rewards and visible rankings behind a mode, players will inevitably treat those rankings seriously. Rank 101 is no longer merely one number below rank 100. It can represent a different reward tier.

But Was the Tower Actually Closed Early?

This is where the complaint becomes more complicated.

The original poster describes the Tower as being closed roughly two weeks before the end of the season and argues that the finish line was moved without warning. Another player in the same discussion immediately pushes back on that interpretation, saying leaderboard runs operate in two-week cycles and that the Tower also closes around patches, adding that the same thing happened last season.

The original poster accepts that context but argues that this is precisely the problem. A competitive system should not require players to remember what happened last season, infer the schedule from patch timing or learn the rules through forum replies after the door has already closed. Their suggestion is extremely simple: put a visible countdown inside the Tower interface.

That feels like the stronger argument.

If the closure happened exactly according to Blizzard's intended schedule, then this is not really a story about Blizzard unexpectedly changing the rules. It is a story about those rules apparently not being communicated clearly enough to someone who spent hundreds of hours competing under them.

We Have Already Seen This Problem With the Tower

Unfortunately, the Tower and calendars have met before, and the relationship has not always been romantic. Earlier this year, we covered players discovering that Tower-related seasonal objectives remained visible while the Tower itself was closed. That produced a remarkably similar question: if content becomes unavailable according to a schedule, how clearly should the game communicate that schedule to players whose progression depends on it?

We have also seen smaller rule and reward problems around the mode. A Season 14 bug meant Tower rewards could behave incorrectly for party members while Solo Self-Found visibility was also broken. None of these issues means the Tower itself is a failure. In fact, the intensity of the current complaint suggests almost the opposite. Players care enough about the mode to spend hundreds of hours optimizing for it.

That is valuable.

It also means the boring administrative parts suddenly matter enormously.

A Competitive Leaderboard Needs a Visible Finish Line

Diablo IV is never going to be a perfectly standardized competitive game. Gear matters. RNG matters. Class balance matters. Transfiguration rolls can matter enormously, something we have already seen in Season 14's increasingly elaborate Transfiguration endgame. Two players entering the Tower are not starting from identical equipment and being asked to perform the same mechanical test.

But the calendar is different.

Everybody can understand a countdown.

If a leaderboard closes Friday at a specific time, put that time on the leaderboard. If the final competitive cycle ends two weeks before the season itself, state that explicitly. If a patch temporarily disables the Tower, show it before somebody spends three evenings rebuilding an entire loadout for a run they can no longer submit.

These are not balance decisions. They are interface decisions.

And they become particularly important when Blizzard itself has encouraged players to care about specific ranking thresholds.

The Player Did Not Lose 400 Hours, But the Frustration Makes Sense

It would be unfair to say all 400 hours were wasted. The player reached rank 119 globally, competed near the top of the Spiritborn leaderboard and presumably accumulated everything else that comes with playing Diablo IV at that level. A leaderboard position is also never guaranteed merely because a player believes their new gear can achieve it. The Top 100 contains ninety-nine other people with similarly inconvenient ambitions.

But that is not really what the complaint is about.

The player wanted the chance to try.

They built toward a final run because they believed the competitive window was still open. When they were ready, it was not.

If Blizzard's schedule was operating exactly as designed, then the solution does not require changing the Tower season, giving anybody a free ranking or reopening the leaderboard because one player missed the cutoff.

It requires a clock.

Diablo IV already asks its most dedicated players to track gear rolls, Paragon choices, War Plans, crafting materials, boss keys, Transfigurations and enough multiplicative damage modifiers to frighten a mathematics department.

Remembering when the leaderboard quietly locks should probably not be another build requirement.

Read More

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

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

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

Diablo 4's Recent Reviews Are Sitting at 68%

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

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

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

This Is Not Another “Diablo 4 Is Dead” Story

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

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

That is considerably more interesting.

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

Read More

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

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

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

Spawn Might Be the Most Natural Weird Crossover Yet

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

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

Chains and Hell are confirmed.

Everything beyond that can wait.

Lut Gholein Is Getting Bigger Again

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

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

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

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

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

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

Two New Legendary Gems Are Coming

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

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

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

Battlegrounds Are Going Back to Their Nephalem Look

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

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

And Blizzard Is Already Teasing What Comes After Spawn

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

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

Spawn is inevitably going to get most of the attention.

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

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

Apparently Sanctuary was not busy enough already.

Read More

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

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

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

The Quote Really Happened

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

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

That last possibility would almost be refreshing.

Blizzard Has Since Made the Tease More Interesting

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

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

BlizzCon should finally separate those two categories.

Diablo 4 May Not Be the Only Game Involved

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

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

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

Players Have Had Seven Months to Invent Answers

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

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

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

It is a magnificent hype generator.

It is a terrible source of specifics.

Blizzard Is Clearly Expecting People to Watch

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

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

There is clearly something to talk about.

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

Tomorrow the Sentence Finally Gets an Ending

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

Tomorrow the board gets considerably smaller.

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

Everything after that remains speculation.

For one more day.

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

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

Read More

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

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

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

$12.49 Is a Very Different Diablo 4 Purchase

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

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

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

The Sale Arrives at an Interesting Moment for Diablo 4

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

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

It is also sensible marketing.

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

This Does Not Tell Us What Blizzard Is Announcing

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

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

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

If You Were Waiting, $12.49 Is Hard to Ignore

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

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

At $12.49, the calculation becomes rather different.

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

Pure coincidence?

Quite possibly.

Very convenient coincidence?

Absolutely.

Read More

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

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

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

Patch 3.1.4 Is Real. The Patch Notes Are Not Here

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

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

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

The BlizzCon Timing Is Almost Comically Convenient

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

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

There Is One Big Problem With the Secret Season 15 Theory

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

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

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

Sometimes somebody forgot to publish the notes.

Blizzard Should Still Explain What Changed

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

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

For Now, Patch 3.1.4 Is Mostly Excellent Timing

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

We just cannot justify doing it yet.

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

Fortunately, BlizzCon begins tomorrow.

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

Read More

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

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

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

Amazon Absolutely Makes Sense After Lord of Hatred

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

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

That makes Amazon plausible.

It does not make Amazon leaked.

The Hand Crossbow Clue Actually Points Somewhere Else

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

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

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

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

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

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

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

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

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

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

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

Every individual step is possible.

The problem is that possibility compounds very badly when stacked.

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

Paladin Early Access Does Not Establish a New Annual Class Pattern

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

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

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

What Blizzard Has Actually Said About BlizzCon Is Much Broader

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

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

Something is clearly happening.

“Something” remains frustratingly different from “Amazon.”

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

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

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

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

There Are Other Candidates With Equally Interesting Clues

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

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

Congratulations to them. It worked.

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

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

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

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

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

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

So yes, we would happily play an Amazon.

We might even believe Blizzard is preparing one.

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

Read More

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

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

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

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

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

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

Two-Handed Weapons Are Supposed to Support Two Sockets

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

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

Baleful Fragments Make a Failed Socket Expensive

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

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

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

A Similar Socket Report Appeared Back in May

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

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

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

The Increasing Price Makes Repeated Testing a Bad Idea

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

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

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

Blizzard Has Been Adjusting Socketing for Years

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

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

This Is Still One Fresh Xbox Report

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

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

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

A Jeweler Should Probably Provide the Jewelry Service

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

Once is annoying. Twice begins to feel personal.

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

Sanctuary's merchants already charge enough.

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

Read More