Diablo news and guides

Diablo 4 Player Says an Escalation Sigil Kicked Them Out Mid-Dungeon

2026-08-22T03:15:30.777-07:00

Escalating Nightmares are supposed to send Diablo 4 players deeper into increasingly dangerous dungeons.

One player's Legendary Escalation Sigil apparently had a different destination in mind.

Outside.

A fresh Diablo IV bug report describes a player successfully completing the first two stages of an Escalating Nightmare before the portal to the next dungeon appeared.

Instead of continuing the chain, the player says they suddenly found themselves standing at the Vision's End waypoint in the open world.

No return portal.

No third dungeon.

No way back into the Escalation.

Just Sanctuary politely informing them that their endgame activity was apparently over.

The First Two Dungeons Worked Normally

The report was posted on Blizzard's official Diablo IV PC Bug Report forum on August 21.

The player had activated a Legendary Escalation Sigil for Blind Burrows.

According to the report, the first dungeon completed normally.

So did the second.

That matters because Escalating Nightmares are not ordinary Nightmare Dungeons.

They are designed as a sequence of three connected Nightmare Dungeons.

After completing one stage, a Horadric Portal should appear and carry the player into the next dungeon.

The Nightmare affixes accumulate as you progress, increasing both difficulty and potential rewards.

Complete all three on Torment difficulty and the chain eventually leads to the Exalted version of Astaroth.

At least that is the plan.

The Portal Appeared — Then the Player Was Suddenly at Vision's End

The strange part happened after the second dungeon.

The player says the expected portal appeared.

Then something went wrong.

The next thing they knew, they had been transported to Vision's End, an outdoor waypoint associated with the newer expansion content.

The Escalating Nightmare was gone.

There was no portal allowing them to return.

That effectively ended the entire run after two completed dungeons.

For an ordinary Nightmare Dungeon, an unexpected teleport would already be annoying.

For an Escalation, it is worse because the player has invested time in building toward the final stage.

The whole activity is structured around progression.

Dungeon one sets up dungeon two.

Dungeon two makes dungeon three harder.

Dungeon three leads toward the final reward.

Being thrown into the open world after stage two is approximately equivalent to completing two-thirds of a roller coaster and discovering the remaining track has been replaced by a bus stop.

The Player Thinks a First-Time Dungeon Completion May Be Involved

There is one potentially interesting detail in the report.

The player believes one of the dungeons may have been a location they had never completed before.

They received a dungeon completion cache.

That led them to wonder whether the game processed the first-time dungeon completion incorrectly and somehow interrupted the Escalation transition.

That is currently speculation.

We do not have enough reports to establish that completing a previously unfinished dungeon actually causes the problem.

It could be unrelated.

It could be the portal.

It could be the selected dungeon.

It could be some interaction between Escalation progression and expansion-state tracking.

At this point we only know the reported result:

the Escalation stopped after dungeon two and the player was teleported outside.

This Is Currently a Single Player Report

That distinction is important.

There is currently no evidence that Legendary Escalation Sigils are broadly throwing Diablo 4 players out of their runs.

The August 21 report is a fresh PC bug report rather than a widespread confirmed outage.

Blizzard has not yet identified the cause in the thread.

So this is not a situation where players should immediately start destroying every Escalation Sigil in their stash.

Especially since Blizzard recently made them salvageable.

You can at least destroy them professionally now.

But the report is worth watching because Escalating Nightmares have previously experienced several progression-related bugs.

Escalating Nightmares Have Had Portal Problems Before

Blizzard introduced Escalating Nightmares as a major endgame system in Season 9.

The activity has remained part of Diablo IV since then, but its unusual three-dungeon structure creates more opportunities for progression problems than a normal Nightmare Dungeon.

Blizzard has already fixed several of them.

Patch 2.3.2, for example, fixed a problem where the Horadric Portal could stop functioning if the party member who activated the Escalation Sigil left the group.

The same update fixed cases where the number of disabled affixes could incorrectly reset during an Escalation.

Patch 2.3.3 later fixed another issue where the Vile Hive dungeon would fail to escalate correctly under specific circumstances.

More recently, Blizzard fixed Escalation Dungeons selecting Stronghold dungeons that the player had not actually unlocked.

None of that proves the new Vision's End incident shares the same cause.

It does demonstrate that moving players through a chained dungeon system has created some unusual edge cases before.

Escalation Runs Hurt More When They Fail Late

The timing of the bug is what makes the latest report particularly painful.

An Escalating Nightmare becomes more valuable the further you progress.

Affixes from earlier Nightmare Dungeons carry forward.

Difficulty rises.

Rewards improve.

And completing the full sequence is supposed to culminate in the special Astaroth encounter.

A failure during dungeon one wastes some time.

A failure after dungeon two wastes considerably more.

It is the same fundamental problem we have seen with other recent Diablo 4 bugs.

When a system asks players to invest time before delivering the payoff, technical problems near the end feel disproportionately bad.

We recently covered how players can complete all 65/65 areas of Skovos and still fail to receive the associated achievement.

Different system.

Same unpleasant feeling.

The game recognises most of the work.

Then something fails at the point where it is supposed to matter.

Patch 3.1.3 Already Contains an Escalation Nightmare Fix

Escalating Nightmares are still actively being maintained.

Diablo IV Patch 3.1.3, released on August 12, includes a specific fix allowing Escalation Nightmare Dungeons with the Ruptures affix to properly count toward the Season Rank III Set Fire to the Beacons objective.

The larger 3.1.0 update also made Escalation Sigils salvageable and fixed the issue where Escalation Dungeons could include Strongholds that had not been unlocked.

So Blizzard is clearly still adjusting the system.

The new report arrived nine days after that latest Escalation-related fix.

There is currently no corresponding fix listed for players unexpectedly being removed from the dungeon chain.

There Is No Clear Workaround Yet

Because only one detailed report is currently available, there is no reliable workaround to recommend.

The player could not return to the Escalation after being transported to Vision's End.

There was no portal waiting at the waypoint.

And the report does not indicate that relogging or returning to Blind Burrows restored the run.

If the first-time dungeon completion theory eventually proves correct, players could theoretically avoid Escalations containing unexplored dungeons.

But we are nowhere near having enough evidence to recommend doing that.

For now, anyone experiencing the same behaviour should probably note:

Which Escalation Sigil was used
Which three dungeons were selected
Which dungeon stage failed
Whether the dungeon had been completed before
Which waypoint the game transported them to
Whether a completion cache or first-clear reward appeared

Those details would make it considerably easier to determine whether multiple cases share the same trigger.

Hopefully This One Remains Rare

Escalating Nightmares are one of Diablo 4's more interesting endgame ideas precisely because they do more than simply increase a dungeon number.

They create a small endurance run.

Each dungeon changes the next.

The pressure builds.

And players know there is something waiting at the end.

Which means the transition between those dungeons absolutely has to work.

The August 21 incident may turn out to be an extremely rare edge case.

Hopefully it is.

But if more players begin reporting the same unexpected trip to an outdoor waypoint, Blizzard may have another Escalation progression bug to investigate.

Diablo 4's Nightmare Dungeons are supposed to become increasingly hostile.

The portal itself probably does not need to join the enemy team.

Sources

Diablo IV Forums: Legendary Escalation Sigils Bugged

Blizzard: Escalating Nightmares explained

Blizzard: Diablo IV Patch 2.3 Escalating Nightmare fixes

Blizzard: Current Diablo IV Patch Notes

```

Diablo 2 Season 15 Just Unlocked Eight Ladder Runewords for Non-Ladder Players

2026-08-22T03:00:00.474-07:00

Diablo II: Resurrected Ladder Season 15 has officially started.

But one of the most useful changes is actually for people who have absolutely no intention of playing Ladder.

Patch 3.3 has moved eight previously Ladder-only Rune Words into Non-Ladder, finally allowing permanent characters to create several recipes that had remained locked behind seasonal play.

The newly available Rune Words are:

Mania
Hysteria
Metamorphosis
Ground
Temper
Hearth
Cure
Bulwark

For longtime Non-Ladder players, this is considerably more interesting than another race to level 99.

Your old characters just received eight new things to put runes into.

Some of them are genuinely useful.

Season 15 Is Not Just a Ladder Reset

Season 15 began on August 22 in Europe, resetting the Ladder economy and moving Season 14 characters into their respective Non-Ladder groups.

We already covered the full Diablo II Season 15 launch schedule and rollover rules, but Patch 3.3 contains several changes that matter after your Ladder character has stopped being a Ladder character.

The biggest is Blizzard's decision to release an entire batch of seasonal Rune Words into Non-Ladder.

This is important because merely owning one of these items on Non-Ladder was never quite the same thing as being able to create one there.

Older Ladder characters eventually move to Non-Ladder with their equipment intact.

That means Ladder-made Rune Words can gradually enter the permanent economy.

But if the recipe itself remains Ladder-only, a Non-Ladder player cannot simply find a suitable base, collect the runes and make another one.

Season 15 removes that restriction for these eight.

Cure Is Probably the Biggest Winner

If there is one Rune Word many Non-Ladder players will immediately care about, it is Cure.

Cure was introduced alongside several resistance-focused helmet Rune Words and became especially useful on mercenaries.

Its defining feature is the Level 1 Cleansing Aura when equipped.

That aura reduces the duration of poison and curses affecting nearby characters.

Combined with Poison Resistance and Poison Length Reduced, it can make Cure an extremely practical mercenary helmet in areas where poison or curses become irritating.

And because it uses relatively accessible runes compared with the truly expensive endgame recipes, it is not something reserved exclusively for players with a small national treasury sitting in their stash.

For Non-Ladder players who have been keeping suitable helmet bases around, Season 15 gives those bases a new purpose.

Bulwark Is Another Excellent Mercenary Option

Bulwark belongs to the same family of helmet Rune Words.

Instead of specialising in an elemental resistance, it focuses on physical durability.

It provides Faster Hit Recovery, life steal, Vitality, enhanced defense and physical damage reduction.

That makes it particularly attractive for mercenaries who need to survive long enough to continue doing their actual job.

Which is normally:

Stand slightly too close to something horrifying.

Get hit repeatedly.

Occasionally remember that they have an aura.

Non-Ladder characters now have another relatively affordable option between basic leveling equipment and extremely expensive endgame mercenary helmets.

Ground, Hearth and Temper Are the Resistance Trio

Three more Rune Words solve very specific problems.

Ground focuses on Lightning Resistance and Lightning Absorb.

Hearth focuses on Cold Resistance and Cold Absorb, while also providing Cannot Be Frozen.

Temper provides Fire Resistance and Fire Absorb.

All three were originally part of Blizzard's response to the introduction of Sunder Charms.

Sundering an immunity does not magically make resistance management disappear.

Quite the opposite.

If your character suddenly becomes vulnerable to the element they are designed around, stacking enough resistance to compensate becomes very important.

That makes these helmets situational rather than universally best-in-slot.

But Diablo II has always been a game where having the right situational item sitting in your stash can turn an awful encounter into something manageable.

Season 15 now lets Non-Ladder players craft those answers directly.

Metamorphosis Is the Interesting One for Druids

Metamorphosis is considerably more specialised.

The helmet Rune Word was created specifically for Shape Shifting Druids and rewards players for using both Werewolf and Werebear forms.

Werewolf attacks can grant Mark of the Wolf, while Werebear attacks grant Mark of the Bear.

The bonuses include increased maximum life, attack speed, physical damage reduction and Crushing Blow alongside +5 to Shape Shifting Skills.

Blizzard originally described Metamorphosis as an attempt to create another serious endgame option alongside helmets such as Jalal's Mane.

It is not a cheap experimental Rune Word either.

The recipe includes a Cham rune.

So before putting one together because you can finally craft it on Non-Ladder, it is probably worth confirming that your Druid actually wants it.

Diablo II remains very good at transforming excitement into rune-economy anxiety.

Mania and Hysteria Join Non-Ladder Too

The list also includes Mania and Hysteria, which remained among the newer Ladder-exclusive options before Patch 3.3.

The important Season 15 change is not that these Rune Words have been redesigned.

It is that their seasonal exclusivity has ended.

Non-Ladder players can finally incorporate them into permanent character planning rather than relying on Ladder rollover to bring finished examples into the economy.

That distinction is particularly relevant for players who treat Non-Ladder as Diablo II's real long-term endgame.

Those characters may have existed for years.

Their stashes are terrifying archaeological sites.

And some of those forgotten bases may suddenly be useful again.

This Does Not Mean Every Season 15 Item Change Is Available on Non-Ladder

There is an important catch.

Patch 3.3 also modifies a number of existing Unique and Set items.

Those newly changed versions remain Ladder-only under Reign of the Warlock.

For example, Season 15 changes include:

Bloodletter gaining 20% Faster Run/Walk
The Battlebranch receiving a lower item and character level requirement
Rogue's Bow gaining +1-3 to Cold Arrow or Fire Arrow
Pluckeye receiving 25% Increased Attack Speed
Bane Ash being redesigned toward Faster Cast Rate
Gravenspine gaining Faster Cast Rate
Blinkbat's Form receiving more Faster Run/Walk and Mana After Each Kill
The Ward gaining a socket
Manald Heal receiving Faster Cast Rate
Angelic Raiment receiving several set bonuses

Those redesigned versions are part of the new Ladder environment rather than an immediate Non-Ladder update.

So Season 15 effectively creates two different item stories.

Older Ladder Rune Words are moving outward.

Newly reworked items are staying on Ladder for now.

It Is Easy to Misread Blizzard's Patch Notes

The wording caused some confusion almost immediately.

One player on Blizzard's forums asked why the seasonal Rune Words had not appeared in their Lord of Destruction setup after reading that previous Ladder-only items would become available in Non-Ladder.

The important context is that Patch 3.3's new item progression belongs to Reign of the Warlock.

Blizzard specifically notes that the new item changes do not alter Diablo II Classic or the older Lord of Destruction ruleset.

So if you are playing the current Reign of the Warlock era, the new Non-Ladder access is relevant.

If you deliberately remain inside an older era, do not assume every modern item rule automatically travels backward with you.

Diablo II now has timelines.

Apparently we needed those.

Season 15 Also Changed Sunder Farming

The Rune Word rotation is only one of several reasons Non-Ladder and permanent-character players should pay attention to Patch 3.3.

Blizzard also changed how Latent Sunder Charms are farmed in Season 15.

Magic Find-based Sunders are now rarer, require Hell difficulty and have a higher minimum drop level.

Meanwhile, the special Sunder chance attached to Heralds remains unchanged.

Those changes make Rune Words such as Ground, Hearth and Temper particularly relevant again because elemental resistance management remains closely tied to Sunder-based builds.

Blizzard created those Rune Words to help solve exactly that problem.

Non-Ladder can now craft them directly.

Your Old Non-Ladder Stash May Be Worth Checking

This is therefore one of those patches where the first thing a veteran player should do is not necessarily create another character.

Open the stash.

Look through the helmet bases you have been hoarding since an election cycle nobody remembers.

Check the runes.

See whether that Druid finally has a reason to make Metamorphosis.

Consider Cure or Bulwark for a mercenary.

Keep Ground, Hearth and Temper in mind when solving specific resistance problems.

The joy of Non-Ladder is that nothing really disappears.

Characters accumulate.

Items accumulate.

Plans accumulate.

Eventually Blizzard changes one line in the patch notes and a base you refused to throw away three years ago becomes useful.

This is why Diablo II players never clean their stashes.

We were right all along.

Sources

Blizzard: Diablo II: Resurrected Ladder Season 15 and Patch 3.3

Blizzard: Patch 2.6 Rune Words

Diablo II Forums: Patch 3.3 Non-Ladder and Lord of Destruction clarification

Blizzard: Reign of the Warlock Patch 3.1.1

```

Diablo 4 Players Say Transfiguration Can Turn a Dream 4GA Drop Into a Nightmare

2026-08-22T02:51:53.596-07:00

There are few better moments in Diablo 4 than seeing four little stars sitting next to an item.

A 4 Greater Affix drop should be the sort of thing that makes you stop whatever you are doing, inspect the item three times and immediately consider reorganising your entire build around it.

Then you put it into the Horadric Cube.

One click later, it can become Unmodifiable.

And if the Transfiguration roll is bad?

Congratulations.

You still own an extraordinarily rare item.

You just may not particularly want to use it anymore.

A lively Diablo 4 community discussion this week has reignited criticism of the game's Transfiguration system after a player transformed a 4GA item and ended up unhappy with the permanently locked result.

The incident is not necessarily a bug.

In fact, that is precisely what makes the debate interesting.

Transfiguration is designed as a high-risk final crafting step.

Some players think that gamble gives endgame gearing tension.

Others think Diablo 4 has reached the point where obtaining a nearly perfect item is no longer exciting, because the Cube is waiting at the end with a slot machine and a padlock.

A 4GA Item Can Still Lose the Most Important Roll

The latest discussion began on August 18 with a wonderfully concise forum post:

“Ummm….why unmodifiable.”

The player had Transfigured a 4GA item and discovered the problem that experienced endgame players already know very well.

Greater Affixes are only part of the equation now.

A powerful Transfiguration result can add enough value that an otherwise less impressive item may outperform something covered in GA stars.

Conversely, a beautiful 3GA or 4GA drop can receive an undesirable Transfiguration result and immediately become much less appealing.

And because the item may become Unmodifiable after Transfiguration, you cannot simply walk back to the Cube and keep rerolling until the universe apologises.

The gamble is the point.

Whether the gamble is good design is another matter entirely.

What Does Transfiguration Actually Do?

Transfiguration is one of Diablo 4's endgame Horadric Cube systems.

Once you have prepared an item through the usual crafting steps, you can use Cube materials to Transfigure it and potentially gain another powerful modification.

The possible outcomes can be excellent.

They can increase Item Quality.

Add useful offensive or defensive properties.

Create combinations that push a build considerably beyond what the original drop could provide.

But Transfiguration comes with an important risk:

the item can become Unmodifiable.

That means Transfiguration is supposed to happen at the end of the crafting process.

Sockets first.

Tempering.

Enchanting.

Aspect.

Masterworking.

Then you visit the Cube and ask whether everything you just spent time creating would like to participate in a small gambling problem.

Blizzard Is Explicitly Designing Around “Unmodifiable” Items

This is not some accidental hidden mechanic that Blizzard has forgotten exists.

The upcoming Season 15 changes actually make the consequences even clearer.

Blizzard is changing Mythic Unique crafting so that the Horadric Cube can perform a direct 1:1 conversion of an existing item into a Mythic version, retaining its affixes, Tempering and Masterworking.

There is one major restriction.

You cannot use an Unmodifiable item.

Blizzard's own Season 15 PTR notes specifically warn players to be careful about Transfiguring a valuable item they intend to convert into a Mythic later.

That makes the crafting order increasingly important.

The Cube is not merely another upgrade station.

It contains decisions that can permanently close other crafting doors.

Some Players Think That Is Exactly How Endgame Crafting Should Work

Not everyone dislikes the system.

Several responses to the 4GA discussion make essentially the same argument:

You knew the risk.

Transfiguration is gambling.

If every perfect item could simply be rerolled indefinitely until it received the perfect Transfiguration, then there would eventually be very little tension left in endgame gearing.

That argument has some merit.

ARPGs live on imperfect items.

If every desirable stat can eventually be forced onto every item, loot stops being loot and becomes a checklist.

Finding another 4GA item matters precisely because the first one was not guaranteed to become mathematically perfect.

A genuinely perfect item should be extraordinary.

The question is how many separate lotteries an item needs to win before players are allowed to enjoy it.

A 4GA Drop Already Won One Extremely Large Lottery

This is where the opposing argument becomes compelling.

Getting a useful 4GA item is already rare.

Not merely four Greater Affixes.

Four Greater Affixes on the correct item, with the correct stats, for the build you actually play.

That is an important distinction.

A 4GA item with four irrelevant stats is an impressive museum exhibit.

A 4GA item with exactly what your build wants is something else entirely.

Then come Tempering and Masterworking.

Then potentially a Kullean Transfiguration.

Then the final Transfiguration.

Each system adds another opportunity to improve the item.

It also adds another opportunity for the item to stop being exciting.

That is why some players argue the current system has inverted the emotional structure of loot hunting.

Seeing a 4GA item should produce excitement.

Instead, experienced players increasingly see it as a promising crafting base that has not yet survived the dangerous part.

Players Are Saying the Cube Matters More Than the Stars

This complaint has been appearing throughout Season 14.

In another recent discussion about Diablo 4's itemisation, players argued that a strong Transfiguration roll can be more important than multiple Greater Affixes.

One player summed up the problem by questioning why they should care about finding a 3GA or 4GA weapon if a zero-GA item can ultimately become stronger through a lucky Cube result.

That is not necessarily mathematically true for every slot or every build.

But the perception matters.

Greater Affixes are Diablo 4's most immediately recognisable loot jackpot.

The stars tell you:

This item is special.

If the eventual fate of that item depends more heavily on a later random crafting result, the dopamine starts moving away from monster drops and toward the crafting interface.

For an ARPG, that is a dangerous migration.

There Are Also Reports of Transfiguration Producing No Visible Reward

The current debate becomes messier because there are separate reports that may actually involve bugs.

One player reported taking a near-perfect Ancestral Legendary amulet through Enchanting, Greater Affixes, Tempering, Masterworking and a Kullean Transfiguration before performing the final normal Transfiguration.

The result?

The item became Unmodifiable, but the player could not identify any new Transfiguration effect.

No visible new affix.

No apparent Item Quality increase.

No Greater Affix improvement.

Just the Unmodifiable tag.

That case has been filed separately as a bug report and should not be confused with simply receiving an undesirable intended roll.

But emotionally the outcome is remarkably similar.

Hours of gearing go into the Cube.

The Cube hands the item back.

The player quietly considers taking up gardening.

Players Want More Control — But Not Necessarily Guaranteed Perfection

Several alternatives are being proposed.

One suggestion is allowing Transfiguration to work more like Enchanting.

Instead of permanently locking the item, players could Transfigure again, replacing the previous result at an increasingly expensive material cost.

Another suggestion would give especially rare items additional protection.

A 4GA item might receive two Transfiguration opportunities.

Or players could choose from several potential results rather than accepting one completely random outcome.

Others want the current gambling system preserved but the Unmodifiable restriction reduced, allowing mundane actions such as adding sockets after Transfiguration even if the Transfiguration result itself remains permanently locked.

That particular complaint has already appeared in Season 15 PTR feedback.

Players accept that the final Cube roll should carry risk.

They are less enthusiastic about discovering they forgot one crafting step and therefore transformed their dream item into an extremely expensive paperweight.

Season 15 May Make the Decision Even More Dangerous

The upcoming Mythic crafting changes give this entire debate more urgency.

Season 15's direct Mythic conversion is designed specifically to reward players who find and carefully build an excellent item.

You will be able to take an item with desirable affixes, Tempering and Masterworking and convert that exact foundation into Mythic quality without rerolling everything.

That sounds fantastic.

But an Unmodifiable item cannot use the recipe.

So a player who receives a dream item now faces an increasingly complicated optimisation puzzle.

Do you Transfigure it now?

Do you preserve it for Mythic conversion?

Do you wait for another copy?

Do you gamble the 4GA?

Do you use the safe item and throw backup copies into the Cube?

At some point Diablo 4 gearing stops resembling blacksmithing and begins resembling portfolio management.

This Connects to Diablo 4’s Bigger Endgame Balance Problem

The Transfiguration debate also connects to the enormous performance gaps between endgame builds.

We recently looked at how Diablo 4's Tower scaling can turn a relatively small tier difference into an enormous effective power gap.

At that level, marginal upgrades stop being marginal.

One additional multiplier or unusually strong Transfiguration can translate into several more Tower tiers.

That creates tremendous pressure to chase perfect Cube results.

And Season 15 is already producing builds with numbers so extreme that PTR Warlocks have reportedly reached damage numbers measured in tens of quadrillions.

When the top end scales that aggressively, leaving power on the table because your 4GA item received a poor Transfiguration does not feel like a minor imperfection.

It can feel like the item failed.

The Best Drop in Diablo 4 Should Probably Feel Good Before the Cube

This is ultimately the part Blizzard needs to get right.

Diablo 4 absolutely needs long-term item hunts.

Perfect gear should be rare.

Players should have reasons to keep killing monsters after they already possess a strong build.

And a little risk can make crafting exciting.

But the order matters.

A monster drops a 4GA item.

The player should be thrilled.

If their immediate reaction is instead:

Nice. Now let's see whether the Cube ruins it.

Then the most exciting part of an ARPG may be happening in the wrong place.

Transfiguration does not necessarily need to become completely safe.

It probably should not.

But there may be room between guaranteed perfection and permanently locking one of the rarest drops you have seen all season behind a bad roll.

A 4GA item should feel like winning the lottery.

Right now, for some Diablo 4 players, it feels like winning a ticket to another lottery.

Sources

Diablo IV Forums: Transfigure bricked my 4GA

Diablo IV Forums: Transfiguration Bricked My Near-Perfect Amulet With No Result Added

Diablo IV Forums: Current Transfiguration Is Not Good for Overall Game Health

Diablo IV Forums: Transfiguration PTR Feedback

Blizzard: Diablo IV 3.2.0 PTR — What You Need to Know

```

Diablo 2 Season 15 Just Changed the Best Way to Farm Sunder Charms

2026-08-22T02:37:56.878-07:00

Diablo II players love Magic Find.

More Magic Find means more shiny things.

That has been one of Sanctuary's most dependable laws for roughly a quarter of a century.

Season 15 has now added an asterisk.

Patch 3.3 makes several important changes to Latent Sunder Charms, including reducing how strongly Magic Find helps them drop and completely removing Magic Find-based Sunder drops from Nightmare difficulty.

At the same time, Blizzard specifically says the special Sunder drop chance from Heralds is unaffected.

The practical result is fairly clear.

If your primary goal in Season 15 is finding Sunder Charms, blindly stacking Magic Find and hoping ordinary monsters eventually cough one up is less attractive than it was.

Herald hunting just became relatively much more important.

Welcome to Diablo II, where even farming strategies occasionally require patch-note archaeology.

Season 15 Made Three Major Changes to Sunder Drops

Patch 3.3 arrived just before Diablo II: Resurrected Ladder Season 15 began, and buried among its item changes are three lines that significantly alter Sunder farming.

First, Blizzard increased the minimum drop level for Latent Sunder Charms from 69 to 75.

Second, Blizzard reduced the drop rate of Latent Sunder Charms obtained through Magic Find.

Third, Magic Find-based Latent Sunder Charms now drop only in Hell difficulty.

That last change is particularly important.

During the previous system, players could potentially obtain Latent Sunder Charms before reaching Hell.

Season 15 shuts that door.

If you want Sunders through the regular Magic Find loot pool, Hell is now the starting line.

Magic Find Still Works — Just Less Effectively

There is already some confusion around this part.

Blizzard did not say that Magic Find makes Sunder Charms less likely to drop as your MF increases.

Nor did Blizzard remove Sunders from the regular loot pool.

The patch notes say the drop rate of Latent Sunder Charms when using Magic Find has been reduced.

So Magic Find remains part of the normal Sunder system.

It is simply not as powerful a Sunder-farming lever as it was before Patch 3.3.

That distinction matters because some players are already experimenting with everything from zero to several hundred percent Magic Find and wondering whether they have accidentally made their odds worse.

There is currently no indication from Blizzard that higher Magic Find actively penalises your Sunder chance.

The entire Magic Find route has simply been toned down.

Herald Sunder Drops Were Not Nerfed

This is probably the most important sentence in Blizzard's Patch 3.3 notes:

“Note the Herald drop rate is unaffected.”

Heralds use a special increased chance to drop Latent Sunder Charms that exists separately from the ordinary Magic Find loot pool.

That system has already been reworked several times during Reign of the Warlock.

Blizzard previously lowered the Herald tier at which the increased Sunder chance begins and removed player-count scaling from that special chance, specifically improving the situation for solo players.

Higher-tier Heralds receive stronger increased Sunder chances.

Patch 3.3 does not reduce that special Herald chance.

Which means Blizzard has effectively weakened one route to Sunders while leaving the dedicated Herald route alone.

If the game is trying to communicate something, it may be:

Please fight the enormous angry monsters we added.

Players Are Already Wondering Whether Heralds Were Secretly Nerfed

Naturally, Diablo II players have begun doing what Diablo II players do whenever an item fails to drop.

Assume Blizzard changed something.

A current forum discussion includes players reporting extremely long dry streaks while hunting high-tier Heralds, including one player who says they spent several days farming without seeing a single Sunder.

That led to questions about whether Patch 3.3 had quietly reduced Herald Sunder rates as well.

According to Blizzard's published notes, it did not.

The special Herald drop chance is explicitly described as unaffected.

And this is where Diablo II probability becomes emotionally difficult.

A drop chance can remain exactly the same.

You can still kill fifty Heralds.

You can still get nothing.

Randomness does not care how strongly you feel that number 47 should have been the one.

Player Count Doesn't Improve the Special Herald Sunder Roll

There is another useful detail for Season 15 farming.

Stacking a game with more players is not necessary if your only concern is the Herald's special Sunder chance.

Blizzard previously removed player-count scaling from that increased Herald Sunder chance.

That was specifically intended as a buff for solo players.

Higher player counts can still affect ordinary Diablo II loot systems and may make the rest of your farming more rewarding.

But joining an eight-player game purely because you expect the Herald's dedicated Sunder roll to become dramatically better is no longer the strategy it once appeared to be.

This also explains some of the current confusion.

Players are experimenting with both Magic Find and large parties while farming Heralds.

Neither variable directly improves that special Herald Sunder roll.

The main thing that matters is finding Heralds and, ideally, reaching the higher tiers.

High-Tier Heralds Are Still the Target

Not all Heralds are equally valuable when hunting Sunders.

Earlier Reign of the Warlock updates increased the dedicated Sunder chance as Heralds climb through their tiers.

Tier 3 and Tier 4 Heralds receive a substantially better increased chance, while Tier 5 Heralds have the strongest dedicated Sunder opportunity.

That means a dedicated Season 15 strategy should focus less on simply maximising Magic Find and more on maximising the number of meaningful Herald encounters you can generate.

Stay active inside Terrorized Zones.

Kill enough monsters to push Herald appearances.

Prioritise zones where your build can clear efficiently.

And do not assume that fighting the strongest possible Herald in an eight-player game is automatically better than efficiently killing them solo.

The best farming build remains the one that spends more time killing monsters than staring at the resurrection screen.

Nightmare Sunder Farming Is Over

This may be the most controversial Season 15 change for newer characters.

Latent Sunder Charms obtained through Magic Find now require Hell difficulty.

The minimum drop level also moved from 69 to 75.

That means players can no longer use Nightmare as an early opportunity to obtain a Sunder that helps solve Diablo II's famous immunity problem before seriously entering Hell.

Some players dislike that decision precisely because Sunders are build-enabling items.

A Fire build encountering Fire Immunes does not merely become slightly less efficient.

Sometimes the monster effectively becomes a roadblock with legs.

Sunder Charms were one answer to that old problem.

Season 15 now expects players to reach deeper into Hell before that answer becomes available.

Blizzard appears to want Sunders functioning as genuine endgame loot rather than something characters can acquire unusually early through Magic Find.

So What Is the Season 15 Sunder Farming Strategy?

If you are specifically farming Latent Sunder Charms in Season 15, the changes point toward a fairly straightforward strategy.

Farm in Hell. Magic Find-based Sunders no longer drop in Nightmare.
Do not abandon Magic Find. Regular monsters can still drop Latent Sunders through the normal MF system, but the rate has been reduced.
Actively hunt Heralds. Their special Sunder chance was not reduced by Patch 3.3.
Prioritise higher-tier Heralds. They provide the better dedicated Sunder opportunities.
Do not inflate player count solely for Herald Sunders. The special Herald roll is no longer improved by player count.
Farm efficiently. A fast Terror Zone your build handles comfortably will usually beat an theoretically optimal zone that takes forever to clear.

And perhaps most importantly:

Do not judge the system from one bad evening.

Diablo II drop rates have been ruining otherwise pleasant evenings since 2000.

Season 15 Is Pushing Players Toward Heralds

That appears to be the larger design direction behind the change.

When Reign of the Warlock first changed Sunder acquisition, Blizzard wanted to give players another route besides dedicated Herald hunting.

Latent Sunders were added to the regular Magic Find pool specifically so players did not feel forced to chase Heralds.

Now Blizzard is moving the needle back slightly.

Regular Magic Find can still produce Sunders.

But it is weaker.

Nightmare is gone from that equation.

Meanwhile, the Herald-specific chance survives untouched.

That does not make Herald farming guaranteed.

Far from it.

Players are already reporting painful dry streaks.

But Season 15 has made the intended hierarchy much clearer.

If a Sunder Charm happens to drop while you are farming ordinary Hell content, excellent.

If you are deliberately hunting one?

Start looking for Heralds.

Preferably Tier 5.

Then begin the traditional Diablo II ritual of killing the same thing repeatedly while slowly becoming convinced your installation is personally cursed.

Sources

Blizzard: Diablo II: Resurrected Ladder Season 15 and Patch 3.3

Blizzard: Season 14 Herald and Latent Sunder Charm changes

Diablo II Forums: Has Blizzard ruined Heralds of Terror Sunder drop rates?

Diablo II Forums: Season 15 Sunder level 75 discussion

```

Diablo 3 Console Players Can’t Progress the Altar of Rites Because Challenge Rifts Are Broken

2026-08-22T02:28:25.980-07:00

Diablo III players have killed Diablo.

They have killed Malthael.

They have cleared Greater Rifts in which ordinary mathematics stopped being useful several years ago.

Right now, however, some console players are being defeated by something considerably more dangerous.

A missing weekly Challenge Rift.

Players on Xbox, PlayStation and Nintendo Switch have been reporting that Diablo III's Challenge Rift rotation is stuck on Challenge Rift 476, preventing them from accessing the newer weekly Challenges.

Challenge Rift 477 failed to appear correctly.

Challenge Rift 478 has now arrived on PC.

Console players are still waiting.

And because a Challenge Rift Cache is required to progress the Altar of Rites, this is not merely one weekly activity disappearing from the menu.

For players who do not already have a spare Cache, Season 39 progression can effectively stop at the altar.

Nothing says ancient demonic ritual quite like being defeated by the weekly-reset system.

Console Players Are Still Stuck on Challenge Rift 476

The first clear reports appeared on August 11 when an Xbox player noticed that Challenge Rift 477 had not become available.

Instead, the game continued displaying Challenge Rift 476.

Trying to enter it did not help.

The game simply reported:

“Challenge Rift 476 has ended.”

Nintendo Switch players quickly confirmed the same problem, followed by reports from PlayStation users.

By August 13, the issue was widespread enough that a Blizzard representative responded directly in the bug thread, confirming that the team was looking into it.

Unfortunately, the weekly calendar kept moving.

The consoles did not.

Challenge Rift 478 Didn't Fix It

Normally, a broken weekly rotation might solve itself when the next Challenge Rift arrives.

That does not appear to have happened here.

Challenge Rift 478 became available for PC players this week, complete with its wonderfully questionable Necromancer build and Season 39 Shadow Clones.

Console players remained stuck at 476.

A community Challenge Rift guide updated on August 18 specifically warned console users that the rotation was still frozen and that Challenge Rift 478 could not be played until Blizzard fixes the underlying problem.

Additional PlayStation reports were still appearing on August 18.

At this point, we have skipped past “one Challenge Rift failed to load” and entered “the calendar has left without us.”

The Altar of Rites Makes This Much Worse

If Challenge Rifts were merely a weekly side activity, this would be annoying rather than particularly serious.

The Altar of Rites changes that.

Blizzard permanently added the Altar to Diablo III after its original appearance in Season 28, allowing seasonal players to unlock a long progression tree of powerful bonuses by sacrificing specific items and materials.

The fifteenth sacrifice requires one very specific item:

A Challenge Rift Cache.

Normally, obtaining one is straightforward.

Complete the week's Challenge Rift faster than the original player's time and the game rewards a Cache containing crafting materials, Blood Shards and other useful resources.

But you cannot earn the weekly Cache if the weekly Challenge Rift does not exist on your platform.

Players who already stored an unused Cache can continue.

Anyone reaching that Altar requirement without one is stuck until the Challenge Rift system returns.

Players Are Literally Stopping at the Altar

That is exactly what console players are reporting.

By August 17, one player described having waited two weeks and said they could no longer progress through Season 39 because the Altar required the missing Cache.

Others reported returning to Diablo III after years away only to reach the same wall.

One player had apparently completed the previous Challenge Rift but never received its reward Cache, making the current outage even more frustrating.

Several affected players are now asking Blizzard to reconsider the Altar requirement entirely on consoles.

The suggestion is simple:

Replace the Challenge Rift Cache requirement with something that cannot disappear because the weekly rotation breaks.

A Bounty Cache has been suggested.

Or Blizzard could simply ensure Challenge Rifts continue working.

That would also be acceptable.

This Is Particularly Awkward in Season 39

Diablo III is currently running Season 39: Shades of the Nephalem, bringing back the Season 22 theme where activating Shrines and Pylons summons Shadow Clones that fight alongside the player.

It is exactly the sort of recycled seasonal setup that still gives older Diablo III players a reason to return for another run.

We have previously looked at why Diablo III remains surprisingly easy to return to in 2026: progression is quick, the seasonal systems are familiar and players can build something ridiculous without needing a three-week administrative onboarding process.

The Altar of Rites is a major part of that modern progression loop.

It gives returning players goals immediately.

Unlock a Seal.

Gain another account-wide seasonal bonus.

Work toward the next sacrifice.

Repeat until Sanctuary becomes considerably less threatening.

Unless sacrifice number 15 asks for an item the game currently refuses to let you earn.

Blizzard Knows About the Problem

There is at least one piece of good news.

This is not a bug currently disappearing unnoticed into an empty support forum.

On August 13, Blizzard's Marcooose responded directly to the main console bug report and said:

“Thanks for your report, team is looking into it.”

Blizzard said it would update the thread when more information became available.

As of the latest player reports we could verify, however, console users were still reporting the Challenge Rift rotation stuck at 476.

There is currently no published timetable for the fix.

Save a Challenge Rift Cache When This Is Fixed

There is also a useful lesson buried underneath the frustration.

Once Challenge Rifts return, seasonal players may want to keep one spare Challenge Rift Cache in their stash until the Altar has consumed its required Cache.

Normally that sounds unnecessarily cautious.

After the current outage, it sounds more like insurance.

Diablo III is fourteen years old and still running active seasons.

That is impressive.

But an older live game increasingly depends on a relatively small number of systems continuing to operate correctly.

When one weekly activity breaks, it can unexpectedly take another permanent system with it.

Console players do not need Blizzard to invent new Diablo III content here.

They would simply like Challenge Rift 478.

The demons are ready.

The Necromancer is ready.

The Altar is ready.

The menu apparently needs another minute.

Sources

Diablo III Forums: Challenge Rift 477 is not enabled for Xbox

Diablo III Forums: Season 39 Challenge Rift discussion

Blizzard: Altar of Rites requirements

Blizzard: Season 39 — Shades of the Nephalem

```

Diablo 2’s New Protector’s Stone Is Still Broken by a 20-Year-Old Damage Bug

2026-08-21T01:14:02.126-07:00

Diablo II: Resurrected has new classes.

New endgame encounters.

New Unique Jewels.

And apparently at least one bug old enough to remember dial-up internet.

Players are once again warning each other about Protector's Stone, one of the powerful Unique Jewels introduced with Reign of the Warlock.

The problem is not really Protector's Stone itself.

It is what happens when the jewel meets Diablo II's ancient interaction between Enhanced Damage and added minimum or maximum damage.

Socket Protector's Stone into the wrong piece of equipment and part of its attractive damage bonus may simply stop working correctly.

Patch 3.3 is now live ahead of Diablo II: Resurrected Ladder Season 15.

The old Enhanced Damage bug is still not among the listed fixes.

Twenty-five years of Diablo II development later, some traditions remain sacred.

Protector's Stone Looks Like an Amazing Physical Damage Jewel

Protector's Stone is one of the special rewards associated with the Colossal Ancients endgame encounter in Reign of the Warlock.

It can roll with:

1% Chance to cast Level 15 Fade when struck
+30-50% Enhanced Damage
Adds 10-30 Damage
-5-10% to Enemy Physical Resistance
+3-5% Experience Gained
15-35% Better Chance of Getting Magic Items
25-50% Extra Gold from Monsters

For physical builds, that is an unusually attractive collection of stats on a single socketable item.

Enhanced Damage.

Flat damage.

Enemy Physical Resistance reduction.

Magic Find.

Experience.

Gold.

It is basically a physical character asking Santa for a jewel and accidentally receiving the entire catalogue.

Unfortunately, two of those damage modifiers are exactly where Diablo II's old code starts becoming uncomfortable.

The Enhanced Damage Bug Has Been Around Since Original Diablo II

The problem is commonly known as the ED/min-max damage bug.

It affects jewels combining Enhanced Damage with added minimum or maximum physical damage when they are placed in non-weapon equipment.

Players have tested variations of the interaction for years.

The precise result depends on the combination of modifiers involved, but the important practical warning is simple:

Enhanced Damage on Protector's Stone does not behave correctly when the jewel is socketed into armor, helmets or shields.

A lengthy bug report on Blizzard's forums specifically connects the legacy problem to Protector's Stone, with players continuing to bump the thread months after Reign of the Warlock launched.

Another player tested the jewel in non-weapon equipment and reported the same issue.

And another.

This is not exactly an undiscovered corner case.

Players Are Still Getting Caught by It

The most painful part is that Protector's Stone is valuable enough for players to build equipment decisions around it.

On August 5, one player reported buying an expensive version of the jewel and placing it into Arreat's Face.

They then discovered that the damage interaction did not work as expected.

The response from other players was essentially:

Yes.

That bug.

Still.

Another player asking about placing Protector's Stone into Guillaume's Face was advised in July not to do so because the Enhanced Damage portion would not work correctly there.

The result is an especially strange situation for a newly introduced chase item.

Blizzard created a powerful physical-damage jewel in 2026.

Players then have to consult knowledge accumulated from original Diablo II to determine where it can safely be socketed.

Weapons Are Currently the Safer Choice

If you have a good Protector's Stone, the current community advice is generally to use it in a weapon if your build allows it.

The long-standing Enhanced Damage interaction does not produce the same problem there.

That severely limits the jewel's flexibility, however.

A physical build may already depend on specific weapon sockets for Shael runes, attack-speed jewels, runes, damage setups or other requirements.

Helmets and armor would otherwise be obvious homes for Protector's Stone.

Something like Arreat's Face or Guillaume's Face immediately comes to mind.

Except Diablo II remembers a bug from approximately the Bronze Age and objects.

There have also been separate reports involving Protector's Stone interacting strangely with native weapon damage values, meaning the jewel has generated more than one damage-calculation discussion since release.

For an item designed to make physical damage easier, it has generated an impressive amount of mathematics.

Patch 3.3 Fixed Plenty of Other Things

The timing is what makes the issue particularly noticeable again.

Blizzard has just released Patch 3.3 ahead of Season 15.

The update contains numerous bug fixes and balance adjustments.

Warlock received another round of changes.

Blizzard fixed the collision problem that had players arguing that Abyss Warlock had become dramatically stronger.

The studio also adjusted the Reign of the Warlock economy, including changes to Worldstone Shard and Ancient Statue drops.

Several old items received balance changes.

Skills were fixed.

Controller interactions were fixed.

Terror Zones were adjusted.

But the Enhanced Damage/min-max interaction is not listed among the Patch 3.3 fixes.

Players noticed.

The forum thread accompanying Blizzard's Season 15 announcement almost immediately included another complaint that the ED bug remained unaddressed.

Why Hasn't Blizzard Just Fixed It?

That is the obvious question.

It is also difficult to answer from outside Blizzard.

A bug surviving for decades does not necessarily mean the fix itself is simple.

Diablo II's physical damage calculation touches weapons, off-weapon Enhanced Damage, character skills, auras, minimum damage, maximum damage, jewels and various equipment modifiers accumulated across decades of game development.

Changing an old interaction can create new problems elsewhere.

And Diablo II players are extremely good at discovering those problems.

Usually within seventeen minutes.

Still, Protector's Stone changes the argument somewhat.

This is no longer merely an obscure legacy interaction involving rare old jewels.

Blizzard introduced a brand-new endgame reward that deliberately combines Enhanced Damage and flat physical damage on the same jewel.

That puts the old bug directly in front of players again.

A New Item Shouldn't Require a 20-Year-Old Warning Label

That is ultimately why players keep bringing this one back.

Protector's Stone is not a forgotten item from Lord of Destruction.

It belongs to Diablo II's new era.

Reign of the Warlock represents Blizzard doing something extraordinary with this game: creating substantial new Diablo II content more than two decades after the original development ended.

We have already seen how that creates strange problems elsewhere, including the fact that the Warlock era cannot currently be played using Legacy Graphics because those original assets never existed.

Protector's Stone demonstrates the opposite problem.

The item is completely new.

The code underneath it is extremely old.

And somewhere between those two eras sits a physical-damage bug waiting for someone to socket an expensive jewel into a helmet.

Until Blizzard changes it, the safest advice remains remarkably old-fashioned:

Think very carefully before putting Protector's Stone anywhere except a weapon.

Diablo II may have entered a new era.

Its bugs occasionally decline the invitation.

Sources

Diablo II: Resurrected Forums: ED/Damage Jewel Bug

Diablo II: Resurrected Forums: ED Max Damage Jewel Bug

Diablo II: Resurrected Forums: Protector's Stone Enhanced Damage Not Applying

Diablo II: Resurrected Forums: Protector's Stone Weapon Damage Bug Report

Blizzard: Diablo II: Resurrected Ladder Season 15 and Patch 3.3

```

Diablo 4’s Warlock Is Hitting for 80,000 Trillion Damage on the Season 15 PTR

2026-08-21T00:53:40.525-07:00

Diablo 4 damage numbers have officially reached the point where commas are becoming a gameplay mechanic.

Players testing the Season 15 PTR have reported Warlock builds hitting for as much as 80,000 trillion damage.

That is 80 quadrillion.

And before anyone starts deleting their current build, there is an important qualification:

These are PTR numbers.

They are being generated inside a test environment specifically designed to expose broken interactions before Season 15 goes live.

Judging by the numbers, that part appears to be working beautifully.

Blazing Scream Has Reportedly Reached 80,000T

The discussion started during Blizzard's 3.2.0 PTR, which ran from August 4 through August 11.

Warlock players quickly noticed that several Hellfire builds were performing far beyond the rest of the class.

One detailed PTR feedback thread reported Apocalypse hits around 12,000T.

That was already substantial.

Then players started testing Blazing Scream.

According to the reports, Blazing Scream builds were clearing Pit 150 relatively easily, with one reported hit reaching approximately 80,000T.

At that point we are no longer balancing numbers.

We are balancing telephone numbers.

Season 15 Gave Blazing Scream Some Very Serious Toys

The damage did not appear from nowhere.

Blizzard made several significant Warlock changes for the 3.2.0 PTR.

One of the biggest involves Elegy.

The Unique now turns Blazing Scream into an Archfiend Skill while granting it 30-50% increased damage.

It also gives Blazing Scream the Skull Splitter Variant for free, with Lesser Demon skulls dealing the same damage as the main skull.

Then there is The Eightfold Idol.

Blazing Scream can leave Sigil of Subversion trails behind, while enemies standing on the appropriate trail take another 60-80% increased Abyss or Hellfire Skill damage.

That is already a healthy collection of multipliers.

Season 15 then adds another layer through Soul Splinters.

Soul Splinters Are Making the Situation Even Stranger

The new Soul Splinter system is one of Season 15's major mechanics.

Several Splinters provide enormous bonuses alongside equally substantial drawbacks.

The most suspicious interaction during PTR testing involved the Splinter of the Black Soulstone.

Its intended effect is straightforward.

Killing enemies temporarily absorbs their souls, with each soul increasing your damage while also increasing the damage you take.

The highest version grants 5% multiplicative damage per soul.

That stacks.

And during the PTR, Warlock players discovered something slightly unfortunate.

The deaths of the Warlock's own demons appeared to count as enemy kills.

A player testing Blazing Scream reported being able to rapidly generate around 200 stacks without actually killing monsters.

That makes evaluating the true strength of the build considerably more difficult.

If a seasonal effect designed around killing enemies is also rewarding you whenever your disposable demons disappear, the damage meter is going to become ambitious very quickly.

It May Not Just Be the Seasonal Mechanic

The community feedback does not blame everything on Soul Splinters.

Players have also highlighted Overwhelming Aspect.

Its Season 15 version increases Occult Skill damage against Elite enemies for each stack of Overpower, with the bonus doubled against Hexed targets.

That creates another potentially enormous multiplier when combined with the rest of the Warlock's scaling.

Players have additionally pointed toward Moloch's Beating Flame as another contributor to the extreme Hellfire numbers.

The important distinction is that several things appear to be stacking together.

This may not be a single broken skill.

It may be a collection of individually powerful effects discovering each other.

Which is generally how Diablo builds become either extremely fun or extremely unemployed after the next patch.

The Bigger Problem Is Warlock Balance Within the Class

The funny part is that players asking Blizzard to reduce these numbers are often Warlock players themselves.

Their concern is not simply that the class is too powerful.

It is that Hellfire builds appear dramatically stronger than other Warlock archetypes.

One PTR discussion claims that Hellfire setups were already clearing beyond Tier 140 before the new seasonal systems arrived, while some Abyss builds struggled around 120.

Season 15 then appears to widen that gap.

That connects directly to the broader problem we recently looked at with Diablo 4's extreme endgame scaling.

A difference of twenty or thirty tiers does not represent a small balance discrepancy once monster health begins scaling exponentially.

It can represent orders of magnitude.

So when one Warlock build casually reaches Pit 150 and another archetype struggles dozens of tiers lower, simply saying both are technically viable does not tell the whole story.

Players Don’t Want Blizzard to Nerf the Wrong Thing

This is where the feedback becomes more nuanced.

Several players are worried Blizzard will see the enormous PTR numbers and simply nerf Warlock.

They would rather Blizzard identify which Season 15 interactions are actually causing the extreme scaling.

That distinction matters.

If Blazing Scream becomes absurd because a seasonal Soul Splinter is incorrectly treating friendly demon deaths as enemy kills, nerfing Blazing Scream itself could leave the build unnecessarily weak once the seasonal bug disappears.

The same applies to interactions involving individual Aspects or unusual multiplier stacking.

The PTR exists specifically so Blizzard can separate those problems before the patch reaches live servers.

Blizzard has explicitly said that feedback from the 3.2.0 PTR will be used to adjust balance and remove bugs before Season 15 launches.

So an 80,000T Warlock is not necessarily a preview of what players will be doing all season.

It is closer to an extremely enthusiastic bug report.

Season 15 Warlock Is Probably Not Shipping Like This

That is the important takeaway.

Do not build your entire Season 15 plan around dealing 80 quadrillion damage.

Blizzard still has time to change coefficients, fix Soul Splinter interactions and adjust individual Warlock items before the season goes live.

And considering players are actively asking Blizzard to investigate the build, there is a very good chance something changes.

But the PTR has already demonstrated one thing.

Diablo 4's multiplication problem is alive and well.

We recently reached the point where players struggle to see what is killing them.

Now we may also be approaching the point where they struggle to read what they are killing things with.

80,000 trillion.

Season 15 hasn't even started yet.

The calculator is already sweating.

Sources

Diablo IV Forums: Warlock Balance Feedback — Overperforming Hellfire Builds

Diablo IV Forums: Season 15 Class Balance Discussion

Diablo IV Forums: Season 15 PTR Feedback Summary

Blizzard: The 3.2.0 PTR — What You Need to Know

```

Diablo 4 Players Say the Real Problem With One-Shots Is That You Can’t See Them

2026-08-21T00:46:53.471-07:00

Diablo 4 has swords falling from the sky.

It has poison pools.

Earthquakes.

Fire chains.

Exploding monsters.

Player spells covering half the screen.

And somewhere underneath all of that is apparently the attack that just killed you.

A new Diablo 4 community discussion has once again turned toward the game's notorious falling swords, but players are increasingly arguing that the swords themselves are not the real problem.

The problem is visual clarity.

Diablo 4 can throw so many overlapping enemy mechanics, death effects and player abilities onto the battlefield that avoiding dangerous attacks sometimes becomes less about recognising the mechanic and more about successfully locating it underneath the fireworks.

The sword is dangerous.

The poison puddle is dangerous.

The earthquake is dangerous.

The real boss fight is identifying which shade of red is currently trying to murder you.

Players Are Still Complaining About the Falling Swords

The latest discussion appeared on Blizzard's Diablo IV forums on August 17.

The original topic revisits one of Diablo 4's more controversial ways of keeping players moving: swords that appear above the character, follow them briefly and then slam into the ground for heavy damage.

Players have complained about the mechanic for months, particularly in higher difficulties and Hardcore.

One Hardcore player described the swords earlier this year as more frightening than connection problems after losing a character when several of them appeared while other environmental hazards restricted movement.

The mechanic itself can be avoided.

The swords follow the player briefly before committing to their landing position, meaning continued movement gives you a chance to escape the impact.

One player in the new discussion even says the timing feels more generous this season, with a longer delay between the sword stopping and actually falling.

That observation has not been documented as an official Blizzard change, but it highlights something important.

If you can clearly see the sword, you can react to it.

That is where things begin falling apart.

The Sword Is Not Alone

One response in the current discussion neatly describes the actual problem.

Imagine a falling sword appearing inside a poison pool.

Now add an earthquake.

Then cover the same area in giant fire chains and player spell effects.

The game has technically communicated every individual mechanic.

The player can technically respond to all of them.

Visually, however, the battlefield has become soup.

That matters because Diablo 4 increasingly relies on reactive mechanics to threaten powerful endgame characters.

If enemies simply deal slightly more ordinary attack damage, highly defensive builds may ignore them entirely.

So the game uses ground effects, explosions, delayed attacks, projectiles and other mechanics that demand movement.

In isolation, that is good combat design.

You see danger.

You react.

You survive.

The problem begins when six pieces of good combat design happen in exactly the same square metre.

Monster Density Makes Everything Harder to Read

Modern Diablo is built around density.

Players want large packs.

They want abilities hitting twenty enemies simultaneously.

They want screens full of demons exploding into gold, materials and increasingly complicated equipment.

Low-density ARPG combat tends to feel slow.

But density also multiplies every mechanic attached to those monsters.

If one enemy can leave something dangerous behind when it dies, that is manageable.

If ten of them die simultaneously, the floor becomes an insurance claim.

The current forum discussion specifically points toward the number of on-death mechanics as part of the problem.

Killing the enemy does not necessarily remove the threat.

Sometimes it creates the threat.

That also produces a strange reversal of normal ARPG logic.

Your character becomes more powerful.

You kill the pack faster.

The entire pack triggers its effects simultaneously.

Congratulations on your improved DPS.

Please evacuate the postcode.

Realmbreakers Are Creating Similar Complaints

The falling-sword discussion is not happening in isolation.

A separate forum thread posted on August 18 complains about Realmbreakers apparently killing players from long range before they realise what is attacking them.

The discussion quickly moves toward their damaging ground pools.

One player argues that the pools can begin dealing damage without enough warning and suggests giving them a clearly visible outline before the damaging area appears.

That would be a relatively simple principle:

show the danger before applying the damage.

Diablo 4 already does this successfully with plenty of mechanics.

The Blood Maiden's attacks, major boss mechanics and many elite abilities give players a visual window to react.

The frustration comes from situations where the warning is too subtle, arrives too late or disappears underneath everything else happening on screen.

One-Shots Feel Worse When You Don't Know What Killed You

There is another part of this problem that Diablo 4 still handles poorly.

Death information.

If the player gets flattened by an obviously telegraphed boss attack, the lesson is straightforward.

Do not stand there next time.

If the screen explodes and the game simply reports that your character “was slain”, there is very little to learn.

Was it poison?

Physical damage?

An on-death explosion?

A projectile?

Did your resistance fail?

Was your armor too low?

Did something hit you for twice your maximum life?

Good luck.

Several players in the latest discussion are asking for better death information, including a breakdown showing how much damage the killing blow dealt.

That would not prevent one-shots.

It would at least make them understandable.

There is a considerable difference between:

I died because my Poison Resistance is terrible.

And:

I died because Sanctuary briefly became red and then I wasn't alive anymore.

Turning Off Damage Numbers Apparently Helps

Players are already finding their own ways to reduce the noise.

One suggestion in the current discussion is simply turning off damage numbers.

That removes one entire layer of rapidly changing information from the battlefield.

Another player suggests Blizzard should provide an opacity control for player effects.

That idea could become increasingly valuable as builds become more spectacular.

Diablo 4's abilities are designed to look powerful.

That works wonderfully when a Sorcerer fills the screen with magic.

It works slightly less wonderfully when the Sorcerer's magic prevents the Sorcerer from seeing the unexploded ordinance underneath it.

There is a balance between spectacle and information.

At the moment, some players think Diablo 4 has wandered too far toward spectacle.

Not Everyone Thinks the Swords Are a Problem

It is worth noting that this is not universal.

Hardcore players in the same discussion argue that the falling swords are clearly visible and audible enough to avoid consistently.

They also make an interesting point about player behaviour.

Hardcore teaches players from level one that survival matters.

Softcore often teaches the opposite.

If killing twenty monsters at once is faster than carefully fighting six, dying occasionally may simply be an acceptable efficiency cost.

That encourages aggressive builds, low defensive investment and enormous pulls.

Eventually those habits meet an attack designed specifically to punish standing still.

The sword wins.

There is probably truth on both sides.

Players can build more defensively.

Players can pay more attention.

And Diablo 4 can communicate lethal mechanics more clearly.

Those ideas are not mutually exclusive.

Difficulty Should Come From Reacting to Danger, Not Finding It

This is ultimately what makes the visual-clarity argument more interesting than another debate about whether Diablo 4 is too difficult.

Difficult attacks are fine.

Deadly attacks are fine.

Even one-shot mechanics can work when the game clearly tells players what is about to happen and gives them a meaningful opportunity to respond.

The frustrating deaths are the ones where the explanation only becomes obvious after watching a recording frame by frame.

Blizzard does not necessarily need to remove falling swords, poison pools, explosions or dangerous monster affixes.

It may simply need to make sure players can actually see them.

Reduce unnecessary effect clutter.

Strengthen dangerous telegraphs.

Give hostile ground effects clearer outlines.

Add better death information.

Consider opacity controls for friendly spell effects.

Diablo 4 should be chaotic.

It is Diablo.

Half the appeal is turning hundreds of demons into an expensive particle-effects demonstration.

But when the game asks players to dodge a lethal sword falling from the sky, there is one fairly reasonable requirement.

Let them see the sword.

Sources

Diablo IV Forums: Swords Falling On My Head

Diablo IV Forums: Stupid Overhead Sword Kill

Diablo IV Forums: Falling sword tactic?

Diablo IV Forums: Realmbreaker one-shot discussion

Blizzard: Diablo IV Patch Notes

```

Diablo 4’s Tower Scaling Shows Just How Insane the Build Gap Has Become

2026-08-21T00:35:31.393-07:00

There is a difference between a strong Diablo 4 build and a weak Diablo 4 build.

Then there is whatever is happening at the top of the Tower.

A current community discussion has put numbers on just how violently Diablo 4's endgame scaling accelerates at the highest tiers.

According to the calculation being debated, moving from Tower Tier 120 to Tier 150 requires dealing with roughly 4,142 times as much effective monster health.

Not 4,142%.

Approximately 4,142 times.

And if one build clears Tier 150 significantly faster than another build barely clears Tier 120, the theoretical performance gap becomes even more absurd.

At some point, the Tier List stops being a list and becomes a geological survey.

The Calculation Starts With 32% Per Tier

The argument comes from a discussion on Blizzard's Diablo IV forums about the way monster health scales at the extreme end of the Tower.

According to the player calculations being discussed, each tier above 120 effectively multiplies the required damage by approximately 1.32.

One tier does not sound particularly dramatic.

Thirty tiers do.

The calculation looks like this:

1.32³⁰ = approximately 4,142.

In other words, the health requirement represented by Tier 150 is more than four thousand times the Tier 120 baseline under that scaling model.

That does not mean every Tier 150 build literally deals exactly 4,142 times the real-world DPS of every Tier 120 build.

Movement speed matters.

Monster density matters.

Pylons matter.

Boss selection matters.

And the Tower contains enough RNG that high-level players have already been asking Blizzard to rethink parts of the mode.

But the underlying health curve illustrates something important.

A relatively small difference in Tower tier can represent an enormous difference in required character power.

A Three-Minute Clear Makes the Comparison Even Wilder

The original forum post takes the calculation one step further.

Imagine one build takes nine minutes to clear Tower 120.

Another clears Tower 150 in three minutes.

If you simply use completion time as an additional rough indication of throughput, the theoretical gap climbs from around 4,142x to more than 12,000x.

That particular comparison is more controversial.

Other players correctly point out that clear time cannot be converted directly into damage because sufficiently powerful characters eventually become limited by things like movement, enemy positioning and dungeon mechanics rather than raw DPS.

A character capable of deleting everything instantly cannot kill enemies before reaching them.

Teleportation remains stubbornly faster than mathematics.

Still, the exact multiplier is almost beside the point.

Whether the practical gap is 4,000x, 2,000x or something considerably smaller, Diablo 4's strongest builds are operating in a different universe from many perfectly functional endgame builds.

This Is Why Diablo 4 Balance Can Look Fine Until It Suddenly Doesn't

At ordinary difficulty levels, two builds can feel reasonably close.

Both kill monsters.

Both finish activities.

Both generate enormous numbers accompanied by explosions.

Move far enough up the Tower, however, and small differences begin compounding.

One build gets another multiplicative damage source.

Another gets stronger resource scaling.

One interaction double-dips.

A new Unique adds another multiplier.

A seasonal power multiplies the multiplier that was already multiplying something else.

Do that enough times and the difference is no longer 20%.

It is several Tower floors.

And several Tower floors can represent exponentially more health.

This is also why seemingly modest Diablo 4 balance changes can have enormous consequences at the extreme endgame.

We recently looked at how Season 15 changes the fundamental stat scaling of several classes, while new systems continue adding powerful multiplicative effects.

Each individual change can look manageable.

The final build eventually becomes a spreadsheet with anger issues.

The Tower Was Built to Expose Exactly This

There is also an argument that the Tower is doing its job.

Blizzard created the mode specifically as a competitive endgame challenge.

The Tower uses timed runs and increasingly difficult tiers to determine leaderboard placement, with the highest-performing characters competing for rankings and seasonal rewards.

Blizzard even added a build viewer so players can inspect the setups used by top leaderboard entries.

If Tower 150 were only slightly harder than Tower 120, the leaderboard would struggle to separate extraordinarily powerful builds from merely excellent ones.

Extreme scaling creates room at the top.

That is useful.

The problem appears when that leaderboard gap begins exposing enormous balance differences between skills and classes rather than simply differences in optimisation.

A player who regularly pushes the Spiritborn leaderboard recently argued that the Tower itself also suffers from excessive RNG, citing monster combinations, density, boss selection and Sanctification effects as factors capable of deciding high-tier runs.

So the final Tower number is measuring several things simultaneously:

Build strength
Player execution
Equipment optimisation
Dungeon RNG
Pylon usage
Monster selection
And increasingly ridiculous amounts of damage

Mostly that last one gets the screenshots.

Diablo 4 Has Been Here Before

Anyone who played Diablo III for long enough may recognise the direction of travel.

Damage starts relatively understandable.

Then items introduce multipliers.

Sets introduce larger multipliers.

Difficulty rises to compensate.

More multipliers arrive to beat the new difficulty.

Eventually everyone is discussing percentages that would make an accountant quietly leave the room.

Diablo 4 originally launched with much smaller damage numbers than Diablo III's late-game extremes.

Three years of systems, Uniques, Paragon interactions and seasonal additions have gradually changed that.

The Season 15 PTR is already experimenting with additional major damage sources, including a Soul Splinter capable of granting up to 100% multiplicative damage in exchange for disabling Critical Hits.

Power is fun.

Multiplication is fun.

The problem comes when every new system needs another multiplier simply to remain relevant beside the old multipliers.

The Difference Between Builds Matters More Than the Damage Number

The real issue is not whether Diablo 4 characters deal millions, billions, trillions or numbers requiring scientific notation.

The screen can display whatever Blizzard wants.

The important question is how far apart viable builds are.

If one fully optimised build reaches Tower 120 and another reaches 150, the tier difference may look modest on a leaderboard.

Thirty levels.

Nothing dramatic.

But exponential scaling means those thirty levels can hide an extraordinary difference in effective power.

That makes balancing weaker skills increasingly difficult.

Buff something by 50% and it sounds enormous.

If the strongest alternative is effectively orders of magnitude ahead at the extreme end, 50% barely moves the elevator.

This is why some players in the current discussion are asking Blizzard to reduce the overall spread rather than simply handing weaker builds increasingly enormous percentage buffs.

Diablo 4 does not need every build to perform identically.

That would arguably make an ARPG considerably less interesting.

There should be discoveries.

There should be powerful combinations.

There should absolutely be builds that make you wonder whether someone at Blizzard forgot a decimal point.

But when the difference between two endgame builds can be illustrated using a multiplier above 4,000, balancing becomes something considerably stranger.

Tier 120 and Tier 150 are separated by thirty numbers.

Mathematically, they may as well live in different postal codes.

Sources

Diablo IV Forums: Multipliers, the 1,242,600% imbalance!

Diablo IV Forums: Tower needs a Rework

Blizzard: Diablo IV 3.1 PTR — Tower and Leaderboard updates

Blizzard: Diablo IV Patch 2.5 — Tower scaling and Pit parity

```

Diablo 4 Players Have Explored 65/65 Skovos Areas — And Still Can’t Get the Achievement

2026-08-21T00:15:32.115-07:00

Diablo 4 players have successfully explored every corner of Skovos.

The game agrees.

65 areas discovered out of 65.

The achievement system has apparently decided that mathematics is merely a suggestion.

Players are continuing to report that the No Island Unturned challenge remains incomplete even when their Skovos exploration counter shows 65/65, preventing some of them from earning the associated achievement and Amazonian Charge mount.

The problem is particularly frustrating because Blizzard already fixed the original version of the Skovos exploration bug.

Unfortunately, that fix appears to have created a second problem for players who explored everything too early.

Skovos Originally Asked Players to Find 67 Areas

When Lord of Hatred opened Skovos earlier this year, completionists quickly ran into something strange.

The region's exploration tracker expected players to discover 67 locations.

Players searched beaches.

They searched temples.

They searched suspicious bits of coastline.

They wondered whether the Cow Level was somehow involved.

Eventually it became clear that players weren't simply overlooking two extremely well-hidden rocks.

The available map contained only 65 areas that could actually be discovered.

Blizzard subsequently changed the requirement, and the Skovos exploration counter now correctly displays 65/65 rather than 65/67.

Problem solved.

Mostly.

Players Who Already Had 65/67 Can Still Be Stuck

The particularly unlucky group appears to be players who completely explored Skovos before the requirement was corrected.

Those characters previously showed 65/67.

After the update, they now correctly show 65/65.

But for some players, No Island Unturned still remains listed as incomplete or even “Not Started”.

The likely problem is relatively straightforward.

The game appears to award the challenge when a new Skovos area is discovered.

If you had already discovered all 65 locations before Blizzard changed the requirement, there is nothing left for that character to discover.

The counter knows you have finished.

The achievement apparently never receives the memo.

And Season 15 Hasn't Fixed It

This would be easier to dismiss as an old expansion-launch bug if players weren't still reporting it now.

They are.

One of the longest-running bug threads was bumped again on August 17, with a player saying that the problem remains in Season 15 despite having 65/65 exploration on both Softcore and Hardcore.

Another current report describes exactly the same situation: 65/65 areas discovered, achievement status “Not Started.”

A separate PlayStation player reports being stuck at 99% overall achievement completion because No Island Unturned refuses to unlock.

There are reports going all the way back to May.

At this point, the island has been turned over quite thoroughly.

The achievement has not.

There Is a Workaround — Unless You Were Too Thorough

Some players have managed to trigger the achievement by exploring Skovos again on the opposite game mode.

If you originally completed the map on Softcore, for example, starting the campaign on Hardcore and discovering all 65 locations there can reportedly cause No Island Unturned to unlock.

The same principle can work in reverse.

That is inconvenient.

But at least it is something.

The real problem affects players who already fully explored Skovos on both Softcore and Hardcore before the requirement was corrected.

They have no untouched realm left to use as a trigger.

Players have also reported that creating another character on a realm where exploration is already shared does not solve the problem.

For that group, the current solution appears to be:

wait for Blizzard.

Every completionist's favourite endgame activity.

Make Sure You Actually Have 65/65 First

There is an important distinction between this bug and simply being stuck at 64/65.

If your map still says 64/65, you probably are missing an area.

Players continue to find tiny pieces of Skovos that are remarkably easy to overlook, including a small pocket near the Dark Refuge area in Lycander.

Finding the final legitimate location can still trigger the achievement normally for players who did not previously complete the old 65/67 requirement.

The bug discussed here specifically affects people whose map already says:

65/65.

If that is you and No Island Unturned still says incomplete, running around Skovos staring suspiciously at every beach probably isn't going to help.

The Amazonian Charge Mount Can Be Caught in the Problem Too

No Island Unturned is more than another checkbox for completionists.

Players affected by the issue have also reported being unable to receive the Amazonian Charge mount reward tied to their Skovos exploration progress.

That makes the missing retroactive completion considerably more annoying than an incorrectly displayed percentage.

Players did the exploration.

The map confirms that they did the exploration.

The game simply needs to recognise that 65 out of 65 is generally considered complete.

This Looks Like It Needs a Retroactive Fix

That is what affected players are now asking Blizzard to implement.

Not another change to the number of locations.

Not another hidden area.

Not another journey around Skovos on a third character.

A retroactive check that looks at characters or realms with 65/65 exploration and awards No Island Unturned accordingly.

Until that happens, some of Diablo 4's most dedicated explorers are stuck in the unusual position of having explored 100% of an island while receiving 0% of the achievement for doing it.

Mephisto may be the Lord of Hatred.

But nothing generates hatred quite like staring at 65/65 next to an unfinished achievement.

Sources

Diablo IV Forums: No Island Unturned — “Not Started” with 65/65 discovered

Diablo IV Forums: No Island Unturned and Amazonian Charge not granted after requirement update

Diablo IV Forums: Cannot complete No Island Unturned

Diablo IV Forums: No Island Unturned still not possible on PlayStation

```

Diablo 4 Players Are Killing Their Own Party Members in Infernal Hordes

2026-08-21T00:07:12.819-07:00

Infernal Hordes already contain enough things trying to kill you.

Apparently your party members can now join the list.

A fresh Diablo 4 bug report describes players being repeatedly killed by other members of their own party during Infernal Hordes, despite the activity having absolutely nothing to do with PvP.

The latest report was posted on August 20 by a player who says another Barbarian repeatedly appeared as the cause of death.

More importantly, this does not appear to be an entirely new problem.

Several earlier reports point toward a deeply strange interaction involving Wyrdskin, Barbarian shouts and friendly players.

Sanctuary has friendly fire now.

Possibly.

And naturally, the Barbarian may be responsible.

A Barbarian Apparently Kept Killing Their Teammate

The newest report comes from Blizzard's official Diablo IV bug forums.

The player says they have been killed by other players while participating in Infernal Hordes as part of a party.

During the most recent run, another Barbarian allegedly killed them repeatedly.

According to the report, the problem had also happened more than a week earlier, leading the player to assume it would eventually be fixed.

It wasn't.

Another forum user immediately asked whether the Barbarian was using Wyrdskin.

That is where things become considerably more interesting.

Wyrdskin Has Been Affecting Friendly Players for Months

Wyrdskin is supposed to make attacks apply Vulnerable to distant enemies and Weakened to close enemies, while increasing damage against targets suffering from both effects.

The important word there is enemies.

Players have been reporting since at least May that the Wyrdskin Charm can apparently treat friendly players rather less diplomatically.

One Barbarian playing alongside a Paladin discovered that using Rallying Cry could apply Weakened to the Paladin.

The interaction then appeared to trigger the Paladin's Thorns, causing damage to be reflected back onto the Barbarian.

The player tested the problem by removing Wyrdskin.

The friendly-fire behaviour disappeared.

Later reports described the same basic problem with Wyrdskin applying Vulnerable and Weakened to party members.

By July, players were reporting something worse.

They could actually die from it.

Players Have Reported Deaths Outside PvP Zones Too

A July console bug report described two Whirlwind Barbarians using Wyrdskin and becoming Vulnerable and Weakened around each other.

The player also reported taking enormous damage when Thorns entered the equation.

In one case, the combat log reportedly named another player as the source of death even though they were not participating in PvP.

Removing Wyrdskin once again stopped the behaviour.

Another report came from a Hardcore Barbarian who said they were killed by another player during a Realmwalker encounter outside a PvP zone.

That player was also using Wyrdskin.

For a normal character, unexpected friendly fire is irritating.

For Hardcore, it is the sort of bug capable of converting several dozen hours of character progression into a character-selection-screen memorial.

We Don't Know If Wyrdskin Caused the Latest Infernal Hordes Deaths

There is one important distinction.

The player reporting the August 20 Infernal Hordes deaths did not confirm that the other Barbarian was using Wyrdskin.

They had not inspected the character's equipment when the deaths happened.

So we cannot say that Wyrdskin definitely caused this particular incident.

But the similarities are difficult to ignore.

We already have multiple reports involving Barbarians, Wyrdskin, friendly players receiving enemy debuffs and combat logs crediting other players with kills outside PvP.

Now another player is reporting almost exactly that outcome inside Infernal Hordes.

At minimum, Blizzard appears to have a friendly-player interaction worth investigating.

The Latest Patch Doesn't Mention Fixing It

Blizzard released Diablo IV Patch 3.1.3 on August 12 with another collection of fixes for Season of Death Awakening.

The patch addressed several class issues and even fixed a problem involving teleporting to Infernal Hordes.

There is no listed fix for Wyrdskin applying Vulnerable or Weakened to friendly players.

The previous 3.1.2 patch did include a Wyrdskin fix, but it concerned the gloves failing to appear correctly on character models.

So Blizzard has successfully made Wyrdskin easier to see.

It may still be trying to murder your friends.

Infernal Hordes Probably Didn't Need Friendly Fire

Infernal Hordes are already built around throwing increasingly dense waves of enemies at players while they race to generate Burning Aether.

As we have seen with other Infernal Hordes bugs, even relatively small mechanical problems become considerably more noticeable inside a timed activity.

Getting killed is supposed to be part of the danger.

Getting killed by Dave from your own party is less traditional.

Until Blizzard confirms exactly what is happening, players using Wyrdskin alongside other Barbarians or Thorns-heavy characters may want to keep an eye on their debuffs and combat logs.

Especially in Hardcore.

The demons are supposed to be on the other team.

Sources

Diablo IV Forums: Killed by players during Infernal Hordes

Diablo IV Forums: Rallying Cry killing me with Paladin in party

Diablo IV Forums: Wyrdskin and Thorns letting players kill each other outside PvP

Diablo IV Forums: Hardcore player killing bug report

Blizzard: Diablo IV Patch Notes

```

Diablo 2’s New Warlock Era Doesn’t Support Legacy Graphics — And Players Are Divided

2026-08-20T01:18:25.690-07:00

Diablo II: Resurrected has always had one particularly wonderful party trick.

Press a button and 2021 disappears.

The rebuilt monsters, dynamic lighting and detailed environments vanish, replaced instantly by the pixels, sprites and 800x600 memories of Diablo II's original era.

Then Reign of the Warlock arrived.

And for players entering Diablo II's newest era, that button effectively stopped being part of the experience.

Reign of the Warlock content does not currently support Diablo II: Resurrected's Legacy Graphics mode, leaving players divided over whether Blizzard should recreate the new expansion in an art style originally built more than 25 years ago.

For some players, that sounds like an unreasonable amount of work for a nostalgia feature.

For others, switching between old and new Diablo II was part of what made Resurrected special in the first place.

Legacy Graphics Were More Than a Joke Button

When Diablo II: Resurrected launched in 2021, Blizzard made a very deliberate choice.

The new graphics were essentially built over Diablo II rather than replacing it entirely.

Players could switch between Resurrected and Legacy visuals while playing and immediately see how closely the remake followed the original environments, monsters and animations.

Blizzard continued improving that feature after launch.

Patch 2.4 even introduced three different Legacy Graphics emulation options: GDI, Glide and Resurrected.

Blizzard described the Resurrected option as its preferred emulation mode while preserving the unfiltered GDI presentation for players who wanted something even closer to the software-rendered original.

This was not a forgotten setting buried in a menu.

Blizzard actively maintained it.

Then Diablo II started receiving things the original game had never contained.

Warlock Creates a Problem the Original Remaster Never Had

Reign of the Warlock is fundamentally different from earlier Diablo II: Resurrected updates.

Balance changes are easy enough.

A Terror Zone can reuse an existing area.

A revised Unique can reuse an existing item graphic.

But the Warlock is the first completely new playable Diablo II class in 25 years.

There is no original Warlock sprite hidden on an old Blizzard hard drive waiting to be switched on.

There is no classic animation for Miasma Chain.

No 2000-era Warlock wearing every possible armor combination.

No original set of walk, run, cast, attack, hit-recovery and death frames.

Someone would have to make them.

And Diablo II’s Old Graphics Were Not Exactly Simple

This is where the debate gets more interesting.

It is easy to look at Diablo II's original graphics today and think:

They're sprites. How difficult could it be?

Very.

Diablo II's characters were originally created as 3D models and then rendered into enormous collections of 2D frames.

A character needed animations from multiple directions.

Armor and equipment had to visually work across those animations.

Weapons changed appearance.

Different actions required different sequences.

Warlock would need to fit into all of that.

One player in the current discussion estimated that properly building a complete Warlock sprite library would effectively mean recreating a significant fraction of Diablo II's original character-art workload.

Then come the new skills.

The new items.

Interface additions.

And whatever Blizzard adds next.

Suddenly the nostalgia toggle has its own development roadmap.

Some Players Still Want Blizzard to Do It

That has not stopped people asking.

A forum thread from May includes players requesting Legacy Graphics support for Reign of the Warlock, with one saying they enjoy the original visuals so much that they are reluctant to progress into the new era without them.

Another player went considerably further:

They said they would actually pay another $30 for a legacy graphics pack.

That may sound extreme.

But Diablo II has a very unusual audience.

This is a game where selecting the correct shade of brown from the year 2000 can constitute an important artistic principle.

Others Think Blizzard’s Resources Are Better Spent Elsewhere

The opposite argument is fairly convincing too.

Diablo II: Resurrected still has bugs.

It still has balance issues.

Reign of the Warlock itself is still being tuned.

Patch 3.3 just changed several parts of the expansion ahead of Ladder Season 15.

One tiny-looking collision fix has already led players to believe Abyss Warlock became dramatically stronger in practical combat.

Blizzard also changed Worldstone Shard and Ancient Statue drop rates, while continuing to adjust the expansion's item economy.

For players who want more balancing, more endgame content and more bug fixes, assigning artists and engineers to recreate an entire new class in 25-year-old graphics is not necessarily where they want Blizzard spending its limited Diablo II resources.

Could Blizzard Fake It?

Players have suggested compromises.

One idea is to use placeholder legacy assets.

Give Warlock a recolored sprite from another class.

Simplify newer spell effects.

Reuse existing monster graphics wherever possible.

Another proposal is allowing Legacy Graphics in Reign of the Warlock while disabling the Warlock and incompatible expansion items.

That would preserve access to newer quality-of-life systems while letting people continue playing older classes with the classic presentation.

Technically elegant?

Probably not.

Very Diablo II?

Absolutely.

The Era System Makes the Divide Even More Noticeable

Reign of the Warlock introduced an unusual solution for protecting Diablo II's history.

The game is now divided between separate eras:

Diablo II Classic
Diablo II: Resurrected
Diablo II: Reign of the Warlock

Characters can exist separately across those partitions and move forward through the eras.

They cannot move backward.

Blizzard calls the system “Play your Era, Your Way.”

That makes a lot of sense mechanically.

It also makes the graphical difference rather poetic.

You can preserve old Diablo II mechanically.

You can preserve its old graphics.

But once you step into the genuinely new Diablo II timeline, something eventually has to be new.

This Is the Strange Price of Diablo II Getting New Content

For decades, Diablo II nostalgia had an enormous advantage.

The past was finished.

Everything Blizzard needed to reproduce already existed.

Reign of the Warlock changed that.

For the first time, Diablo II: Resurrected is not merely restoring or modifying Diablo II.

It is creating Diablo II content that never existed in Diablo II.

That sounds obvious.

Artistically, it creates a surprisingly difficult question.

If Blizzard adds a new class in 2026, how much effort should it spend pretending that class was also made in 2000?

Some players would clearly love to see it.

Others would rather Blizzard spend those resources on Season 16.

There probably is not a perfect answer.

But there is something wonderfully Diablo II about a game receiving its first new class in 25 years and immediately inspiring an argument over whether Blizzard should remake that new class to look 25 years old.

Sources

Diablo II: Resurrected Forums: Legacy graphics for Reign of the Warlock?

Diablo II: Resurrected Forums: No Legacy Mode in Reign of the Warlock games?

Blizzard: Rain Annihilation in Reign of the Warlock

Blizzard: Diablo II: Resurrected Patch 2.4 — Legacy Graphics Emulation

Diablo Immortal Is Rebalancing Six Classes for Bout of Realms — Four Are Missing

2026-08-20T01:07:25.441-07:00

Diablo Immortal is about to rearrange part of its PvP meta in the middle of one of the game's biggest competitive events.

Blizzard has announced a new balance patch scheduled for August 26, with changes targeting six classes:

Crusader
Druid
Monk
Tempest
Warlock
Wizard

The changes are being announced early because Blizzard wants Bout of Realms teams to have more time to think about compositions, builds and strategy.

But four classes are conspicuously absent.

Barbarian, Blood Knight, Demon Hunter and Necromancer.

Players noticed immediately.

Because nothing says competitive balance quite like reading the patch notes and checking whether your class survived the invitation list.

The August 26 Changes Are Not Bout-Only

There was initially some confusion over whether Blizzard was creating a special balance ruleset specifically for Bout of Realms.

Community Manager Jadai clarified that this is not the case.

The adjustments were not created exclusively for the tournament.

They are normal class balance changes that will affect the game more broadly, but Blizzard is revealing them early because Bout of Realms is its most competitive mode and organized teams need extra preparation time.

That makes this considerably more important than a temporary tournament modifier.

If you play one of these six classes in Battlegrounds or elsewhere, these changes matter to you too.

Warlock Is Getting One of the Most Important PvP Nerfs

Warlock receives three listed essence adjustments, and the biggest attention is already falling on Measured Halves.

Spiteful Sacrifice will still become a moving channeled attack that throws dark-energy swords forward.

But Blizzard is changing how it behaves.

The attack interval is being increased, meaning volleys happen less frequently, although each volley will hit harder.

Movement speed while channeling is being reduced.

Range is being reduced.

And most importantly, the Sacrificial Power bonus projectiles will no longer lock onto enemy players.

Instead, they fire at the target's current position.

A moving opponent can therefore dodge them.

That is a meaningful PvP change for a class that has already generated plenty of balance arguments since arriving in Diablo Immortal.

We recently looked at how Warlock was still receiving extensive fixes to its skills and legendary interactions.

Now Blizzard is moving beyond cleanup and directly changing how some of its most important PvP tools function.

Tempest Gets More Survivability and Longer Channeling

Tempest is receiving changes to both Dream and Drown and Cyclone's Call.

Dream and Drown will now let Cascade-generated waves grant an absorb shield when they hit enemies.

Blizzard is also adding a maximum trigger range so waves cannot continue spawning around targets that are too far away.

Cyclone's Call gets a more substantial redesign.

Crosswinds remains a moving channeled skill, but Tempest will now be immune to knockback while channeling.

Enemies struck by multiple wind blades in quick succession can also suffer an additional hit.

Blizzard says wind-blade damage is increasing while energy costs fall and regeneration improves.

Translation:

Longer spinning.

More blades.

Less opportunity to politely ask Tempest to stop.

Crusader’s Shield Charge Is Becoming an Actual Charge Again

Crusader receives changes to Anointed in Blood and Forced Abjuration.

The latter is especially noticeable.

Shield Charge currently turns into a forward shield swipe that knocks enemies back, slows them and builds damage through successive hits.

After the patch, it will instead make the Crusader dash forward, damaging, knocking back and slowing enemies along the path.

Hitting an enemy also grants an absorb shield.

The successive-hit damage scaling is being removed, while base damage increases.

For a skill called Shield Charge, moving forward aggressively does feel suspiciously appropriate.

Druid and Monk Get More Focused Adjustments

Druid's Promise the Obscure modifies Werebear Mangle into four directional attacks with knockback and control immunity.

Blizzard says its cooldown is being reduced and its damage scaling is being simplified around maximum Life.

Budding Union is also changing, with Circle of Life healing less when only a single target occupies the area.

That pushes the ability slightly harder toward its intended group-support identity.

Monk's Mystic Allies receive more Life through Fate and Fortune.

Nest of Vipers will also allow nearby summons to benefit from Dragon's Strike rather than limiting the effect to the Monk.

Some conditional crowd-control damage is being removed, while baseline damage increases to compensate.

Wizard Beams Are Being Pulled Back

Wizard gets changes to Frostfield and Disintegrate.

Lissana's Sorrow will increase the Chill applied by Creeping Chill.

Searing Judgement is more complicated.

Disintegrate's beam distance will be reduced.

The maximum Burn stacks required to trigger its additional damage will increase, meaning the burst happens less often.

Blizzard says the burst damage itself is being increased to compensate.

Wizard will also remain immune to knockback while channeling.

So this is less “beam deleted” and more “beam asked to respect personal space.”

Players Immediately Asked Where the Other Four Classes Went

The first community reaction was predictable.

Where is Barbarian?

Where is Necromancer?

Where is Demon Hunter?

And what about Blood Knight?

One player directly asked whether Barbarian had simply been forgotten.

Others argued that Necromancer badly needs PvP attention, while Demon Hunter players and opponents are already debating current stealth and survivability builds.

Those complaints do not automatically mean Blizzard should change every class in every patch.

Sometimes the correct balance adjustment is no adjustment.

But announcing a competitive balance pass involving six out of ten classes inevitably makes the other four much more visible.

Bout of Realms Makes the Timing Much More Sensitive

Diablo Immortal's current Bout of Realms is already underway.

Preliminary matches run from August 18 through August 22, with the Finals scheduled from August 25 through August 29 and the Championship Match on August 31.

That makes the August 26 balance update especially interesting.

According to Blizzard's currently published schedule, the class changes arrive during the Finals window.

Teams may therefore enter the tournament using one version of a build and find themselves competing under different balance conditions later in the event.

Blizzard clearly understands that compositions take planning, which is precisely why it announced the adjustments early.

We have already seen how seriously Blizzard treats this format through previous Bout of Realms tournaments and their increasingly competitive team structures.

Changing class behavior around that environment is never going to be invisible.

These Numbers Are Not Final Yet

There is one very important caveat.

Blizzard explicitly says the descriptions, statistics and balance changes revealed on August 19 are not final.

They can still change before the patch goes live on August 26.

That means players should not dismantle entire builds, swap classes or begin writing memorial speeches for Measured Halves quite yet.

But the direction is clear.

Warlock loses some tracking and range.

Tempest gains shields and stronger channeling.

Crusader gets a more mobile Shield Charge.

Druid, Monk and Wizard receive targeted adjustments.

And four classes sit outside the balance list entirely.

For casual players, that means another round of build tinkering.

For Bout of Realms teams, it means spreadsheets.

Many, many spreadsheets.

Sources

Blizzard: Balance Patch Update / Bout of Realms Preparation — August 26

Blizzard: Rise to the Top in Bout of Realms

Diablo 4 Player Runs Kurast Undercity 10+ Times for Primordial Dust — Gets Zero

2026-08-20T00:47:29.265-07:00

Diablo 4 has many ways to tell you that your build is not finished yet.

Apparently one of them is sending you into Kurast Undercity more than ten times and giving you exactly zero of the crafting material you went there to farm.

A Diablo 4 player is reporting that Volatile Primordial Dust has stopped dropping for them in Kurast Undercity, despite repeatedly using Tributes designed to reward Horadric Cube materials.

The player says they completed more than ten runs while specifically trying to farm Volatile Primordial Dust for an amulet.

The result:

0 Volatile Primordial Dust.

That does not prove the material is currently bugged.

It does, however, add another uncomfortable data point to a crafting resource that players have already spent most of Season 14 complaining is far too scarce.

The Player Was Specifically Farming Cube Materials

This was not someone casually running Undercity and wondering why a random material never appeared.

The player says they deliberately used Horadric Cube Materials Tributes while farming.

The relevant Legendary Undercity option is the Greater Tribute of Ingenuity, which enhances the final reward with Horadric Cube materials.

That is exactly the sort of activity players have been recommending when someone asks how to farm Volatile Primordial Dust.

Community farming advice has repeatedly pointed toward Kurast Undercity with Cube-material Tributes as one of the better targeted methods.

Which makes running it ten or more times without seeing the material considerably more noticeable.

Volatile Primordial Dust Is Used for Transfiguration

Volatile Primordial Dust is one of the rarer Horadric Cube materials introduced with Lord of Hatred.

Its main purpose is Transfiguration.

That means it sits directly inside one of Diablo 4's most expensive endgame crafting loops.

You take an item you have already spent time building.

You spend a rare material.

You roll the dice.

And, as we have already seen with the player whose near-perfect amulet became locked without receiving a visible Transfiguration reward, the system is not particularly forgiving when something goes wrong.

The scarcity of Volatile Dust therefore matters far more than the loss of another miscellaneous crafting reagent.

Players can burn through substantial amounts of it while chasing the correct result.

This Material Was Already a Bottleneck

The new Undercity report arrives after weeks of complaints about Volatile Primordial Dust.

Back in July, we covered how the Volatile Dust grind was turning solo endgame crafting into a second job.

One player described spending three hours farming approximately 40 Dust and then consuming the entire supply in roughly ten minutes of crafting.

Other players said the Season 14 drop rate felt substantially worse than before.

A July forum discussion includes players saying they were running Material Reserve Nightmare Dungeons and Cube-material Tributes while still struggling to maintain a supply.

Another complaint posted in early August estimated a farming rate of only 7 to 20 Volatile Primordial Dust per hour.

So even if the new player's zero-drop streak turns out to be brutal RNG rather than a bug, it is happening inside a system where the resource economy was already under pressure.

Kurast Undercity Is Supposed to Be One of the Better Options

That is what makes this particular report interesting.

Players who run out of Volatile Dust are regularly directed toward:

Kurast Undercity with Horadric Cube Material Tributes
Material Reserve Nightmare Dungeons and Escalations
Cube Spoils through War Plans
Whisper rewards
Elite farming

Even popular Diablo 4 farming guides recommend using an Undercity Tribute with Horadric Cube Materials when you need Cube resources quickly.

And Blizzard itself has previously fixed a tooltip problem involving Cube Dust, specifically noting that the tooltip did not properly indicate that the material could be obtained from Undercity activities.

In other words, Kurast Undercity absolutely belongs in this farming ecosystem.

Whether every individual Cube material is guaranteed on every run is another matter.

Zero Drops Does Not Automatically Mean Bugged

This distinction is important.

We currently have one fresh player report describing more than ten runs without Volatile Primordial Dust.

Blizzard has not confirmed a drop bug.

The Greater Tribute of Ingenuity promises Horadric Cube materials broadly. It does not appear to guarantee that every Cube material, including Volatile Primordial Dust, will appear on every run.

That leaves RNG as a completely plausible explanation.

Ten unlucky runs can happen.

Diablo has built an entire franchise around demonstrating this scientific principle.

But when players specifically target the activity recommended for Cube materials and repeatedly receive none of the material creating their crafting bottleneck, it is worth watching.

The Bigger Problem Is How Much Dust Transfiguration Can Consume

This is ultimately why players care.

If Volatile Primordial Dust were used once every few hours, a streak of bad drops would be annoying but manageable.

Transfiguration can consume it considerably faster.

Players chasing very specific endgame outcomes can make dozens of attempts.

One recent feedback thread describes the resource as the main limitation of the current Transfiguration system and argues that Dust should drop from far more endgame activities.

The complaint is not simply that good items should be easy to obtain.

It is that the crafting system encourages repeated experimentation while the material supply actively discourages it.

That creates a strange loop.

The Horadric Cube says:

Try again.

Your material tab says:

Absolutely not.

For Now, This Is One Report Worth Watching

We would not call Kurast Undercity broken based on this report alone.

There are too many players successfully obtaining Volatile Primordial Dust from Cube-focused activities for that conclusion.

But more than ten targeted runs for zero Dust is enough to raise the question, particularly after an entire season of complaints about the material's availability.

If other players begin reproducing the same sudden zero-drop behavior, then we may be looking at something more specific than Season 14's already unpopular drop rate.

Until then, the safest conclusion is simpler.

Diablo 4 has an endgame material that players desperately need for repeated crafting attempts.

One of the activities recommended for farming it just gave one player more than ten consecutive lessons in disappointment.

Sanctuary's crafting economy remains extremely efficient.

At consuming your materials.

Sources

Diablo IV Forums: Player report regarding Volatile Primordial Dust not dropping in Kurast Undercity

Diablo IV Forums: Volatile Primordial Dust Nerfed to the Ground

Diablo IV Forums: More Volatile Primordial Dust

Diablo 4 Says These Eternal Characters Are in Endgame — But War Plans Are Still Locked

2026-08-20T00:24:02.670-07:00

Diablo 4 has found an impressively philosophical way to define the word “Endgame.”

Some Eternal characters are being displayed as Lord of Hatred (Endgame) on the Character Select screen.

There is just one problem.

They still cannot access parts of the endgame.

Players have been reporting the issue since shortly after Lord of Hatred launched, with older Eternal characters sometimes failing to inherit the correct campaign-completion state even after Lord of Hatred has been completed elsewhere on the account.

In one particularly clear example, a player says their Eternal characters have already skipped the campaign and Character Select explicitly shows them as being in Lord of Hatred's Endgame state.

Yet War Plans are unavailable.

Tyrael is missing from the War Plans table in Temis.

Several waypoints remain locked.

Endgame, apparently, is now more of a state of mind.

The Character Select Screen Says Everything Is Fine

The current problem is closely related to the Eternal campaign skip problem we recently covered, but this particular version is even stranger.

The affected characters are not simply being told to complete the campaign again.

According to the player report, Diablo 4 already recognizes them as being in:

Lord of Hatred (Endgame)

That should be the destination.

Blizzard's own Lord of Hatred documentation describes “Story Complete: Endgame” as the option available after completing the expansion campaign. Once unlocked, existing characters can also skip the campaign from Character Select instead of replaying the story.

The problem is that the label and the actual character state do not always appear to agree.

War Plans Simply Aren’t There

The most obvious symptom is War Plans.

War Plans are one of Lord of Hatred's central endgame systems. Once properly unlocked, players travel to Temis, use the Command Table and build chains of activities including Nightmare Dungeons, Helltides, Infernal Hordes, the Pit, Undercity and boss content.

For the affected Eternal characters, that onboarding appears to be missing.

The player says Tyrael is not standing beside the War Plans table.

The table is effectively dead.

That creates a particularly nasty progression problem because War Plans are not just another optional side activity. They feed directly into Diablo 4's current endgame structure and Activity Trees.

And even when War Plans do unlock correctly, they have their own problems. We recently covered players completing every activity only to find their War Plan progression stuck at 9/10.

Some players cannot finish the board.

Others apparently cannot get the board in the first place.

Efficiency.

The Horadric Cube Has Been Caught in Similar Progression Problems

This is not the first time old Eternal characters have struggled to inherit Lord of Hatred unlocks correctly.

Back in May, players reported completing Lord of Hatred on one character and then discovering that older level 60 Eternal characters still could not use the campaign skip.

One PlayStation player specifically said they had completed Lord of Hatred on an Eternal Sorcerer but could not skip the campaign on two other Eternal characters.

The reason they cared was simple:

They wanted access to the Horadric Cube and War Plans without replaying the entire expansion campaign.

Another player in the same discussion reported that some Eternal characters received the Character Select campaign-sync option while others did not, despite all of them predating Lord of Hatred and being the same level.

That suggests this is not simply someone missing an obvious quest marker.

Finishing Lord of Hatred Is Supposed to Unlock the Skip

Blizzard's intended behavior is fairly clear.

Once Lord of Hatred has been completed, players can create a character using the Story Complete: Endgame starting state.

Blizzard also specifically says that previously created characters can skip the campaign directly from Character Select.

That matters because the affected characters are doing exactly what Blizzard's interface tells them to do.

The campaign is marked as skipped.

The game calls them Endgame characters.

And yet the world state appears to remain partially trapped somewhere before that point.

This Looks Like a Character-State Problem

Blizzard has not publicly confirmed the precise cause, so anything beyond the visible symptoms remains speculation.

But the reports look remarkably like Diablo 4 is failing to synchronize several different progression flags.

One flag tells Character Select:

This character is in Endgame.

Another apparently tells Temis:

Absolutely not.

That would also explain why players report a mixture of symptoms rather than one simple missing button.

Some cannot select the campaign skip.

Some can select it but still lack War Plans.

Some find waypoints locked.

Some do not see the expected endgame NPCs.

And some Eternal characters on the same account apparently work perfectly normally.

The Latest Patch Notes Don’t Mention a Fix

Diablo 4's latest listed live patch is 3.1.3 from August 12.

It includes several War Plans fixes, including a problem where teleporting to Infernal Hordes could fail on lower difficulties.

But Blizzard's patch notes do not mention repairing campaign-state synchronization for older Eternal characters.

That is important because these reports have now survived well beyond the immediate Lord of Hatred launch period.

This is not simply expansion-launch confusion from the first afternoon.

Players were reporting campaign-skip problems in May.

The “Endgame but no War Plans” report arrived in July.

And there is still no specifically documented fix in the current live notes.

Eternal Characters Are Exactly Where This Should Work Best

There is an extra irony here.

Eternal Realm exists partly so players can keep old characters alive indefinitely.

These are the characters people have spent seasons building, adjusting and preserving.

They are precisely the characters most likely to predate Lord of Hatred.

Forcing those characters into broken or inconsistent progression states defeats much of the point.

It is also why this problem is more serious than a missing quest icon.

Lord of Hatred made the Horadric Cube and War Plans fundamental parts of Diablo 4's modern endgame. If an old character cannot correctly transition into that state, a substantial portion of the expansion effectively disappears.

For Now, “Endgame” Doesn’t Necessarily Mean Endgame

There are community-suggested workarounds floating around, including changing difficulty, relogging and looking for missing onboarding quests.

We would not treat any of those as a confirmed fix.

The underlying issue appears inconsistent between characters, and Blizzard has not published an official workaround for this particular progression state.

So the safest description remains straightforward:

Some Diablo 4 Eternal characters are being marked as Lord of Hatred (Endgame) while still missing the systems that designation is supposed to unlock.

When the game's own Character Select screen says you have reached the endgame, expecting to find the endgame seems reasonably fair.

Sanctuary apparently requires additional paperwork.

Sources

Diablo IV Forums: Eternal characters with no War Plan

Diablo IV Forums: Can't skip campaign after completion

Blizzard: Prepare for the Reckoning — Lord of Hatred Draws Near

Blizzard: Diablo IV Patch Notes

Diablo 4 Switch 2 Leak Points to September 15 Release With Both Expansions

2026-08-20T00:07:36.949-07:00

Diablo 4's long-rumored Nintendo Switch 2 version has suddenly become much harder to dismiss.

We no longer just have ratings-board sightings and vague suggestions that Blizzard is working on something.

A new report from Dealabs leaker billbil-kun now gives us a date.

A price.

A version name.

Expansion details.

And even the slightly depressing contents of the physical box.

According to the leak, Diablo 4 will launch on Nintendo Switch 2 on September 15, 2026 as the Age of Hatred Collection, including the base game, Vessel of Hatred and Lord of Hatred.

Blizzard has not officially announced the Switch 2 version yet.

But at this point, the demon is beginning to leave quite a lot of footprints.

The Reported Release Date Is September 15

Dealabs reports that Diablo 4 is scheduled to arrive on Nintendo Switch 2 on September 15.

The information comes from billbil-kun, whose leaks have repeatedly proven accurate across games, hardware and subscription announcements.

Video Games Chronicle has since reported the same new details, while stressing that the port remains officially unannounced.

The timing would be extremely interesting.

BlizzCon 2026 begins on September 12.

The leak claims pre-orders for the Switch 2 version are also planned to open on September 12.

Three days later:

Launch.

That does not exactly require Deckard Cain to interpret.

It Reportedly Includes Both Expansions

The Switch 2 release is reportedly called the Age of Hatred Collection.

That means Nintendo players would not be receiving a stripped-down version of Diablo 4 from 2023.

The package reportedly includes:

Diablo IV
Vessel of Hatred
Lord of Hatred

That would put Switch 2 players directly into the current version of Diablo 4 rather than making them buy years of content separately before catching up.

And there is quite a lot to catch up on.

Lord of Hatred has transformed Diablo 4's endgame through systems such as War Plans, the Horadric Cube and newer progression structures.

Unfortunately, some of those systems have also created problems. We recently covered how players can finish every War Plan activity and still become stuck at Rank 9/10.

Welcome to Sanctuary.

Here is your handheld.

Here is your endgame bureaucracy.

The Price Is Reportedly $69.99

The leak lists the Switch 2 edition at:

$69.99
€69.99
£62.99

Given that the package reportedly includes both expansions, this would position the Switch 2 release as the current complete Diablo 4 bundle rather than a budget port of the base game.

That distinction matters because Lord of Hatred is no longer simply optional side content sitting beside the original campaign.

Much of Diablo 4's current progression structure assumes players are engaging with the expansion systems.

We have seen that especially clearly with older characters, where some Eternal characters are still having trouble accessing the campaign skip and the progression state required for newer endgame content.

A fresh Switch 2 account would presumably begin with a much cleaner path.

Presumably.

This is Diablo.

There Is a Physical Edition — Sort Of

Collectors should probably lower their expectations before making shelf space.

The leak says Diablo 4 will receive a retail boxed release for Switch 2.

But it reportedly will not contain a cartridge.

It will not even use Nintendo's Game-Key Card format.

Instead, the box is said to contain a download code.

So technically:

Physical box.

Digital game.

Modern preservation remains a delightful subject.

Blizzard Has Already Said the Hardware Isn’t the Problem

A Switch 2 version has always made technical sense.

Former Diablo general manager Rod Fergusson said back in 2025 that Switch 2 had the performance required to run Diablo 4.

His concern was not raw hardware.

It was live-service functionality on a device people regularly play handheld and away from a permanent internet connection.

That is the more interesting challenge.

Diablo 4 remains an always-online game.

Putting it on a handheld platform does not suddenly turn it into Diablo III's wonderfully portable offline experience.

If the port is real, Blizzard will need to make that relationship extremely clear.

This Has Been Building for Months

The September leak does not appear from nowhere.

Earlier ratings-board activity already suggested Diablo IV and Lord of Hatred were being prepared for Nintendo Switch 2.

At the time, ratings alone were not enough to tell us whether the project would actually launch, when it might appear or what would be included.

The new leak fills in most of those blanks.

September 15.

Age of Hatred Collection.

Both expansions.

$69.99.

Code in a box.

There are only so many details you can add before a rumor begins wearing launch-day clothes.

BlizzCon Looks Like the Obvious Reveal

If the reported September 12 pre-order date is correct, BlizzCon is the obvious candidate for an official announcement.

The event begins that same day.

A first-day Switch 2 reveal followed by immediate pre-orders and a September 15 launch would give Blizzard an extremely tidy announcement cycle.

There is another possibility.

Gamescom Opening Night Live takes place on August 25, and Blizzard has repeatedly used Gamescom to show major Diablo and Warcraft material.

That could allow Blizzard to reveal the port earlier and save BlizzCon for something larger.

And Blizzard certainly has other Diablo 4 material to discuss.

Season 15 is already becoming one of the more substantial system updates we have seen recently. The PTR tested Soul Splinters, which may have been one of its strongest new ideas, alongside Challenge Dungeons, Legacy Uniques and Rebirth.

Blizzard also deliberately held some Season 15 content back from the PTR, something we discussed while asking whether public testing is solving Diablo 4's problems or spoiling too much before launch.

BlizzCon still has secrets left.

A Switch 2 Launch Could Be Excellent Timing for Diablo 4

A portable Diablo 4 has obvious appeal.

Diablo III was a remarkably natural fit for the original Switch.

Diablo II: Resurrected followed.

Diablo 4 is the missing piece.

And launching it as a complete collection after Lord of Hatred rather than rushing the base game onto Nintendo hardware years earlier may actually work in its favor.

Switch 2 players would arrive after years of itemization revisions, endgame rebuilds and quality-of-life improvements.

Even Season 15 is already preparing another overhaul of high-end gearing, including the new direction for Mythic crafting.

They may be arriving late.

They may also be arriving at a considerably better version of the game.

Still a Leak Until Blizzard Says Otherwise

The amount of detail is convincing.

The previous ratings add weight.

billbil-kun has an excellent history with this kind of information.

And September 15 fits neatly around BlizzCon.

None of that makes this official.

Blizzard has not announced Diablo 4 for Nintendo Switch 2.

Nintendo has not listed it for September 15.

There is currently no official Switch 2 store page we can point you toward and say:

There.

The demon lives here now.

But compared with the vague rumors from earlier this year, we now have something much more specific.

If the leak is correct, Diablo 4 is less than a month away from becoming portable.

Provided, of course, you also bring an internet connection.

Sources

Dealabs: Diablo IV Switch 2 Release Date, Price and Physical Edition Report

Video Games Chronicle: New Information on Switch 2 Diablo 4 Port

Diablo 2’s PS5 Offline Stutter May Finally Be Fixed After Six Months

2026-08-19T01:39:00.451-07:00

Diablo II: Resurrected players on PlayStation may finally be able to identify items without the game briefly reconsidering its existence.

For roughly six months, PS4 and PS5 players have reported an irritating offline hitch introduced around the Reign of the Warlock 3.0 update.

Talk to Deckard Cain.

Freeze.

Use the Horadric Cube.

Freeze.

Enter a portal.

Freeze.

Buy something from a vendor.

You get the idea.

Now, following the August 18 Patch 3.3 rollout, several of the players who spent months documenting the issue say the stutter appears to be finally fixed.

The Problem Started With the Reign of the Warlock Update

The first major PlayStation bug reports appeared on February 12, immediately after Diablo II: Resurrected's 3.0 update.

Players on both the native PS5 version and the PS4 version running through backward compatibility reported short freezes while playing completely offline.

One of the easiest ways to reproduce the problem was having Deckard Cain identify multiple items.

The game would briefly freeze for roughly 0.2 to 0.3 seconds.

But Cain was only the beginning.

Players eventually reproduced similar hitches while entering portals, changing areas, leveling up, using the Cube, interacting with vendors and during ordinary gameplay.

Most importantly, players reported the issue even on characters that did not own or use Reign of the Warlock content.

The expansion may have arrived with the update.

The hitching apparently came free.

Autosaves and Transactions Became the Main Suspect

Over the following months, the PlayStation community became impressively forensic about the problem.

One player recorded the Cain identification freeze frame by frame and spotted a brief message appearing during the hitch:

Waiting For Confirmation Of Transaction.

That led players to suspect the visible Cain freeze was only one symptom of a broader slowdown involving transactions, validation or game-state saving.

Later testing seemed to support that theory.

Players reported the same hitch around:

Cain identification
Manual item identification
Horadric Cube transmutation
Moving items into the Cube
Vendor purchases and sales
Gambling
Entering portals
Area transitions
Autosaves
Some item drops and gameplay events

That is unfortunately most of Diablo II.

Gambling Made the Problem Almost Comical

By August, players had found an especially effective demonstration.

Gambling.

Normally, players can rapidly buy items from the gambling screen and fill an inventory in seconds.

With the PlayStation hitching problem, each purchase could briefly lock the game before the next input registered.

Repeated purchases made the stutter occur again and again, turning an ordinary gambling session into a sequence of tiny pauses.

The same thing reportedly happened while repeatedly cubing gems.

Insert three gems.

Transmute.

Hitch.

Repeat.

The Horadric Cube already has enough opportunities to disappoint you without requiring a loading break between them.

The Problem Was Especially Uncomfortable in Hardcore

A menu hitch is annoying.

A gameplay hitch is potentially lethal.

Several players specifically stopped playing Hardcore offline characters because stalls could also happen during combat, immediately after entering an area or around portal transitions.

A fraction of a second is usually irrelevant.

In Diablo II Hardcore, a fraction of a second standing beside the wrong pack can become an obituary.

That is why the issue continued generating console bug reports long after smaller visual glitches would normally have been forgotten.

Several Earlier Updates Helped, but Didn’t Finish the Job

Players reported improvements during the months after launch, but the underlying hitch never completely disappeared.

In March, some players felt freezes had become shorter.

Others still reproduced them consistently.

Reports continued through April, May, June and July.

Even in August, PlayStation players were still opening new threads about offline hitching, freezing and autosave-related stalls.

The issue had effectively survived multiple patches and most of Reign of the Warlock's first six months.

Then Patch 3.3 Arrived

Patch 3.3 began rolling out on August 18 as part of the run-up to Diablo II: Resurrected Ladder Season 15.

Blizzard's published notes do not contain a line saying:

Fixed the six-month PlayStation offline hitch.

Instead, the Bug Fixes section simply begins with “Various stability and performance improvements.”

Apparently one of those improvements may have been doing quite a lot of work.

Players Immediately Started Stress-Testing It

One of the players who had spent months documenting the problem downloaded the new patch on August 18 and began testing the old triggers in real time.

Enter the Tristram portal.

No hitch.

Return to town and ask Cain to identify items.

Instant.

Use the Horadric Cube.

No chop.

Visit Gheed.

No obvious delay.

The player concluded that the issue finally appeared to be resolved.

Another PS5 player confirmed the result early on August 19.

A separate PS4 Slim player also reported no freezes after updating.

And another long-time reporter said Cain identification, Cube stuttering and ordinary gameplay hitching all appeared fixed.

This Is More Than One Happy PS5 Owner

That distinction matters.

If one person said their game suddenly felt smoother, we would not have much of a story.

But several people who had previously reproduced the problem across PS4, PS5 and PS5 Pro are now independently reporting that their known triggers no longer cause the same stalls.

That is strong community evidence that something meaningful changed in the new patch.

It is still not the same thing as Blizzard officially confirming the precise fix.

Patch 3.3 Is Turning Out to Be More Interesting Than Expected

The console fix is not the only seemingly small Patch 3.3 change producing a much larger practical effect.

We have already covered how a Miasma Chain collision fix appears to have made Abyss Warlock dramatically stronger in early player testing.

The patch also reduces Worldstone Shard and Ancient Statue drop rates, while improving Rare-or-better drops from higher Herald tiers.

It makes Latent Sunder Charms harder to obtain through Magic Find.

And Season 15 will bring eight older Ladder-only items into Non-Ladder.

Patch 3.3 looked fairly small.

Its consequences are proving considerably larger.

Season 15 Could Arrive With PlayStation in Much Better Shape

The timing is excellent.

Ladder Season 15 starts August 21 at 5 p.m. PDT, with European players joining on August 22 at 2 a.m. CEST.

That gives PlayStation players a few days to test the new patch before deciding whether they trust another Hardcore character with it.

If the early reports hold up, console players may finally be entering a new Ladder without the constant fear that talking to Deckard Cain will briefly freeze the universe.

We Should Still Call This “Appears Fixed” for Now

There is one final caveat.

Blizzard has not explicitly identified the PlayStation offline hitch in the Patch 3.3 notes.

The company only lists general stability and performance improvements.

So we cannot say with absolute certainty which technical change solved the problem, or whether every edge case on every PlayStation configuration has disappeared.

But this is the strongest evidence players have had in six months.

The same people who were reproducing Cain freezes, gambling delays, Cube stalls and portal hitches days ago are now trying those same actions and reporting smooth gameplay.

Six months.

Dozens of reports.

Multiple patches.

And finally, Deckard Cain may once again identify your inventory without requiring Diablo II to stop and think about it first.

Sources

Diablo II: Resurrected Forums: PS5 Offline Stuttering/Hitching Has Ruined My Favorite Game

Diablo II: Resurrected Forums: PS4/PS5 Offline Hitching — Gambling Exposes Severity

Diablo II: Resurrected Forums: PS5 & PS4 Console — Freeze When Deckard Cain Identifies Items

Blizzard Entertainment: Diablo II: Resurrected Ladder Season 15 Coming Soon / Patch 3.3 Notes

Diablo Immortal Players Say Normal Gems Are Disappearing During Salvage and Quick Craft

2026-08-19T01:28:31.956-07:00

There are few things in Diablo Immortal more satisfying than finally ranking up a Normal Gem.

There are also few things less satisfying than watching the gems required for that upgrade disappear without producing anything.

Players are now reporting two separate cases where valuable Normal Gems apparently vanished during completely ordinary inventory actions.

One involved salvaging a Set item.

The other involved using Quick Craft at the Jeweler.

Blizzard has not confirmed that the two incidents share the same cause, or even that they are manifestations of the same bug.

But if you are sitting on high-rank Normal Gems, this may be a good week to click things slightly more carefully than usual.

A Rank 8 Topaz Disappeared After Salvaging a Set Item

The first report appeared on August 16.

A player had just reached Paragon 1600 and was replacing some Inferno XIII Set equipment.

They salvaged a Restitution glove at the Blacksmith and converted it into a Wisp.

Afterward, one of the Rank 8 Topaz gems associated with their equipment was gone.

The player says they checked their inventory, stash and other equipped items and could not find it anywhere.

That is a particularly painful disappearance because high-rank Normal Gems represent a considerable amount of accumulated lower-rank gems.

The player was also close to having enough resources for another Rank 9 Topaz.

Instead, one of the Rank 8 building blocks apparently entered the Void.

Possibly the most expensive inventory tab in Sanctuary.

Then 81 Aquamarines Disappeared During Quick Craft

A day later, another player added a completely different Normal Gem problem.

They attempted to use Quick Craft at the Jeweler to turn 81 Rank 1 Aquamarines into a Rank 5 Aquamarine.

According to the report, all 81 gems disappeared from the inventory.

No Rank 5 Aquamarine appeared in their place.

The player later created a dedicated bug report and provided their device information, character UID and exact number of missing gems.

They also noted that at least some of the Aquamarines had effectively been acquired using paid services, making the loss considerably more than an inconvenience.

The Player Thinks Mixed Bound and Unbound Gems May Matter

The Quick Craft report became more interesting after other forum users tried to understand the sequence.

The affected player says they had previously crafted Rank 3 and Rank 4 gems without any problems.

The failure happened specifically while attempting Rank 5.

They later suggested a possible reproduction method:

Have exactly 81 Rank 1 gems.
Use a mixture of bound and unbound gems.
Select Rank 5 at the Jeweler.
Use Quick Craft.

According to the player, that is the situation developers should test.

Blizzard has not confirmed that this sequence reproduces the problem, so players should treat it as community troubleshooting rather than an established technical explanation.

These May Be Two Completely Different Bugs

It would be tempting to declare that Diablo Immortal has one giant Normal Gem deletion bug.

We do not have enough evidence for that.

The Topaz disappeared after Set-item salvage.

The Aquamarines disappeared during crafting.

Those are entirely different systems.

The only obvious connection is the end result:

Player had gems.

Player performed a normal game action.

Player no longer had gems.

That is enough reason to pay attention, but not enough to claim a shared technical cause.

Normal Gems Have Disappeared Before

There is some uncomfortable history here.

In May 2025, another Diablo Immortal player reported losing a Rank 7 Citrine while switching equipment and Armory loadouts.

The same player said they had previously lost two Rank 7 Sapphires and managed to recover those through an older saved Armory configuration.

They suspected another gem may have disappeared when a Set item was salvaged and the socketed gem failed to return correctly.

That older thread also linked to previous reports involving Normal Gems disappearing during Armory and gear-switching sequences.

Again, there is no evidence that the 2025 cases and this week's incidents have the same underlying cause.

But Normal Gems apparently finding creative exits from the inventory is not an entirely new complaint.

That Matters Because Normal Gems Are Painfully Expensive to Replace

Normal Gems are not decorative pocket gravel.

High-rank gems represent enormous quantities of lower-rank gems accumulated through regular play, events, the Marketplace and other sources.

Players have repeatedly complained that Normal Gem progression is one of Diablo Immortal's harder long-term systems to catch up on, particularly for newer accounts.

That is why losing a Rank 8 gem feels considerably worse than accidentally salvaging another random Legendary shoulder.

One can be replaced after some farming.

The other represents a small geological era.

Diablo Immortal Has Had a Rough August for Expensive Items

The Normal Gem reports arrive during an awkward run of inventory and premium-system problems.

We just covered another player who says 6,000 Eternal Orbs were spent on an unusable Celestial Serpents cosmetic upgrade.

That followed the earlier 4,500-Orb Fanal of Hope purchase that Blizzard is investigating.

Another player says the Temptation's End dye system still would not change colors after a 10,960-Orb setup.

And underneath all of this, players are still adapting to the Inferno XIV Loyalty Point conversion and new Essence progression cycle.

None of those problems necessarily share a cause.

But August has been an unusually educational month for the importance of checking what happened after pressing Confirm.

For Now, Manual Crafting May Be the Safer Option

There is no confirmed Blizzard workaround for either new Normal Gem report.

Still, players concerned about losing expensive gems may want to take a few temporary precautions until the situation becomes clearer.

If you are salvaging Set equipment containing valuable Normal Gems, verify where those gems are before and after the salvage.

If you are combining a large pile of Rank 1 gems, particularly a mixture of bound and unbound gems, manually ranking them in smaller steps may be worth considering instead of immediately using Quick Craft to Rank 5.

And screenshots of your inventory before performing expensive operations are rarely a terrible idea when reporting a potential item-loss bug.

That advice is precautionary.

It is not confirmation that either process is universally unsafe.

Gems Should Become Bigger Gems, Not No Gems

Diablo Immortal is built around upgrading things.

Equipment becomes better equipment.

Essences become builds.

Small gems become larger gems.

That last progression step becomes considerably less attractive when 81 Aquamarines apparently become air.

For now, we have two current reports involving two different systems and some older history suggesting Normal Gem disappearances have happened before.

What we do not yet have is a Blizzard explanation.

Until then, perhaps treat that Quick Craft button with the respect normally reserved for a suspicious Horadric Cube.

Sources

Diablo Immortal Forums: Normal Gems Disappeared After Salvaging Set Item

Diablo Immortal Forums: Aquamarine Disappeared After Quick Craft at Jeweler

Diablo Immortal Forums: Normal Gem Gone

Another Diablo Immortal Player Bought an Unusable Cosmetic — This One Cost 6,000 Orbs

2026-08-19T01:21:56.824-07:00

Diablo Immortal has another expensive cosmetic problem.

And this time the number is even larger.

A player says they spent 6,000 Eternal Orbs on an upgraded Celestial Serpents cosmetic after the option appeared in-game.

After completing the purchase, they say they received no cosmetic or anything else they could actually use.

The report was filed on August 19 and directly references the recent case where another Diablo Immortal player spent 4,500 Eternal Orbs on a Fanal of Hope enhancement that required a base cosmetic they did not own.

One case can be an unfortunate edge case.

Two expensive cosmetic reports within days of each other start making the purchase logic considerably more interesting.

The Player Spent 6,000 Orbs on Celestial Serpents

The new report is remarkably short and direct.

The player says Diablo Immortal showed them the option to purchase the Celestial Serpents upgraded cosmetic for 6,000 Eternal Orbs.

They bought it.

Then nothing useful appeared.

The player is using an iPad and filed the issue under Diablo Immortal's iOS Bug Report section.

At the time of writing, Blizzard has not publicly responded to this specific 6,000-Orb report.

Celestial Serpents Has a Separate Upgrade System

The important context comes from Blizzard's original Celestial Serpents announcement.

The cosmetic debuted through the Lunar New Year Phantom Market in January 2025 and included an optional upgrade system called Tempering & Refining.

Tempering changes the appearance of the gilded serpents and alters the color of Primary Attacks.

Polishing adds a special finisher animation when killing Elites or bosses.

But Blizzard's wording contains a particularly important condition:

The Celestial Serpents cosmetic must already be unlocked before players can spend Eternal Orbs to Temper and Polish it.

That makes the new report difficult to dismiss as someone simply misunderstanding what an upgrade does.

If a player does not meet the requirement, the more important question becomes why the 6,000-Orb purchase option appeared at all.

We Don’t Yet Know Whether the Player Owns the Base Cosmetic

There is an important difference between this report and the earlier Fanal of Hope case.

The new player has not yet explained whether they already own the Celestial Serpents base cosmetic, a portal or another component from the original set.

So we cannot say the exact same bug has happened again.

The failure could involve account ownership detection.

It could involve delivery of the upgraded cosmetic.

It could involve another problem entirely.

Right now, all we know is that the game accepted 6,000 Eternal Orbs and the player says nothing usable arrived.

That is enough to warrant investigation.

Not enough to diagnose the patient.

The Player Links Directly to the 4,500-Orb Case

What makes the timing particularly awkward is that the new player explicitly connects their experience with the 4,500-Orb Fanal of Hope case we covered last week.

In that earlier report, a player purchased a cosmetic enhancement believing they were buying usable cosmetic content.

They later discovered that the purchase only modified the Fanal of Hope base armor cosmetic.

They did not own that armor.

Worse, the base cosmetic was no longer obtainable.

The player therefore had 4,500 Orbs tied up in an upgrade for something they could not currently acquire.

Blizzard Is Already Investigating the Earlier Case

The previous story eventually reached Blizzard's development team.

A Blizzard representative responded publicly on August 12 and said the team was investigating the bug and would communicate what steps it planned to take.

That was significant because Customer Support had previously told the player it could not reverse the purchase, refund the Orbs or provide another form of compensation.

The new 6,000-Orb reporter had actually already appeared in that older thread on August 18, saying they had encountered the same general type of problem and had not heard back regarding their support ticket.

Less than a day later, they created a dedicated Celestial Serpents bug report.

This Makes Purchase Validation More Important

We still do not know whether both cases have the same technical cause.

But they raise the same basic design question.

Should Diablo Immortal allow an account to purchase an expensive cosmetic enhancement unless the game has verified that the enhancement will actually be usable?

The cleanest version of the system would be boring.

Own the base cosmetic?

Purchase button available.

Do not own it?

Purchase button disabled.

That would eliminate a considerable amount of customer-support archaeology.

Premium Cosmetic Systems Are Becoming More Complicated

The issue is particularly relevant because Diablo Immortal has recently been expanding cosmetic customization aggressively.

We recently covered the new Temptation's End dye customization system, which costs 4,500 Orbs just to unlock.

Then another player reported that their full Temptation's End dye setup still refused to change colors after they had spent 10,960 Orbs.

Now we have Celestial Serpents and another 6,000-Orb purchase dispute.

None of those reports proves that Diablo Immortal's entire cosmetic system is broken.

But the more layers Blizzard adds to premium cosmetics, the more important it becomes that ownership requirements, upgrade dependencies and purchase results are absolutely clear.

6,000 Orbs Should Probably Produce Something

There is no Blizzard response on the new Celestial Serpents report yet.

There is also not enough information to say the player definitely encountered the same ownership bug as the Fanal of Hope buyer.

For now, this remains one newly documented case.

But it arrives while Blizzard is already investigating another expensive unusable-cosmetic purchase.

That makes it worth watching.

Because premium cosmetic systems can be complicated.

Temper.

Polish.

Refine.

Upgrade.

Change colors.

Add finishers.

Fine.

But after 6,000 Eternal Orbs leave the account, the next step should probably not be:

Open a bug report.

Sources

Diablo Immortal Forums: 6000 Eternal Orbs Spent on Unusable Cosmetic

Diablo Immortal Forums: 4,500 Eternal Orbs Spent on Unusable Cosmetic

Blizzard Entertainment: A Gilded Dawn — Tong Shi's Renewal

Diablo 4 Players Are Finishing Their Entire War Plan — Then Getting Stuck at 9/10

2026-08-19T01:06:09.097-07:00

Diablo 4's War Plans are supposed to reward you for completing endgame activities.

Some players have discovered a slightly less satisfying final objective.

Finish everything.

Then stare at 9/10 forever.

A long-running Diablo IV bug report describes War Plans becoming permanently stuck one level short of completion even after every available activity on the board has been maxed out.

The problem was first reported in June and is still receiving fresh reports on August 19.

For affected players, the missing rank means they cannot unlock the final War Plan reward despite apparently having nothing left to complete.

Every Activity Is Finished, But the War Plan Still Wants One More

The original report came from a Barbarian player on the Asia servers.

They completed every activity shown on the right side of the War Plan tree.

The activities were done.

The points were spent.

But the overall War Plan remained at Rank 9/10.

The interface still said another activity or skill point was required to reach the final rank.

There was only one minor problem.

There were no activities left.

The player tried restarting Diablo 4, restarting Battle.net, verifying the game files and logging out and back in.

Nothing changed.

Yes, War Plans Really Can Reach 10/10

One of the first questions in the bug thread was whether 9/10 might simply be the intended maximum because War Plans begin at Rank 0.

Other players quickly ruled that out.

War Plans can reach 10/10, and the UI continues showing unfinished progression after Rank 9 for affected players.

Later reports are even more explicit.

One player finished the entire War Plan and received the associated completion achievement, but the board itself remained at 9/10.

Another reported every activity sitting at 7/7 while the War Plan remained one rank short.

Achievement complete.

Activities complete.

War Plan apparently unconvinced.

Players Think Double Rank-Ups May Be Losing a Point

The most interesting community theory appeared after players began comparing how their War Plans progressed.

Several suspect the bug happens when an activity gains two ranks at once around the same time the overall War Plan should gain a level.

One player suggested that doing two Nightmare Dungeon Escalations or two Greater Helltide upgrades together may cause the system to count only one of the activity ranks.

A later player described what appears to be the same problem in more detail.

According to their testing, if an activity double-ranks while the War Plan itself is close to leveling, one activity rank may fail to count toward the overall total.

Nothing looks obviously broken at the time.

The problem only becomes unavoidable weeks later, when every activity is maxed and the missing point can no longer be earned.

That explanation has not been confirmed by Blizzard.

But it would explain why the bug feels like it appears at the end even though the actual mistake may have happened much earlier.

Another Theory Points to the First Activity Rank

There is not complete agreement on the cause.

Another player testing a fresh character noticed that the first rank gained in one activity tree appeared not to contribute an expected point.

So the community currently has at least two possible explanations:

A double activity rank-up causes one point to be skipped.
An early activity rank sometimes fails to count correctly.

Neither theory has received official confirmation.

What players do agree on is the outcome.

Eventually the board reaches a state where everything is finished but the numbers no longer add up.

The Bug Is Still Happening on August 19

The original thread did not disappear after June.

Players reported the same problem throughout July and August.

On August 3, one player said they had finally maxed their War Plan after several weeks of progression and ended up permanently one point short.

More reports followed on August 11.

And early on August 19, another Barbarian player confirmed the same issue again.

Interestingly, that player said their Warlock did not have the problem.

They wondered whether the difference might relate to one character starting Seasonal while the Barbarian began on Eternal.

That is only speculation, but it adds another variable worth investigating.

War Plans Have Already Needed Plenty of Fixes

This is not Diablo 4's first argument with the War Plan system.

Blizzard has already fixed multiple problems involving War Plan progression, boss spawns, activity tracking and rewards since Lord of Hatred launched.

We previously covered an Infernal Hordes War Plan bug that could completely block progression, which Blizzard later addressed.

We have also been following the Ultimate Nemesis party loot problem, where groups report completing the final encounter only for some players to receive no proper reward.

Blizzard's official patch notes include numerous War Plan fixes, from Nemesis Lairs failing to trigger to activity icons displaying incorrectly and campaign states being evaluated inconsistently between party members.

The system is clearly complicated.

Unfortunately, Rank 9 apparently still knows how to count to ten about as well as a Fallen.

This Is Another Progression Bug With No Way Forward

The reason this one matters is not simply that the UI displays the wrong number.

The final rewards remain locked.

There is no additional activity to grind.

Reassigning points reportedly does not solve it.

Restarting does not solve it.

And because every activity is already at maximum rank, the player has no obvious way to generate another progression event and force the missing point to appear.

That puts it in the same unpleasant category as several progression issues we have covered recently.

Some Eternal characters still cannot access the campaign skip they should have unlocked.

Players can become soft-locked during the Secret Cow Level quest despite completing the required steps.

And even 65/65 Skovos exploration can leave the Amazonian Charge mount locked for some accounts.

The common theme is particularly frustrating:

The player has already done the work.

The game just has not finished counting it.

Blizzard Has Not Announced a Specific Fix Yet

Blizzard's current patch notes contain plenty of War Plan fixes, but we have not found a published correction specifically addressing the 9/10 progression issue.

The main bug thread is also still active today.

That does not mean Blizzard is not investigating it.

Bug reports can be tracked internally without receiving a public developer response.

But from the player's perspective, there is currently no confirmed fix or reliable workaround.

Weeks of Grinding Should Probably Add Up to Ten

War Plans were introduced with Lord of Hatred as a way to give Diablo 4's endgame more structure, allowing players to customize and progress through chains of activities after finishing the expansion campaign.

That structure only works if the progression system remembers all the progression.

Players reporting this bug are not asking for free levels.

They are not asking Blizzard to reduce the grind.

They have already finished the grind.

They would simply like:

Seven out of seven.

Plus seven out of seven.

Plus everything else completed.

To eventually equal ten out of ten.

Sanctuary has more complicated mathematics than that.

This should not be one of them.

Sources

Diablo IV Forums: War Plans Level Stuck at 9/10 — Missing Skill Point After Completing All Activities

Blizzard Entertainment: Prepare for the Reckoning — Lord of Hatred Draws Near

Blizzard Entertainment: Diablo IV Patch Notes

Diablo 2 Patch 3.3 Fixed One Warlock Bug — Players Say It Made Abyss Ridiculously Strong

2026-08-19T00:54:54.180-07:00

Diablo II: Resurrected Patch 3.3 contains one very innocent-looking Warlock bug fix.

Miasma Chain no longer collides with friendly and neutral units.

That is it.

No giant damage multiplier.

No doubled skill coefficient.

No developer note announcing that Hell Diablo should immediately begin updating his will.

And yet, less than a day after Patch 3.3 went live, Warlock players are already reporting that the fix may have given the Abyss Warlock a much larger practical damage boost than anyone expected.

Miasma Chain Was Hitting Things It Wasn’t Supposed To

Blizzard's official Patch 3.3 notes describe the change very simply:

Miasma Chain had missile collision with friendly and neutral units. That has now been fixed.

On paper, this is quality-of-life.

Miasma Chain projectiles should reach enemies instead of colliding with things that are not actually trying to kill you.

In practice, however, Miasma Chain is one of the main single-target damage tools in Abyss Warlock builds.

And if those chains are suddenly reaching bosses more reliably, the difference can be much larger than the patch note makes it sound.

Players Say Hell Diablo Is Melting

The first post-Patch 3.3 testing is already raising eyebrows.

One player on Blizzard's forums described the new Abyss Warlock performance as so overwhelming that it becomes difficult to consider starting Season 15 with another character.

Another player tested the build against Hell Diablo and reported that the boss went down extremely quickly after stacking a large number of Miasma Chains around his spawn point.

The important detail is the gear.

The player described using relatively inexpensive equipment with only around +5 total skills and no skill Grand Charms.

That is hardly the sort of setup where Diablo should evaporate because somebody looked at him aggressively.

This Is Really a Miasma Chain Story

Calling this an “Abyss buff” is slightly misleading.

Blizzard did not actually buff Abyss in Patch 3.3.

The change affects Miasma Chain.

But Abyss Warlocks already commonly use Miasma Chain as part of the same build, particularly against bosses and tougher targets.

That relationship was obvious even before Patch 3.3.

Earlier Hardcore testing from Season 14 described Abyss as excellent AoE damage and crowd control, while Miasma Chain became the real heavy hitter against bosses and enemies that survived the initial Abyss damage.

So if Patch 3.3 has substantially improved Miasma Chain's ability to connect with a target, the entire Abyss package benefits.

The skill did not become stronger mathematically.

It simply became better at actually delivering the mathematics to Diablo's face.

Abyss Was Already Very Strong

This is the other reason the early reports matter.

Abyss was hardly waiting for Blizzard to rescue it.

Players were already calling it one of the strongest Warlock leveling tools during Season 14 because it combines several unusually useful properties:

Strong area damage
Magic damage, avoiding many common immunities
Large-area crowd control
Continued scaling through synergies
Safe off-screen targeting

One Hardcore player documented beating Hell Baal at level 78 with modest equipment while praising Abyss for handling dangerous enemies such as Gloams and Dolls.

That makes Patch 3.3 potentially dangerous from a balance perspective.

You are not fixing the broken steering on a weak build.

You may be fixing the broken steering on something that was already driving extremely fast.

Season 15 Starts in Just a Few Days

The timing could hardly be better for build experimentation.

Patch 3.3 is already live, but the actual Diablo II: Resurrected Season 15 Ladder does not begin until August 21, or early August 22 for European players.

That gives the community a few days to test Abyss and Miasma Chain before everyone begins again from level one.

And suddenly the Warlock starter question becomes much more interesting.

If this performance survives deeper testing, Abyss could become one of the obvious early Season 15 choices.

Patch 3.3 Is Already Changing the Season 15 Meta

The Miasma Chain fix is only one part of a surprisingly consequential patch.

We have already covered how Patch 3.3 makes Sunder Charms harder to obtain, while also changing how Magic Find interacts with some drops.

Blizzard is also reducing Worldstone Shard and Ancient Statue drop rates, which will affect how players approach the Reign of the Warlock endgame.

At the same time, eight older Ladder-only items are moving into Non-Ladder, while the newly adjusted Season 15 items remain part of the fresh Ladder economy.

Blizzard even changed Manald Heal from Faster Run/Walk to Faster Cast Rate shortly before the patch arrived.

Season 15 looked relatively modest on paper.

The details are doing quite a lot of work.

Warlock Has Already Changed Diablo II More Than Expected

When Reign of the Warlock arrived, adding an entirely new class to Diablo II was already a fairly extraordinary event.

The class has since become deeply connected to the game's expanded endgame, including Terror Zones, Heralds and the Colossal Ancients pinnacle encounter.

Patch 3.3 now shows how even tiny mechanical fixes can change that ecosystem.

A projectile collision bug sounds boring.

Until removing it allows twenty poisonous chains to stop colliding with somebody's goat and start colliding with Diablo.

Don’t Call Abyss Broken Yet

There is still a very important caveat.

These are early community tests.

Blizzard has not said Abyss Warlock is overpowered after Patch 3.3.

We do not yet have large-scale Season 15 performance data, fully optimized comparisons or enough testing across player counts and endgame encounters to declare a definitive new meta.

Pre-casting large numbers of Miasma Chains at a known boss spawn is also an unusually favorable scenario for the skill.

Hell Diablo standing patiently where twenty chains are waiting for him is not necessarily representative of every fight in Diablo II.

It is, however, representative of a very bad morning for Diablo.

One Bug Fix May Have Changed the Best Season 15 Starter Conversation

The interesting part is that nobody needed a giant Warlock balance patch to create this discussion.

Blizzard fixed one collision problem.

Miasma Chain started behaving more like players expected it to behave.

And suddenly the community is asking whether one of the strongest Warlock builds just became dramatically better.

That is exactly the sort of interaction worth watching before Ladder Season 15 begins.

If the current results hold up, players may remember Patch 3.3 less for its item tweaks and drop-rate changes than for one wonderfully understated line buried under Bug Fixes.

Fixed an issue where Miasma Chain had missile collision on neutral and friendly units.

Diablo may eventually request that Blizzard puts the bug back.

Sources

Blizzard Entertainment: Diablo II: Resurrected Ladder Season 15 Coming Soon

Diablo II: Resurrected Forums: 3.3 Abyss Warlock Has Become Too Strong

Diablo II: Resurrected Forums: Abyss Warlock After Beating Hell Baal in Hardcore

Diablo Immortal Player Says a 10,960-Orb Dye Setup Won’t Actually Change Colors

2026-08-17T23:55:50.851-07:00

Diablo Immortal recently added proper dye customization to Temptation’s End.

One player says they have now discovered an unfortunate limitation.

The colors refuse to change.

A new Android bug report says the player unlocked every available dye option for the Temptation’s End cosmetic, including the variable color controls, only to find that the outfit continues displaying its default appearance regardless of which colors are selected.

The player estimates the complete dye setup cost 10,960 Eternal Orbs for that cosmetic.

That is a great deal of premium currency for a color picker currently behaving like a decorative button.

Blizzard Added Temptation’s End Dyeing on August 12

The dye system arrived with Diablo Immortal’s August 12 update.

Blizzard officially added color customization for both Temptation’s End and the Temptation’s End Collector’s Edition, allowing players to unlock expanded color options for 4,500 Eternal Orbs.

We covered that initial price in our look at Diablo Immortal’s new 4,500-Orb dye customization system.

That 4,500-Orb figure is the feature unlock Blizzard advertises.

The player behind the new bug report says continuing to unlock the full range of dye options, including the variable color bar, brought the total to 10,960 Orbs per cosmetic.

And after doing that, Temptation’s End apparently remained exactly the same color.

No Matter Which Color Is Selected, It Stays Default

The report was filed on August 16 by a player using a Samsung Galaxy S26 Ultra running Diablo Immortal version 5.0.0.

Diablo 4 Lowered the Skovos Requirement — Some Players Still Can’t Get the Mount

2026-08-17T23:50:48.039-07:00

Diablo 4 fixed one of Skovos' most irritating exploration problems.

Then apparently forgot about some of the players who had already finished it.

The No Island Unturned achievement originally asked players to discover 67 areas in Skovos. Unfortunately, many players reached 65/67 and discovered there did not appear to be another two areas to find.

The requirement has since been changed to 65/65.

Problem solved.

Except players who had already explored those 65 areas before the change say the achievement can remain stuck at Not Started, preventing the associated Amazonian Charge mount from unlocking.

The Original Problem Was 65/67

The main bug report dates back to July 5.

The player had fully explored Skovos on Eternal Softcore and then repeated the process on Eternal Hardcore.

Both times, the map stopped at 65/67.

After Diablo 4 changed the requirement to 65/65, the exploration counter correctly updated.

The achievement did not.

The player says No Island Unturned remained incomplete despite the map now showing full exploration, which also meant the Amazonian Charge reward never arrived.

Other players immediately reported the same thing.

One described the challenge as showing Not Started despite all of Skovos being visible.

Another confirmed the problem still existed on July 17 after completing the regions during the earlier 65/67 bug.

65/65 Apparently Isn’t Enough for Some Accounts

A separate Technical Support report from July 29 describes the same situation in even simpler terms:

Exploration Progress: 65/65.

No Island Unturned: incomplete.

The player had also completed the Lord of Hatred campaign on both Softcore and Hardcore and said exploration was the only remaining challenge preventing full completion.

By August 17, the issue was still being reported.

One player said they had 65/65 on both Softcore and Hardcore before the fix and still had not received retroactive credit.

That makes the current problem less about discovering Skovos.

Players already did that.

The game just needs to notice.

The Likely Problem Is Retroactive Progress

Players have developed a fairly convincing theory.

If you discovered the 65 valid Skovos areas after the requirement changed, the final area can trigger the achievement normally.

If your account already had all 65 areas discovered beforehand, there may be no new exploration event left to trigger the achievement check.

That would explain why some players can reach 65/65 and receive the mount while others remain permanently stuck despite displaying the exact same number.

Blizzard has not publicly confirmed that technical explanation, so it remains a community diagnosis rather than an official cause.

The Community Workaround Is Not Especially Convenient

One workaround suggested by players is completing Skovos exploration on a fresh realm state, particularly Hardcore if the player has not already explored it there.

The idea is simple:

Start with fewer than 65 discovered areas.

Reach 65/65 naturally.

Let the final discovery trigger the achievement.

That has reportedly worked for some players.

It is less helpful for people who already explored Skovos on both Softcore and Hardcore before Blizzard changed the requirement.

Those players have effectively run out of fresh maps to complete.

That is an impressive achievement in itself.

Unfortunately it does not come with the mount.

The Amazonian Charge Is the Part Players Actually Care About

Achievement completion is nice.

The Amazonian Charge is nicer.

The mount is tied to No Island Unturned, which means this is not merely a challenge counter displaying the wrong percentage.

Players are being prevented from receiving a cosmetic reward attached to completing the exploration requirement.

That puts the bug in the same irritating category as several progression problems we have covered recently.

Some Eternal characters still cannot skip the Lord of Hatred campaign despite completing it elsewhere.

Players are still reporting that the Secret Cow Level quest can soft-lock during the Anger step.

And groups reaching Ultimate Nemesis can still finish the fight without everyone receiving the expected loot.

Different systems.

Same sentence:

I did the thing. Where is my reward?

Skovos May Have Another Tracking Problem Too

There is another fresh Skovos-related report from August 17.

One Eternal player says their Skovos World Event Master progress is stuck at 93/100 even after repeatedly killing the Skovos World Boss enough times that they believe the count should have reached 100.

That is currently only a single report, so there is no reason to assume the two problems share the same cause.

But it is another example of Skovos progression apparently not always registering the activity happening directly in front of it.

Season 14 Has Had a Strange Collection of Tracking Bugs

Diablo 4 is currently carrying several bugs where the underlying action seems to work while the progression or stat attached to it does not.

We recently covered a Block Chance problem where Greater Affixes and Masterworking reportedly leave the stat unchanged.

And today we looked at a Transfiguration report where a near-perfect amulet became Unmodifiable without any visible reward.

That is what makes No Island Unturned particularly frustrating.

There is no mystery about whether the player completed the requirement.

The game itself says:

65/65.

Blizzard Needs a Retroactive Check

Players affected by the old 65/67 state are asking Blizzard for a backend or retroactive progression check that recognizes accounts already sitting at 65/65 and grants the missing achievement and reward.

That sounds like the cleanest solution if the community diagnosis is correct.

Do not ask players to rediscover an area that is already discovered.

Do not ask them to create another character.

Do not ask them to explore an island for the third time.

Just look at the counter.

65.

Out of 65.

There are more complicated mathematical problems in Diablo 4.

This probably should not be one of them.

Sources

Diablo IV Forums: No Island Unturned Achievement and Amazonian Charge Mount Not Granted After Skovos Requirement Update

Diablo IV Forums: Unable to Complete No Island Unturned Achievement Despite 65/65 Exploration

Diablo IV Forums: World Boss Kills in Skovos Are Not Being Counted in Eternal

Diablo 4 Players Are Still Getting Locked Out of the Secret Cow Level Quest

2026-08-17T23:44:59.210-07:00

Diablo has spent almost thirty years insisting that there is no cow level.

Diablo 4 has apparently found a new way to preserve the tradition.

There may be a cow level.

You just might not be allowed to reach it.

Players are still reporting that the hidden Secret Cow Level questline can become soft-locked during its Anger step, leaving them unable to obtain the required Amazon Training pieces, Mother’s Rose or activate the final brazier.

The main bug report began back on May 9 and was still receiving new complaints on August 17.

The Anger Step Can Apparently Stop Progressing

The original player had successfully collected and equipped all five pieces of the Amazon Training set.

While waiting for Vasha the Unbroken, they removed the Training Boots because of an inconvenient Fury-draining affix, returned to town and accidentally salvaged them.

That should have been annoying.

Instead, it apparently became permanent.

From that moment onward, Corrupted Amazons stopped dropping replacement Training pieces. The player salvaged the remaining set, restarted the Anger ritual, reacquired the initial helm from the training dummy and cleared multiple Celestia zones.

Nothing.

Vasha also refused to drop Mother’s Rose, and the Temple of Courage brazier remained non-interactable.

The player believes some hidden progression flag may remain set after the game registers the full armor set, preventing the quest from correctly resetting if part of the sequence is interrupted.

Blizzard has not confirmed that explanation.

Other Players Are Getting Stuck in Different Places

The worrying part is how many variations of the same problem have appeared.

One player reported collecting three Amazon Training pieces before a Helltide began, after which nothing except the helmet would drop.

Another said they killed more than 10,000 Corrupted Amazons while trying relogs, Cross Play changes, quest resets and different characters without fixing the problem.

Others successfully collected all five armor pieces but repeatedly killed Vasha without receiving Mother’s Rose.

One player tried the process on three separate alts.

Still no Rose.

At some point this stops being secret-content discovery and becomes bovine bureaucracy.

Moving Items Between Characters Can Make Things Stranger

Players have also discovered that the hidden quest appears unusually sensitive to which character completes each step.

One player eventually obtained the Amazon equipment and Mother’s Rose on a Warlock after their Barbarian became stuck.

They then placed the Rose in the stash and moved it to the Barbarian.

The Barbarian could not light the associated brazier.

Switching back to the Warlock allowed the brazier to activate, but introduced another progression problem afterward.

That player concluded that the safest approach may be completing all three ritual branches on the same character.

Again, that is community troubleshooting rather than confirmed Blizzard guidance.

There Are Workarounds, but They Don’t Work for Everyone

One July player reported a successful recovery without creating another character.

Instead of repeatedly resetting Anger, they completed another ritual branch first, returned to Anger afterward, activated the talisman again, reread the journal, equipped the Amazon Training armor and went directly to Vasha.

This time Mother’s Rose dropped.

Another player confirmed in August that the same workaround fixed their quest.

Unfortunately, later reports say even that method does not always work.

On August 11, one player said they had tried multiple characters, salvaged and refarmed the equipment four times, reread the notebook and restarted Anger repeatedly.

No Rose.

On August 17, the same player returned with a wonderfully concise summary of the entire situation:

They just wanted to moo.

Still no confirmed Blizzard acknowledgement.

Diablo 4 Has Had a Bad Run of Progression Bugs

The Cow Level problem fits an unfortunate pattern we have been following recently.

Just yesterday we covered how some Eternal characters still cannot skip the Lord of Hatred campaign months after players completed it elsewhere.

We have also covered an older progression problem where Diablo 4 removed Elixirs while an old Vessel of Hatred quest still appeared to require one.

And at the endgame, players continue reporting that Ultimate Nemesis parties can complete the encounter only for some members to receive no proper loot.

Different systems.

Same particularly unpleasant result:

The player does what the game asks, and progression simply stops.

Hidden Quests Are Especially Vulnerable to This

A normal quest bug is frustrating.

A hidden quest bug is worse because players are already working without normal guidance.

The Secret Cow Level chain deliberately relies on obscure objects, unusual drops and player experimentation.

When one step fails, it becomes extremely difficult to know whether you have discovered another secret condition or whether the game has simply broken.

Do you need another armor piece?

Did you perform the rituals in the wrong order?

Should Vasha drop something?

Is the brazier intentionally inactive?

Or did a hidden progression flag give up three hours ago?

That uncertainty is entertaining when solving a secret.

It is considerably less entertaining after 10,000 Amazon kills.

Don’t Salvage the Training Set Until You’re Finished

Until Blizzard clarifies the problem, the safest community advice is fairly conservative.

If you are working through the Anger sequence, keep the full Amazon Training set intact.

Try to complete the associated steps on the same character.

And avoid moving or salvaging quest-related items until Mother’s Rose has been used successfully.

Those precautions are based on player reports rather than an official fix, and even following them does not appear to guarantee success.

But they may reduce the chance of ending up in one of the broken states described in the forum thread.

The Secret Cow Level Should Be Difficult to Find, Not Impossible to Finish

There is something wonderfully Diablo about a hidden Cow Level quest requiring players to decipher strange rituals, wear ridiculous equipment and murder suspicious numbers of monsters.

That part should remain obscure.

The quest should feel like something the community collectively uncovers.

But once a player has figured out what to do, the challenge should be completing the secret.

Not determining whether the secret currently works.

Diablo has spent decades telling us there is no cow level.

Diablo 4 apparently added an asterisk.

There is no cow level if Mother’s Rose refuses to drop.

Sources

Diablo IV Forums: Cow Level Anger Step Soft-Locked — Amazon Training Set Drops Stop, Vasha Drops No Mother’s Rose, Brazier Non-Interactable

Diablo 4 Player Says Transfiguration Bricked a Near-Perfect Amulet and Gave Nothing Back

2026-08-17T23:38:16.190-07:00

Diablo 4's Transfiguration system is supposed to be risky.

You take an excellent item.

You put it into the Horadric Cube.

You press the button.

And then you discover whether Sanctuary has decided to reward months of optimization or turn your prized possession into an expensive cautionary tale.

One player says the system has now discovered a third option.

Do absolutely nothing and lock the item anyway.

A fresh August 18 bug report describes a near-perfect Ancestral Legendary amulet becoming permanently Unmodifiable after Transfiguration despite receiving no visible new affix, no Item Quality increase, no Greater Affix upgrade, no Indestructible effect and apparently no other Transfiguration result.

This Was Not a Disposable Amulet

The player, Apokriphos, had already put a considerable amount of work into the item before attempting the final roll.

According to the report, the amulet had an enchanted +4 skill affix, several important Greater Affixes, finished Tempering and Masterworking, a finalized Legendary Aspect and a successful Kullean Transfiguration already applied.

In other words, this was not something picked up during a Helltide and thrown into the Cube because there was nothing interesting on television.

It was an endgame item.

The sort of item where every additional crafting step is preceded by a short conversation with yourself about whether greed is really worth it.

Apparently it was not.

The Final Transfiguration Locked It With No Visible Reward

The player then performed one final normal Transfiguration using Volatile Primordial Dust.

The result was immediate.

The amulet became Unmodifiable.

That part is not unusual. Transfiguration is intentionally capable of permanently locking an item from further modification.

What was unusual was everything that did not happen.

The player reports receiving:

No new affix
No Item Quality increase
No Greater Affix upgrade
No Indestructible result
No visible replacement or additional Transfiguration effect

The item simply became locked.

Bad RNG is one thing.

RNG forgetting to generate the R is another.

Transfiguration Is Already Diablo 4’s Final Gamble

This hurts because Transfiguration sits at the very end of the crafting process.

By the time players seriously consider using it on a valuable item, they may already have invested Enchanting, Tempering, Masterworking and substantial time finding the correct Greater Affixes.

Blizzard has continued integrating Transfiguration into high-end itemization, including Season 14 changes to Mythic crafting and fixes for several Cube interactions. The current patch notes still contain Transfiguration-specific fixes, including preventing non-functional Greater Affixes from being added to Mythic Unique items.

That is why a no-result roll feels different from simply receiving the wrong bonus.

The player was prepared to gamble the item.

The expectation was that the gamble would produce something.

This May Not Be the First Time

There is another reason the new report deserves attention.

A separate bug report from May describes a remarkably similar outcome on another amulet.

That player started with a four-star amulet, performed a basic Transfiguration and watched the item become Unmodifiable and display five stars.

But the player could not identify any actual stat increase or additional Greater Affix afterward.

Their theory was that Transfiguration may have selected an affix that was already Greater or already enhanced, resulting in no meaningful visible improvement.

Blizzard never publicly confirmed that explanation.

But it raises an uncomfortable possibility:

A Transfiguration outcome may occasionally select something that produces no useful change while still consuming the roll and locking the item.

Amulets Have Already Had Transfiguration Problems

This would hardly be Diablo 4's first strange interaction involving amulets and the Horadric Cube.

Players previously reported cases where changing a Legendary Aspect after using a Kullean Tuning Prism caused the Transfigured Aspect to disappear, sometimes leaving the amulet unable to be Transfigured again. Multiple players reproduced that problem in May.

Blizzard has fixed several Cube-related problems since then, but today's report suggests highly invested amulets may still have dangerous edge cases.

That fits a broader pattern we have been watching across Diablo 4's increasingly complicated item systems.

We recently covered how Block Chance may fail to improve through Greater Affixes and Masterworking, despite players investing heavily into the stat.

We have also looked at the enormous damage gap that extreme endgame scaling can create between builds.

Different problems.

Same underlying reality.

Modern Diablo 4 has an extraordinary number of systems stacked on top of each other.

The Risk Is Supposed to Be the Outcome, Not Whether There Is an Outcome

There is an important argument in favor of Transfiguration's brutality.

Endgame gear should probably have some risk.

If players could endlessly reroll every final modification until perfection appeared, there would eventually be very little tension left in the item hunt.

That is part of why Transfiguration has generated so much debate since Lord of Hatred introduced the modern Horadric Cube systems.

And it is also why players have spent so much time debating whether Diablo 4's public testing process catches enough of these interactions before they reach live servers. We recently explored that question in our piece on whether Diablo 4's PTR solves problems or spoils too much before launch.

But risk only feels fair if players understand what they are risking.

Bad affix?

Fine.

Indestructible when you wanted damage?

Painful, but understandable.

Permanent lock with no observable reward?

That feels considerably less like gambling and considerably more like the machine ate your coin.

Season 15 Will Make Item Reliability Even More Important

Season 15 is already preparing another wave of buildcrafting changes through Soul Splinters, Legacy Uniques, Challenge Dungeons and further item-system adjustments.

We came away from the PTR particularly positive about Soul Splinters and their meaningful build tradeoffs.

But adding more interesting build choices also makes reliable item behavior more important.

Players can work around balance.

They can choose a different affix.

They can farm another item.

What they cannot easily plan around is a crafting system occasionally producing no identifiable result.

For Now, This Is Still a Player Report

There is no Blizzard response on the new August 18 thread at the time of writing.

We therefore cannot confirm that the Cube definitely failed to apply an outcome internally.

It is possible something changed that is not immediately visible.

It is possible the system selected an already-maximized or otherwise redundant result.

It is possible there is another explanation entirely.

That is exactly what the player is asking Blizzard to investigate.

But because a similar no-visible-change report exists from May, players with truly exceptional amulets may want to think carefully before using that final normal Transfiguration.

Diablo 4 has always encouraged greed.

The Horadric Cube has historically punished it.

Still, when it eats a near-perfect amulet, the least it can do is leave a receipt.

Sources

Diablo IV Forums: Transfiguration Bricked My Near-Perfect Amulet With No Result Added

Diablo IV Forums: Amulet Transfiguration — Greater Affix Bug?

Blizzard Entertainment: Diablo IV Patch Notes