Advertisement
How answers get graded
Early Access answers age quickly. Each claim therefore carries a source, a check date, a version boundary and a condition that sends the page back to draft.
The source ladder
| Source | Weight | What it means |
|---|---|---|
| Developer changelog | Publishable alone | Patch notes and developer posts on the official Steam news feed. The strongest source available for a game this new. |
| Developer statement | Publishable alone | A clearly attributable answer from NerveLabs on its own official or public account. It must answer the page's exact intent, not a nearby question. |
| Official Steam listing | System facts only | Useful for supported modes, Early Access scope and requirements. A broad feature listing cannot supply a route, command or quest solution by itself. |
| Two independent players | Publishable together | Two accounts that reached the same conclusion separately. Copies of one post, or reposts of the same thread, count once. |
| Single report | Publishable with a warning | A complete current-build route from one named creator can publish only with attribution and an explicit statement that no second source independently reproduced it. Missing steps stay draft. |
| Generated aggregator | Rejected | Pages that restate each other without citing anything. Being first in a search result is not evidence. |
What happens to a question that fails the gate
It becomes a draft. A draft keeps sourced fragments and open questions, but it has no quick answer, carries noindex/nofollow, stays out of the sitemap, and receives no link from an indexable page. Of the 62 evidence-carded questions checked for Update 7, 57 passed and 5 did not.
The held pages cover the first key and hermit, main quest stages, Tower preparation, spellcrafting explosion conditions, co-op setup and the save path. Each has useful background evidence, but none has an answer to the unresolved part of its exact question. Background evidence is not a substitute for solving the player’s problem.
Rules this site holds itself to
- No claimed playthrough. Nothing here is presented as first-hand play, because none of it is.
- No screenshots taken from other people. The diagrams on this site are drawn from scratch.
- Version-stamped. Every answer names the build it was checked against, because a patch can invalidate it overnight.
- Unknowns stay visible. Where the evidence stops, the page says so instead of filling the gap with a plausible sentence.
- Corrections are structural. If a source turns out to be wrong, the page goes back to draft rather than being quietly edited.
Confirmed changes are recorded in the public corrections log.
Known gaps in the research itself
- There is no official Wiki. Competing guide hubs are useful for discovering search phrasing, but they do not clear the evidence gate by repeating one another.
- Two comments in one discussion are weaker than two independently produced walkthroughs. Same-thread agreement is recorded, but it does not automatically turn a route into a verified answer.
- Sources from pre-release playtests are treated as historical unless Update 7 evidence confirms that the mechanic survived.