Egon’s Stone and dungeon recovery after October 13
The October 13 official hotfix fixes unequipping Egon’s Stone preventing Gloom loss. Do not plan a resource-preservation loop around that old exploit: unequipping the item is not the intended break condition described by the Week 1 notes.
The same update fixes slow-streaming dungeons with seamless dungeon streaming enabled and double dungeon loading. Keep those loading issues separate from the stone’s durability, revival location and dropped-resource state. If a fault persists, record the installed platform version, streaming setting and item state; the notes do not promise retroactive repair for every save.
The intended recovery loop
The August 29 notes describe revival at a dungeon entrance using the stone’s durability; when it breaks, it prevents Gloom loss for that death. September 24 lists fixes for dungeon loading and for the stone removing Gloom dropped in the open world.
Before committing to a dungeon
Check that you are using the intended item and read its current in-game description and durability. Do not treat “revive at the entrance” and “prevent Gloom loss when it breaks” as the same unconditional benefit.
Choose a purpose for the run: learn the first dangerous room, reach a known objective, or recover from a failed attempt. If every retry includes a different detour, it becomes difficult to judge whether the recovery setup is saving time.
After a death
First identify where you respawned and what happened to the item. Then inspect the resource state and any recovery marker. Keep these observations separate: a changed inventory count alone does not tell you whether the stone broke, an old issue occurred, or you are looking at a different recovery state.
If behaviour contradicts the current description, stop repeating the same expensive test. Record the dungeon, platform, version, item state before death and the result. That record is more useful for support than a general claim that the item never works.
A safer testing plan
Use a familiar route for the first comparison and avoid carrying resources you are unwilling to risk. This is an editorial testing precaution, not a hidden game rule. Do not delete a save, manipulate cloud synchronisation or copy an exploit from an older patch to diagnose a recovery issue.
The official update confirms fixes, not a guarantee that every saved state is repaired retrospectively. Check the installed update and the current announcement before repeating an older workaround.
When to choose something else
If the problem is recognising a boss attack, changing recovery equipment may shorten the walk back but will not teach the response. Pair the route with a single combat drill or check Adaptive Difficulty. If your Shell investment is the issue, read the respec guide before spending more.
Before your next attempt
0 / 4
Saved on this browser. No account required.
Sources and scope
Official changes are linked below. Practice routines are editorial suggestions, not a claim of hands-on testing or a guaranteed result.