How to Find the Dungeon Key, Treasure Room and Exit in Sunken Realms

The short route: pulse, key, door, decision

The most useful confirmed clue in the footage is not a landmark: it is the light companion. The demo tutorial says the key is randomly placed each run, while Glis pulses in its vicinity. That immediately rules out an honest one-size-fits-all screenshot with a red X. A screenshot of one particular room may show the right kind of key but cannot tell you that the item will appear there next time.

Start with the map, clear a manageable route and revisit any unexplored junctions. The signal is local; use it to concentrate your search when it appears. Do not assume a particular hidden wall, container or enemy guarantees the key. Videos sometimes show different room sequences, which is consistent with Steam’s description of rearranged handcrafted rooms.

Once you have the key, distinguish the boss-door task from the optional treasure task. Collecting a key is not the same as winning every fight, and the tutorial describes the treasure gate as requiring the enemies to be defeated.

Troubleshooting: when the key seems missing

First, check whether you have already opened a different branch or crossed a room without checking the edges. Retracing a cleared path is less useful than systematically exploring unopened branches. If Glis pulses, search the immediate room more thoroughly before moving on. Use the map to keep your search bounded.

Next, identify the actual gate you are trying to open. The optional treasure room and the boss area have different functions in recorded demo tutorials. If one door does not respond, an unmet enemy-clear condition may apply to the treasure room; it does not mean the key mechanic is broken. Conversely, possession of a key should not be treated as proof every encounter elsewhere has been cleared.

Finally, if a quest gate genuinely behaves differently in your build, record the precise message, current version and a screenshot. Older community reports include demo navigation issues, but that does not establish a current retail bug or a universal workaround. Reproduce the state before recommending a restart.

Swipe the table sideways for all columns →

Treasure or boss: the risk decision

The demo marks the treasure room as optional and indicates that it unlocks after its enemies are eliminated. Clearing it can increase your haul, but every extra encounter consumes time and can consume health or potions. The decision depends on whether that potential reward justifies further risk for the current loadout.

The boss route is a second commitment. A recorded tooltip offers extraction or continuation, and death is presented as costly to your carried items and gold. If this is your first trip or your resources would fund a needed camp upgrade, extracting early can be a rational learning strategy. You can return stronger and use the same dungeon loop again.

Boss essence is observed in a demo as a means to skip a previously cleared section on later runs. This guide deliberately does not give a fixed essence cost or universal drop rule. Both the availability and price should be rechecked after the release build is accessible.

Run notes you can reuse without a fabricated map

A text checklist is safer than a fake interactive map when rooms reshuffle and current coordinates have not been verified. Write down whether Glis signalled the key, whether the boss access is open, whether the optional treasure gate was cleared and whether you returned safely. These are observable events across a run rather than guessed world positions.

You can use our run checklist to follow that workflow. It stores selections only in your current browser session and can encode the selected item IDs in a URL for a shared personal checklist; it is not connected to Steam saves and it does not imply the game tracks these exact achievements.

For a rigorous visual walkthrough, we still need current build screenshots of the key signal, map, boss gate and extraction prompt. This page links the source footage instead of drawing a made-up minimap.

Patch v1.05 and the Week 1 update: rooms, load times and extraction

v1.04 fixed the treasure-room bugs — the developer says the room now works every time, so a room that fails to open is a reportable bug rather than a known quirk — and raised enemy spawn rates across the board: plan extraction with a smaller safety margin than the September recordings imply.

v1.05 (25 September) changed how the layout reads. Repeated rooms were reduced so you should no longer see the same room placed next to itself, and enemies can no longer be climbed (except the Fallen Tufa), which removes the old escape of vaulting onto a hostile. This does not restore a fixed map — the key is still placed per run — so keep navigating by Glis’s pulse rather than memorising room order.

The Week 1 update (26 September) made the descent itself cheaper: dungeon load times dropped to an average of about seven seconds with crashes on dungeon load eliminated, and the treasure-room mechanic is described as bulletproofed. It also added the pause-menu unstuck button — if you wedge behind scenery, clip through a wall or otherwise get stuck, use that button instead of abandoning the run.

v1.08.2 and v1.09 (4 October): performance and flow

v1.08.2 fixed the single most expensive thing in a run: a dungeon-map bug that hammered low-end hardware. The developer's own measurement on a Steam Deck at low settings went from about 12 to about 50 FPS after the patch. If you bounced off dungeon performance before this, it is worth a retest.

v1.09 landed the same day: after a fight finishes, exploration picks up where it left off instead of restarting, and gold can be picked up with a full inventory.