Diablo 4 Players Say Killing the Fathomless One Too Fast Can Break Saltwind Stronghold

Diablo IV normally rewards you for killing bosses quickly.

Saltwind Stronghold has apparently decided to experiment with a different philosophy.

Players fighting Grigg'sal'tosh, the Fathomless One in Skovos are continuing to report an extremely strange progression problem:

If you kill the boss before its scripted swallow mechanic happens, the Stronghold may refuse to complete.

The Fathomless One can be dead.

The boss arena can be empty.

The fight can still technically be running.

And the player may find themselves trapped on the beach with no way to activate the final Stronghold altar.

The latest report was posted on August 23.

And the workaround is wonderfully backwards.

Stop doing so much damage and let the monster eat you.

The Fathomless One Is Supposed to Swallow You

Saltwind is one of Skovos' three Strongholds and contains one of Lord of Hatred's more elaborate boss encounters.

The Fathomless One is a huge sea creature fought in a confined coastal arena.

But simply reducing its health to zero is apparently not the entire encounter.

During the fight, the boss is supposed to swallow the player.

You then find yourself inside the creature and must destroy four internal targets before being expelled back onto the beach.

After that sequence completes, you can finish the boss normally and cleanse the Stronghold.

It is a pretty memorable mechanic.

Assuming your build gives the boss enough time to perform it.

Players Have Been Killing It Before the Script Happens

The original bug report appeared back on April 29.

A player said they killed the Fathomless One three times in a row, only for the encounter to remain active after its death.

They could not complete the Stronghold and had to leave the area.

Another player immediately suspected the problem:

the boss was dying too quickly.

That theory has continued to fit later reports.

On August 20, another player confirmed the problem was still happening.

Their Fathomless One never swallowed them.

They killed it.

The Stronghold did not complete.

Then, on August 23, another player posted the clearest explanation yet after repeating the Stronghold around five times.

They eventually discovered that killing the boss was not enough.

They had to deliberately wait near its mouth until the swallow mechanic triggered.

Only after completing the internal phase and then killing the boss did the Stronghold finish correctly.

The Current Workaround Is: Let It Eat You

If your Saltwind Stronghold appears stuck, the latest community workaround is surprisingly simple.

Restart the boss encounter.

Then:

• Do not burst the Fathomless One down immediately
• Move around the beach and periodically approach its mouth
• Wait for the boss to swallow your character
• Destroy the four objectives inside the creature
• Allow the game to spit you back into the arena
• Then kill the boss

The player who posted the August 23 solution says the Stronghold completed properly after doing exactly that.

There is also an older workaround that has helped several players:

Lower the difficulty to Normal.

That may sound unrelated.

It probably is not.

Reducing the difficulty also reduces the chance that an endgame character deletes the boss before the scripted phase can happen.

Players on both PC and Xbox have reported that switching to Normal allowed them to complete the encounter.

In other words, Normal may not be fixing the boss.

It may simply be protecting the boss from you.

This May Be Half Bug, Half Terrible Communication

The newest player to solve the encounter argues that this is not technically a bug at all.

The swallow mechanic is simply mandatory.

The problem is that Diablo IV does very little to tell you that.

That distinction is worth making.

If the encounter requires a scripted phase, then waiting for the swallow is part of the intended fight.

But if the game allows the boss to die before that required script executes and then leaves the Stronghold permanently incomplete, the result still behaves like a progression bug from the player's perspective.

The game accepts the boss death.

It simply refuses to accept that you won.

There is also no obvious quest instruction saying:

Do not kill this boss yet. Please stand in front of its mouth until consumed.

That would probably help.

Strong Builds Make the Problem More Likely

This is one of those bugs — or encounter-state problems — that becomes more visible as Diablo IV's power level increases.

A freshly geared character may naturally spend enough time fighting the Fathomless One for every phase to occur.

A highly optimised Torment character may not.

The boss appears.

Cooldowns are pressed.

Several billion damage happens.

The Fathomless One dies before it has finished its theatrical presentation.

The Stronghold script then sits there waiting for a scene involving a creature that is already dead.

It is the same strange design tension we have seen elsewhere in Diablo IV:

Players spend the entire game becoming stronger.

Then one encounter quietly asks them not to be.

Saltwind Matters for More Than One Boss Fight

This is especially annoying because Strongholds are tied into broader Skovos progression.

Completing Saltwind contributes to Renown and full regional completion.

We have already seen how fragile that progression can feel when players reach 65/65 discovered areas and still fail to receive No Island Unturned.

Getting stuck inside one of the region's required Strongholds is therefore more than a funny boss glitch.

It can interfere with players trying to fully clear Skovos.

And because Saltwind unlocks as a permanent Stronghold after completion, anyone hitting the problem is effectively blocked from finishing that part of the map until they repeat the encounter correctly.

The Fathomless One Has Had Other Strange Issues Too

The swallow sequence itself has generated additional reports.

One April player says the camera went completely rogue after the internal section, flying far beyond the arena before eventually returning when the boss died.

So the mechanic clearly involves more scripting than an ordinary health-bar fight.

That makes sequence-breaking more plausible.

And it also explains why brute-forcing the encounter may not always work.

Diablo IV has recently produced several similar situations where progression and scripted events disagree about what the player actually accomplished.

We just covered a Legendary Escalation run that reportedly threw a player out before the final dungeon, while the secret Cow Level's Anger quest can become stuck around hidden item and kill-state requirements.

The individual causes differ.

The result feels remarkably similar.

You did the hard part.

The game is still waiting for paperwork.

There Is Still No Official Fix Listed

The Saltwind thread remained active through August 23.

Players were still able to reproduce the incomplete encounter months after the first April reports.

We could not find a current Blizzard patch note specifically saying the Fathomless One's early-kill progression issue has been fixed.

So if you have not completed Saltwind yet, the safest approach is simple:

Do not immediately vaporise the boss.

Let the swallow phase happen.

Complete the internal objectives.

Then resume the traditional Diablo activity of making the health bar disappear.

If the boss still refuses to cooperate, lowering the difficulty to Normal has worked for multiple players.

Diablo 4 Has Finally Created a Boss You Can Be Too Strong to Kill

There is something almost beautiful about this problem.

ARPG players spend hundreds of hours optimising characters for one purpose.

Kill things faster.

Find another multiplier.

Reduce another cooldown.

Delete bosses before they can move.

Then Diablo IV places one giant sea monster in front of them and quietly says:

Please stop.

The Fathomless One does not need another nerf.

It needs enough time to eat you.

Because apparently in Saltwind Stronghold, the correct boss strategy is:

lose the first phase on purpose.

Sources

Diablo IV Forums: Saltwind Stronghold — Fathomless One

KeenGamer: Diablo IV Lord of Hatred Skovos Region Guide

Icy Veins: Skovos and Saltwind Stronghold Overview

```

Read More

Diablo 4’s Rathma Golem Can Reach Zero Health And Simply Refuse To Die

Diablo 4 players have discovered another boss that considers zero health more of a recommendation than a rule.

Rathma’s Golem can reportedly reach the bottom of its health bar, stop progressing through the encounter and remain permanently alive.

Players can continue attacking.

The Golem can continue standing there.

The quest does not complete.

The campaign does not move forward.

Sanctuary has apparently introduced immortality through missed scripting.

The Golem Can Become Stuck At Zero Health

The long-running bug report began in April 2026 and was still receiving new replies on July 28.

Players describe Rathma’s Golem reaching zero health without triggering the final stage of the encounter.

The boss may stop attacking entirely or remain active while refusing to die.

Continued damage has no effect.

The objective remains incomplete, leaving the player trapped inside a fight that has already been won mathematically.

The health bar has accepted defeat.

The quest script has requested additional documentation.

Killing The Boss Too Quickly Appears To Be The Main Trigger

The most common explanation from affected players is excessive damage.

Rathma’s Golem appears to rely on several scripted phases and dialogue triggers.

If a powerful build removes its health too quickly, the encounter can skip one of those required transitions.

The Golem reaches the final protected state before the quest has processed everything that was supposed to happen earlier.

The game then waits for a trigger that never arrived.

The player waits for the boss to acknowledge having no life remaining.

Nobody moves on.

Modern Builds Can Outrun Older Encounter Scripts

Seasonal characters now have access to stronger equipment, Mythics, Talismans, Charms, Transfiguration and increasingly complicated damage multipliers.

A campaign boss originally designed to survive several seconds inside each phase may now lose enormous sections of health in one attack.

Critical hits, minions and automatic effects can push the fight forward faster than the dialogue and animations can respond.

This is becoming a recurring problem in Diablo 4.

Players recently reported similar behaviour during the Adreona encounter, where too much damage could also leave the boss stuck at low health.

Diablo rewards players for becoming powerful.

The campaign occasionally responds by asking them to calm down.

The Most Reliable Workaround Is To Deal Less Damage

Players who successfully completed the fight recommend using a weak skill and allowing every phase to play out naturally.

Attack until Rathma’s Golem begins a scripted sequence.

Then stop dealing damage.

Wait for dialogue, animations and additional enemies to finish.

Resume attacking only when the next combat phase is clearly active.

One player specifically advised using nothing except a low-damage skill.

This gives the encounter enough time to process each transition before the health bar reaches zero.

The official strategy is therefore:

Bring your strongest hero.

Equip your weakest attack.

Respect the Golem’s preferred theatrical pacing.

Mercenaries Can Keep Damaging The Boss

Stopping personal attacks may not be enough when a mercenary is active.

Companions can continue dealing damage while the player waits for the next phase.

That can push Rathma’s Golem through another threshold before the script is ready.

Several affected players recommend dismissing mercenaries before restarting the encounter.

This reduces uncontrolled damage and makes the fight easier to pace manually.

The mercenary is trying to help.

The campaign would prefer they respect rehearsal breaks.

Minion Builds May Have The Same Problem

Necromancers and other companion-focused builds may struggle to stop damage completely.

Summons can continue attacking after the player releases every button.

Damage-over-time effects can remain active through dialogue sequences.

Automatic abilities may also trigger when enemies appear during the transition.

Players using these builds may need to remove damage-heavy equipment, change skills temporarily or reduce the difficulty-adjusted power of the character before entering the fight again.

The goal is not surviving Rathma’s Golem.

The goal is preventing Rathma’s Golem from dying incorrectly.

Changing Difficulty Can Give The Scripts More Time

Some players report success after changing the game difficulty.

Increasing difficulty gives Rathma’s Golem more health, making it harder to skip several phases with one attack.

For extremely powerful builds, even the higher health pool may not be enough.

Lowering difficulty may also help in some situations by changing encounter behaviour or resetting the instance, though it can make the damage-skipping problem worse.

The important part is restarting the fight under conditions where the boss survives long enough to perform every required sequence.

Diablo 4 has created the unusual situation where making a boss tougher can make it easier to complete.

Playing In A Group Has Helped Some Players

Some reports suggest that joining another player’s instance can allow the encounter to complete normally.

A party member with a weaker character may control the pace more effectively.

The host’s quest state may also produce a clean version of the encounter.

This is not a guaranteed solution.

Groups can create additional damage and make phase skipping even easier if everyone attacks immediately.

Party members should understand the workaround before the fight begins.

Four players politely waiting for the Golem’s dialogue is strange.

Four players deleting it during the opening animation is less useful.

Restarting Alone May Not Fix The Underlying Problem

Leaving the game and restarting the encounter can reset Rathma’s Golem.

It does not automatically prevent the bug from happening again.

If the player returns with the same build and repeats the same burst rotation, the fight may lock at zero health again.

The restart must be combined with slower damage and careful phase control.

Otherwise, the player is simply repeating the bug with a fresh loading screen.

The Bug Blocks Campaign Progression

Rathma’s Golem is connected to required story progression.

When the encounter fails, players cannot simply collect the loot and choose another activity.

The quest remains active.

The next campaign step remains unavailable.

The player must restart and find a workaround before continuing.

This makes the bug considerably more serious than an optional boss failing to drop an item.

The Golem is not guarding a random chest.

It is guarding the rest of the story through technical stubbornness.

The Fight Can Waste A Significant Amount Of Time

Players may not immediately understand why Rathma’s Golem refuses to die.

The health bar shows zero, but the boss remains present.

Some continue attacking for several minutes, expecting another phase or hidden mechanic.

Others search the arena for an interactable object or additional enemy.

Eventually, they discover that the encounter is broken and must be restarted.

The next attempt can fail again if the player does not know that high damage is the likely trigger.

The boss battle becomes a tutorial taught entirely through repeated disappointment.

Hardcore Characters Face A More Dangerous Version

Hardcore players cannot safely experiment with a broken boss indefinitely.

If Rathma’s Golem remains active at zero health, the character may still take damage while the encounter refuses to end.

A normal character can die, restart and try another workaround.

A Hardcore character can be permanently lost.

Affected Hardcore players should leave the encounter immediately if the health bar reaches zero without completing the quest.

They should restart with lower damage, no mercenary and careful phase control.

Permadeath is supposed to punish combat mistakes.

It should not punish the player for defeating the boss before its dialogue catches up.

The Encounter Needs Protected Health Thresholds

The cleanest technical solution would prevent Rathma’s Golem from losing health beyond each required phase threshold.

When the boss reaches a scripted transition, additional damage should stop applying until the sequence finishes.

Once the next phase begins, the remaining health bar becomes vulnerable again.

This system is already common in story-heavy boss fights.

Players may complain about brief immunity periods, but the encounter remains functional regardless of character power.

A few seconds of obvious immunity is better than permanent immunity at zero health.

Excess Damage Could Be Applied After The Transition

Blizzard could also store damage dealt during a protected phase.

When the animation and dialogue finish, part of that damage could be applied to the next stage.

This would preserve the feeling of a powerful build without allowing the player to skip the encounter’s required logic.

The Golem would complete its phase.

The player would keep some value from the massive critical hit.

The quest would stop collapsing under the weight of successful character progression.

The Final Death Trigger Needs A Failsafe

Even if the phase logic fails, Rathma’s Golem should not remain alive indefinitely at zero health.

The encounter needs a secondary check.

If the boss remains at zero health for several seconds, the game should automatically trigger the final sequence or complete the objective.

The system could verify whether required dialogue has occurred and queue any missing events immediately.

A boss absorbing damage at zero life is not a subtle edge case.

The game should recognise that something has gone wrong before the player opens a browser.

A Manual Encounter Reset Would Be Better Than Logging Out

Campaign bosses need a safe reset option.

If the fight becomes stuck, the player could select “Restart Encounter” from the menu.

This would return the character to the entrance and rebuild the boss state without requiring a complete logout.

Hardcore players would gain a safer escape from broken encounters.

The reset could remain unavailable while the boss is functioning normally to prevent abuse.

At present, players use death, teleportation or game restarts as improvised repair tools.

None of those were designed as quest debugging features.

Dialogue Should Not Control Whether The Boss Can Die

Story dialogue can improve an encounter.

It should not be the only thing preventing a boss from entering an invalid state.

If a line is skipped because the player crosses several health thresholds, the quest should queue the missing line or move directly to the appropriate final event.

Combat state should remain authoritative.

When the boss has zero health, the game needs a reliable route toward completion.

The current system appears capable of prioritising an unfinished speech over basic mortality.

Blizzard Has Fixed Similar Progression Problems Before

Previous Diablo 4 patches have addressed several encounters where killing monsters too quickly could block dungeon or quest progression.

Blizzard has also fixed bosses that became unkillable and quest enemies that failed to spawn correctly.

That shows the developer has existing methods for repairing damage-skipped objective triggers.

Rathma’s Golem appears to need the same treatment.

This is not a completely new category of problem.

It is another encounter discovering that Diablo players enjoy doing more damage than the script budget expected.

The Current Patch Notes Do Not List A Rathma Golem Fix

Patch 3.1.2 includes fixes for Rogue damage, Mythic recycling and several other gameplay problems.

The notes do not mention Rathma’s Golem becoming stuck at zero health.

The forum thread was still active on July 28, suggesting affected players continue encountering the problem under the current version.

Blizzard may be investigating the issue without having acknowledged it publicly.

Until a specific fix appears, players approaching the encounter with powerful builds should assume the phase lock remains possible.

The Number Of Reports Makes This More Than A One-Off

The main forum thread has accumulated more than 120 replies and over 10,000 views.

Players across several weeks describe the same core symptom and similar workarounds.

Not every report necessarily shares the exact same cause.

Mercenaries, minions, difficulty and build damage may create different paths toward the broken state.

The repeated zero-health lock is consistent enough to deserve a dedicated fix.

Rathma’s Golem has been refusing death for several months.

That is impressive commitment for an encounter bug.

Players Should Record The Failed Encounter

Affected players should capture video showing Rathma’s Golem reaching zero health without completing the quest.

The recording should include the character class, active mercenary, difficulty and damage sequence used before the lock occurred.

Players should note whether minions or damage-over-time effects continued during dialogue.

They should also report whether a slower attempt completed successfully afterward.

These details can help Blizzard identify which threshold or phase fails.

“Boss cannot die” describes the outcome.

The damage sequence explains how the Golem achieved its administrative immortality.

Workaround: Slow Down And Let Every Phase Finish

Until Blizzard fixes the encounter, the safest method is:

• Dismiss your mercenary before the fight.
• Use a weak basic skill instead of your full damage rotation.
• Stop attacking whenever dialogue or a scripted animation begins.
• Allow summoned enemies and phase mechanics to finish completely.
• Remove some powerful equipment if the boss still loses health too quickly.
• Restart the encounter immediately if the Golem reaches zero health without dying.

This is not an elegant solution.

It has allowed multiple players to continue the campaign.

Powerful Characters Should Not Break The Story

Diablo 4 is built around becoming absurdly strong.

Players spend hours collecting equipment, improving Glyphs and stacking multipliers so bosses die faster.

The campaign needs to support that progression.

Rathma’s Golem should not become unkillable because the character was too successful at killing it.

Blizzard needs to protect the encounter’s phase thresholds, add a zero-health failsafe and provide a safe reset option.

Until then, players may need to approach the Golem with an unfamiliar Diablo strategy.

Stop attacking.

Let the boss finish.

Then kill it slowly enough that the campaign notices.

For more coverage of campaign bugs, boss encounters and Diablo 4’s current technical problems, visit our Diablo 4 archive.

Sources

• Diablo IV Forums: Players report Rathma’s Golem becoming stuck at zero health
• Blizzard: Current Diablo IV patch notes
• Blizzard: Previous fixes for enemies killed too quickly blocking progression

```

Read More

Diablo 4 Players Are Killing Adreona Too Fast For The Campaign To Work

Diablo 4 usually rewards players for killing bosses quickly.

Adreona appears to have negotiated different terms.

Players report that the campaign boss can become permanently stuck on the final sliver of her health bar when a powerful character burns through her phases too quickly.

She continues fighting.

Her health refuses to move.

The encounter never ends.

The campaign cannot progress.

The solution is apparently to stop playing Diablo efficiently and wait patiently for the boss to finish every line of dialogue.

Sanctuary has introduced a damage cap enforced by dramatic timing.

Adreona Can Become Unkillable At Low Health

The problem has been reported by players encountering Adreona during the campaign.

Her human phase can end normally, but the later demon phase may become stuck with only a small amount of health remaining.

Players can continue attacking indefinitely without finishing the fight.

There is no visible immunity object to destroy.

No interaction appears inside the arena.

No quest instruction explains what the player is supposed to do.

Adreona simply continues fighting with the durability of a customer-service hold queue.

The Fight Appears To Depend On Dialogue Triggers

Player testing suggests that the encounter is tied to several health-based dialogue and attack sequences.

At specific points during the fight, Adreona speaks, summons Valkyrie-like spirits and transitions into the next stage of the encounter.

If the player removes too much health before those scripted moments finish, the boss can apparently skip a required trigger.

Her health reaches the final protected threshold.

The game waits for a campaign event that never completed.

The player waits for Adreona to die.

Neither side receives what it wants.

High Damage Can Break The Encounter

The reports consistently point toward excessive damage as the most common trigger.

Powerful seasonal characters can reduce a campaign boss’s health far faster than the original encounter pacing expects.

Critical hits, minions, mercenaries and automatic damage effects can continue attacking while dialogue plays.

The boss may lose an entire phase of health before the associated script catches up.

This is especially easy when returning to campaign content with an established character or playing on a difficulty that no longer matches the build’s power.

The player has built an efficient demon-killing machine.

The campaign responds by refusing to process the kill.

The Main Workaround Is To Deal Less Damage

Players who successfully completed the encounter recommend slowing down dramatically.

Attack Adreona until she reaches a clear phase threshold.

Then stop.

Allow her dialogue to finish.

Wait for the summoned spirit attack or other scripted event to complete.

Only resume dealing damage once the next phase is visibly active.

Some players completed the fight using only their basic attack to avoid pushing her too quickly.

It is an unusual solution for an action RPG.

Optimise the build for months.

Remove most of its damage when the campaign needs time to speak.

Players Should Wait After Every Major Health Threshold

The safest approach is treating every visible phase change as a stop sign.

When Adreona begins speaking, stop attacking.

When she summons spirits, avoid them without continuing the damage rotation.

When the dialogue ends and she resumes normal combat, begin attacking again.

Players have described several dialogue moments during the fight, including lines connected to Lorath, Akarat and Adreona’s identity.

The exact wording is less important than allowing each sequence to finish.

If the boss is talking, the damage meter should take a short lunch break.

Mercenaries Can Push Her Through The Phases

Mercenaries may make the problem harder to control.

Even when the player stops attacking, a mercenary can continue damaging Adreona.

Damage-over-time effects, summons and automatic companion abilities can do the same.

Several players reported completing the encounter after dismissing their mercenary.

Others managed to finish it with companions still active by carefully controlling their own damage.

Dismissing the mercenary is therefore not guaranteed to be necessary.

It can make the workaround considerably easier.

Adreona needs time to perform.

Your hired employee may not respect theatrical union rules.

Minion Builds May Need Extra Preparation

Necromancers and other companion-heavy builds have less direct control over when damage stops.

Minions may continue attacking after the player releases every button.

Damage-over-time effects may remain active through an entire dialogue sequence.

Players using these builds may need to reduce their equipment, dismiss available companions or temporarily alter the build before entering the fight.

Removing one or two high-damage items may be enough.

Switching to a weak basic skill can also help.

The goal is not to make the encounter challenging.

The goal is to make the game slow enough to remember which cutscene comes next.

Changing Difficulty Has Worked For Some Players

One reported workaround involved leaving the game and changing the difficulty.

A player who became stuck on Normal switched to Hard and completed the fight successfully.

The higher difficulty increased Adreona’s health enough to prevent the character from skipping through her scripted thresholds instantly.

Other players raised the difficulty and still dealt too much damage, so this solution will depend on the build.

Changing difficulty does not directly repair the encounter.

It creates more room for the scripts to occur before the boss loses all of her health.

Blizzard has accidentally created a boss that becomes easier to complete when made harder.

Letting Adreona Kill The Character Can Reset The Fight

Players trapped in the endless final phase need to restart the encounter.

Some have done this by allowing Adreona to kill the character.

After respawning, they returned and completed the fight more slowly.

Characters with strong regeneration, barriers or automatic defensive effects may struggle to die.

Players have suggested unequipping armour and defensive items to speed up the process.

Leaving the game can also reset the encounter, although several players said restarting alone did not prevent the bug from happening again.

The fight needs a different pace, not merely another loading screen.

Hardcore Players Face A Much Worse Situation

The death-reset workaround is obviously unacceptable for Hardcore characters.

A Hardcore player cannot deliberately die and return for another attempt.

The character is permanently lost.

One Hardcore player reported encountering the problem and fearing that the endless fight would eventually kill the character.

If Adreona becomes stuck, the safest option is escaping or leaving the game before resources and defensive cooldowns are exhausted.

Hardcore players should reduce their damage before starting the encounter rather than testing whether the bug occurs.

A campaign script should not become a permadeath mechanic.

The Bug Can Block The Entire Campaign

Adreona is not an optional side boss.

Players encountering the bug can be prevented from continuing the campaign.

One report described repeated restarts without success and the player considering abandoning Diablo 4 until a fix arrived.

This makes the issue more serious than a broken farming encounter.

The player cannot simply choose another activity and return later if the campaign is still required for progression.

The boss stands between the character and the next part of the game.

She is not difficult to defeat.

She is technically unwilling to acknowledge defeat.

The Problem Has Been Reported On Multiple Platforms

The original reports included PC players, while an Xbox Series X player described the same low-health lock and campaign blockage.

That makes a platform-specific graphics or installation problem less likely.

The repeated phase-skipping explanation also appears across different reports.

Players on separate platforms found similar solutions:

Slow the damage.

Wait for dialogue.

Allow the spirit attacks to complete.

Then continue.

When several platforms require the same ceremonial restraint, the problem probably lives in the encounter logic.

The Fight Needs Protected Phase Transitions

Adreona’s scripts should not depend on the player voluntarily stopping damage.

Blizzard could temporarily cap her health at each phase threshold.

Once the required dialogue and attack sequence finishes, the next part of the health bar could become vulnerable.

This is common in scripted boss encounters.

The player may dislike a brief immunity phase, but the encounter remains functional regardless of build power.

Alternatively, excess damage could be stored and applied after the transition completes.

The boss should process the phase before processing the death.

At the moment, both events appear to reach the same doorway and refuse to let each other pass.

Dialogue Should Not Control Whether The Boss Can Die

Story dialogue can enhance a boss fight.

It should not be required for the health system to work.

The campaign should be able to trigger the final sequence even when the player crosses several health thresholds rapidly.

If dialogue is skipped by high damage, the game could immediately queue the missing event or advance to the appropriate state.

The boss death trigger should verify whether all required phases occurred and resolve any missing ones automatically.

It should not leave Adreona immortal because the player interrupted her monologue with a critical hit.

The Game’s Power Creep Makes Older Pacing Fragile

Live-service characters become stronger over time.

New items, seasonal mechanics, class buffs and additional progression systems increase the damage players can produce.

Campaign encounters built around older damage expectations may no longer have enough health to support their scripted pacing.

A dialogue sequence that originally triggered after several seconds can now be crossed in a single attack.

Blizzard needs to test campaign bosses against current endgame-level damage rather than only fresh characters.

Players will bring overpowered builds into old content.

That is one of the rewards for becoming overpowered.

The campaign should survive the compliment.

Bosses Should Be Tested With Minions And Damage-Over-Time Builds

Manual burst damage is only one possible trigger.

Minions, mercenaries, thorns and damage-over-time effects can continue applying damage while the player waits.

Testing should therefore include builds that cannot instantly stop every source of damage.

A phase transition must work even when several effects remain active on the boss.

The game can clear temporary damage effects when the threshold is reached or make Adreona fully immune during the transition.

Players should not need to reconstruct the build because the boss requires a clean theatrical pause.

A Reset Button Would Be Better Than Deliberate Death

When a campaign encounter becomes stuck, players need a safe way to restart it.

The game could provide a “Reset Encounter” option after a boss has remained invulnerable for an unusual amount of time.

This would return the player to the entrance without requiring death or a complete logout.

Hardcore characters would gain a way to escape a broken fight without risking permanent loss.

The system could be limited to clearly stalled encounters to prevent abuse.

Being forced to remove every piece of armour so a bugged boss can kill you is not an elegant reset function.

The Quest Should Detect A Stalled Final Phase

Blizzard could also add a failsafe timer.

If Adreona remains below a small percentage of health while taking damage for an extended period, the game should re-trigger the missing phase or complete the encounter.

This would protect players even if the underlying script fails again.

A boss absorbing millions of damage at one percent health for several minutes is not behaving normally.

The game should recognise that without requiring a forum report and an improvised basic-attack guide.

The Current Workaround Is Simple But Absurd

Players who have not yet reached Adreona can prepare in advance.

Dismiss the mercenary if possible.

Remove some of the strongest equipment if the character massively overpowers the campaign.

Use a basic attack or weaker skill.

Pause whenever Adreona begins speaking or summons spirits.

Do not resume full damage until every dialogue and attack sequence finishes.

This method has allowed multiple players to complete the encounter.

It is also the opposite of everything Diablo usually teaches.

Do less damage.

Wait politely.

Allow the demon to finish.

Blizzard Has Not Publicly Confirmed A Complete Fix

Some players briefly believed the encounter had been repaired after later attempts worked.

Additional reports continued appearing afterward, including posts in May and June.

That suggests the issue was not consistently eliminated for every player.

Blizzard’s current patch information does not clearly identify a comprehensive Adreona phase-lock fix.

The problem may not affect every character or every attempt.

The player reports are consistent enough that anyone approaching the encounter with extremely high damage should be cautious.

Players Should Not Be Punished For Strong Builds

Building a powerful character is Diablo’s central progression fantasy.

The player spends hours collecting gear, improving skills and creating a rotation capable of destroying bosses quickly.

The game should celebrate that progress.

It should not block the campaign because the boss’s dialogue system cannot keep up.

Adreona needs protected transitions, a stalled-fight failsafe and a safer reset option for Hardcore.

Until that happens, players may need to approach her with restraint.

Kill the demons.

Just remember to let them finish speaking first.

For more coverage of campaign bugs, boss fights and current Diablo 4 problems, visit our Diablo 4 archive.

Sources

• Diablo IV Forums: Players report Adreona becoming stuck at low health
• Diablo IV Forums EU: Adreona phase-lock reports and player workarounds
• Blizzard: Current Diablo IV patch notes

```

Read More

Diablo Immortal’s Voracity Fix Is A Tiny Patch Note With Big Boss-Fight Energy

Diablo Immortal’s latest update has plenty of louder things to talk about.

Poisoned Winds is rotating through July. Cross Region Bout of Realms is bringing elite PvP back into the arena. Warlock got a stack of fixes. Somewhere, a clan officer is probably staring at a schedule and wondering if sleep is optional.

But one small section near the bottom of Blizzard’s update may be one of the most player-friendly changes in the whole patch:

Voracity’s poison attacks should now better match what players actually see on screen.

Revolutionary concept, really. The green death puddle should kill you where the green death puddle is.

Voracity Got Better Attack Clarity

Blizzard’s Diablo Immortal update says it improved attack clarity for Voracity in Path of Blood.

The patch adjusts Poison Blast animations so the trajectory better matches the actual damage location and hit visual effects. It also reduces the size of the poison pool damage area so it lines up with the visual, meaning players should no longer take damage while standing outside the visible poison.

That sounds small until you have been killed by invisible boss math.

Then it sounds like justice.

This Is Not About Making Voracity Easy

Boss fights in Diablo should be nasty.

They should punish bad movement, greedy damage windows, panic healing, and that classic moment where you think “I can tank one more hit” right before the game politely deletes your confidence.

That is fine.

What is not fine is taking damage from an attack that visually says one thing and mechanically does another. That is not difficulty. That is the boss fight gaslighting you with poison.

Voracity can still be dangerous after this fix.

It should be.

It just needs to be dangerous in the correct spot.

Visual Clarity Is A Real Balance Issue

Players often talk about balance as damage numbers, cooldowns, class tuning, legendary gems, PvP power gaps, and all the usual spreadsheets with claws.

But visual clarity is balance too.

If a boss attack looks smaller than it really is, the player is making decisions with bad information. If a projectile trajectory does not match the hit location, dodging becomes a guess. If a poison pool damages outside its visible area, then the safest move is not skill. It is paranoia.

And Diablo Immortal already has enough paranoia built into its menus.

Path Of Blood Needed The Cleanup

Path of Blood is exactly the kind of mode where clarity matters.

Players push through increasingly demanding encounters, and failure often comes down to movement, positioning, cooldown use, and reading attack patterns quickly.

That only works if the game is honest.

A tough boss with clear mechanics is frustrating in a good way. A tough boss with misleading visuals is frustrating in the “why did I even dodge?” way, which is much worse and usually leads to angry tapping.

Voracity’s poison fixes should make the fight feel cleaner without removing its bite.

Small Fixes Like This Keep Players From Hating The Wrong Thing

The best part of this kind of patch note is that it stops players from blaming themselves for nonsense.

If you stand in poison and die, fair enough. That is on you. The puddle was right there, glowing like a toxic bad decision.

If you stand outside the poison and still die, the game has started a fight with basic trust.

Fixing that does not just make the encounter better. It makes player feedback more useful. When people die, they can actually judge whether they made a mistake, instead of wondering whether the visual effect was secretly lying through its teeth.

Not Flashy, Very Necessary

Voracity’s fix will not dominate the update conversation.

It will not get the same attention as Cross Region Bout of Realms, Champion Stars, Poisoned Winds, or the Warlock fixes. It is not a dramatic headline feature.

But it is the kind of change players feel immediately when the fight starts behaving like the screen is telling the truth.

Diablo Immortal can keep its chaos. It can keep its dangerous bosses, messy events, elite PvP, and questionable relationship with player schedules.

But when the game draws a poison pool, the poison pool should tell the truth.

That is not asking for mercy.

That is asking the green murder circle to stay inside its own damn lines.

Sources

Sources: Blizzard: Crown the Champions in the Cross Region Bout of Realms, More Diablo Immortal coverage on Diabloz.net.

Read More

Diablo 4 Finally Lets Players Skip Mephisto’s Mid-Fight Drama

Diablo 4 Patch 3.1.0 contains a lot of serious changes.

Ruptures have been tuned. Unique items can be enchanted. War Plans have been adjusted. Echoing Hatred has a wave cap. Chromatic Tuning Prisms got their little crafting economy slap.

Important stuff.

But buried inside the patch notes is one tiny line that may bring more joy than half the balance changes combined:

The mid-fight cutscene for Echo of Mephisto can now be skipped.

Blizzard even added one word after it: “Rejoice!”

Correct.

Absolutely correct.

Mephisto’s Drama Was Not the Real Boss Fight

Mephisto is supposed to be terrifying.

He is the Lord of Hatred. A Prime Evil. A cosmic manipulator. A demon so nasty that even standing near his plot relevance probably voids your warranty.

But there is a difference between terrifying and making players sit through mid-fight theatre when they are already farming, pushing, testing builds, or trying to get back into the rhythm of murder.

Boss fights in Diablo 4 work best when the pace is sharp. You dodge, burst, reposition, panic, recover, and then pretend everything was under control.

A forced cutscene in the middle of that loop can feel like the game grabbing your controller and saying: “Hold on, the demon has a monologue.”

No thank you.

Skipping Cutscenes Is a Small Change With Big Sanity Energy

This is not the kind of patch note that changes builds.

It will not suddenly fix your gear. It will not give your Sorcerer better survivability, make your loot rolls kinder, or stop your stash from becoming a haunted storage unit full of bad decisions.

But it will make repeated Mephisto fights feel less annoying.

That matters.

Diablo players repeat content. That is the entire disease. One boss fight becomes ten. Ten becomes fifty. Fifty becomes “I am fine, this is normal, I simply need one more drop.”

When content is repeated that much, every forced pause gets louder.

The first time, a cutscene is atmosphere.

The twentieth time, it is a hostage situation with lighting effects.

Blizzard Knew Exactly What It Was Doing With “Rejoice”

The funniest part is Blizzard’s wording.

Not just “the cutscene can now be skipped.”

Rejoice.

That little word says everything. Blizzard knows. Players know. The demons know. Everyone involved understands that this was not just a technical improvement. It was a mercy.

There is something beautifully honest about it.

Diablo 4 patch notes are usually full of serious language. Damage adjustments. Tooltip corrections. Progression fixes. Reward tuning. Class bugs being dragged out of the basement and beaten with a spreadsheet.

Then suddenly:

Mephisto can stop talking now. Rejoice.

Perfect.

This Is the Kind of Friction Fix Diablo 4 Needs More Often

Big systems get most of the attention, and fair enough.

Season 14 has plenty of those: Pandemonium Ruptures, Mythic Unique changes, Solo Self Found, Tower rewards, War Plans updates, and the whole Death Awakening machine.

But small friction fixes are often what make a game feel better day after day.

Skipping an overplayed cutscene. Making objectives faster. Improving reward flow. Removing awkward interruptions. Letting players stay in the action instead of repeatedly watching the same bit of demonic stagecraft.

That stuff adds up.

Diablo 4 does not always need more complexity.

Sometimes it just needs to stop standing between the player and the next monster that needs deleting.

Let Mephisto Be Evil, Not Unskippable

Mephisto should be dangerous.

He should be creepy. He should feel ancient, manipulative, and deeply unpleasant. He should absolutely make players question whether following demon whispers was a good idea.

But he does not need to force everyone through repeat performance art in the middle of a fight.

That is not hatred.

That is customer service hold music with horns.

Patch 3.1.0 fixes that, and it deserves the little celebration Blizzard gave it.

So yes.

Rejoice.

The Lord of Hatred can still ruin your day.

He just has to do it without making you sit through the same mid-fight drama every single time.

Source: Blizzard’s Diablo IV Patch Notes.

Read More

Diablo 4 Duriel Death Bug Has Players Baffled

 

Diablo 4 has another fresh bug report on the board, and this one hits a boss fight that is supposed to feel brutal, not paranormal. A new Diablo IV PC bug report says the player is dying instantly during the Duriel fight with nothing visibly hitting them, nothing appearing under them, and no obvious attack crossing the room. That already sounds miserable. The extra kick in the teeth is that the player says it is reliably reproducible, which moves this out of random bad-luck territory and into proper bug-watch territory.

What the report actually says

The details are specific enough to be worth taking seriously. The player says they were trying to finish the last part of the Season Journey, fighting Duriel in a group of two, with both players using the same Hydra Sorcerer build and the same gear. Yet only one of them kept getting instantly deleted “to nothing,” including after being resurrected. The same report also says the player has noticed hitbox issues elsewhere this season, but believes this Duriel problem is worse because they were clearly not standing in anything visible when the deaths happened.

Duriel has had visibility problems before

That does not prove this is a long-running Duriel bug with the exact same cause, but it does add context. Back in June 2023, players were already filing official forum complaints about the Duriel fight saying the camera could get blocked by arena geometry and that bad hitboxes around ground hazards made the encounter harder to read than it should have been. So while today’s report is not the same bug, it fits an old Diablo 4 pattern: when players cannot clearly see what killed them, the fight stops feeling deadly and starts feeling dirty.

This is exactly the kind of death that makes players stop trusting the game

That is the real issue here. Diablo players will tolerate hard bosses. They will even tolerate getting flattened when they know why it happened. What they do not tolerate for long is a death that looks like the game forgot to show its work. We have seen that frustration before in broader Diablo 4 complaints, including a January 2025 “Unknown Killer” thread where Hardcore players reported sudden one-shots with no clear source. That does not mean Duriel is caused by the same thing, but it does show how quickly invisible or unreadable deaths poison confidence in the game.

For now, this one stays in bug-watch territory

At the time of writing, the April 22 Duriel thread is live in Blizzard’s PC Bug Report section and does not show a visible Blizzard reply yet. So no, this is not proof that Duriel is broadly broken for everyone. But it is a very usable warning sign, especially in a season where Diabloz has already covered issues like quest steps soft-locking progression and world boss rewards going missing. Sanctuary is at its best when it feels cruel on purpose. “You died to absolutely nothing” is a different flavor, and it is a lot less charming.

Read More