The demo has a confirmed underground secret
The developer's response to a demo player confirms an additional secret in the underground dungeon. This is stronger evidence of a secret's existence than inferring one from a suggestive screenshot. It gives historical demo players a reason to inspect beyond the most obvious route through that playable area.
That confirmation does not supply a verified coordinate or a universal unlock sequence. Keep the distinction between knowing that a secret exists and knowing exactly how to reach it. If you are following a demo-specific lead, match it to the version you are playing before interpreting a different room as the same location.
Record suspicious places on the automap
The automap supports custom marks, and the later notes feature explicitly includes suspicious walls as an example. Use that support to keep track of places you intend to revisit. A note is particularly useful when the location makes sense to you now but would be difficult to recognize after several more encounters.
Write down the observation that made the area interesting. A reminder about a wall, a mechanism or an unfinished branch is easier to act on than a marker with no explanation. When you resolve the question, update your record so it no longer competes with genuinely unfinished exploration.
Inspect environmental puzzles as separate leads
The developer explains that some harder puzzles reward hidden areas. A puzzle can therefore be a lead in a secret search rather than merely an obstacle on the obvious route. Pressure plates, levers and riddles are the confirmed types discussed in the puzzle material.
Investigate the mechanism you actually see and preserve its local context. Do not assume that a combination from another location opens the same kind of secret in your current area. A precise solution needs a matching puzzle and version, while a general exploration habit can be useful throughout the adventure.
Prepare before pursuing an optional encounter
Optional bosses are included in the store's description of hidden content. They bring combat into an exploration decision, so discovering a route is only part of preparing to use it. The documented recovery loop makes it sensible to review resources before committing to a demanding encounter.
Check the party's condition and the supplies that support rest and recovery. Keep the existence of an optional boss separate from any assumed attack pattern or reward. Finding an encounter does not establish its weaknesses, and this guide does not turn an exploration lead into an untested boss strategy.
Keep historical demo leads separate from the release
The developer confirms that the full game's levels differ from the demo. A secret discussed in the demo therefore should not automatically be assigned the same location in the release world. The same version distinction applies to nearby quest encounters and routes used to reach them.
Use the current map to maintain your own exploration record. When comparing another player's discovery, check that the product and surrounding layout match before following the direction. This preserves the useful clue without treating an old route as proof of an unchanged full-game location.
Compare a secret claim with what it actually establishes
A source can establish that hidden content exists without explaining how every player reaches it. The developer's demo reply is useful because it confirms an underground secret, while the release store is useful because it identifies false walls, alcoves and optional encounters as part of the full game's design. Neither statement should be silently expanded into a complete checklist of room positions, rewards and required actions.
When comparing a more detailed hint, look for the matching product and the actual observation it describes. An item hidden by scenery is a visibility problem, a closed route is an access problem and a named encounter is a combat discovery. Keeping those categories separate stops a useful exploration clue from turning into an unsupported instruction about a different system.
You can apply that distinction to your own map notes as well. Mark what you saw and what you intend to inspect, rather than recording an untested theory as a completed discovery. This makes the next visit informative and keeps the search grounded in the world you are actually exploring instead of an imagined completion total.
Explore thoroughly without chasing a false completion count
The confirmed features support careful exploration, but they do not establish a complete secret total or a universal reward checklist. A practical goal is to resolve the marked questions in the area you are exploring. That creates a concrete next step without relying on an invented percentage or an unsupported claim that one remaining wall must contain something.
Use the map, local clues and the distinction between items, mechanisms and encounters to organize that work. Return to unresolved places with a clear observation to investigate. If your immediate problem is the historical mushroom quest or a rubble obstruction, the focused guides provide a better next step than repeatedly checking every wall for an unspecified secret.
Sources and further reading
- Developer: an underground secret in the demo
- Official full-game hidden content description
- Official automap and custom marks
Information checked November 5, 2026. Report a correction.