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
```












