Use this page for optional discoveries, not for guesses presented as hidden mechanics. A secret should have an observable clue, an unusual route, a message, a reward, or a repeatable change in the current base game. Sephiria’s official store page describes the tower, chapters, enemies, bosses, and inventory systems, but it does not publish a secret-room catalog. Community reports can point to a question; the live game must confirm the result.
Record what changed
Note the visible object, path, message, or room behavior that invited a second look.
Describe the decision
Explain the safe approach without pretending that a random route is fixed.
Confirm the outcome
Check the current reward, unlock, or message in the same product and version.
Label the lead
Separate confirmed, observed, community-reported, and unresolved claims.
Protect a first clear
Do not chase a secret during the first run if the detour can end the chapter. Learn the ordinary route, record the clue, and return with a build that has a fallback. The Walkthrough covers preparation; the Builds hub helps decide how much risk a discovery attempt can accept.
If the clue appears near a boss or a transition, note it and finish the run before experimenting. A failed optional attempt is less costly when the main route is already understood. This also keeps the evidence clean: a player can distinguish the discovery action from the unrelated reason the run ended.
Write an evidence card
Each secret card should include chapter label, mode, platform, version, clue, route decision, observed result, and confidence. Preserve a screenshot only when it is original and necessary; do not copy a community image. If the game displays a name or message, transcribe it carefully and keep the exact wording beside the interpretation.
Treat community posts as leads
Steam Community discussions can reveal what players are hunting: hidden paths, final-boss details, chapter progression, or unusual rewards. A post may be old, incomplete, or tied to Early Access. Link it in a secondary-evidence note, rewrite the practical question, and state what remains unconfirmed. Never convert “someone said this worked” into a guaranteed unlock.
Retest after updates
Secrets are vulnerable to route, reward, and progression changes. When an official note touches a chapter or system, retest the clue and the result. Link to Updates and keep historical observations marked. The base-game scope is AppID 2436940; the separately listed demo is outside this page.
Confirm before revealing
A spoiler page should reveal only what its evidence supports. First describe the clue and the safe preparation. Then place the route and result after a warning. If the reward, gate, or exact path is uncertain, keep the section labeled as a lead and tell readers what they can observe for themselves. This lets a blind player stop before the reveal and an investigating player contribute useful evidence.
Do not treat a secret as confirmed because a video reaches an unusual room. Check the product, branch, date, and visible outcome. A demo or Early Access clip may be real and still irrelevant to the base-game launch. The Version History page explains how to preserve that distinction.
Route without sacrificing the run
Use a flexible build, leave inventory margin, and know the ordinary exit before testing the optional path. If the discovery changes a boss or chapter transition, record the result and complete the safe route before repeating it. Link the preparation to Walkthrough and the progression question to Progression.
The ordinary exit is part of the spoiler-safe preparation because it lets a player investigate without losing the run to an optional experiment.