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. |
| Publisher guide | Publishable alone | Documentation produced or linked by the publisher, such as the Beginner's Guide referenced from the official announcements. |
| Official wiki | Use with version check | The publisher-hosted wiki is useful documentation, but it is community-contributed and can lag a patch. Version-sensitive claims are checked against changelogs where possible. |
| 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 | Draft only | One player, one thread, no corroboration. Recorded as an open question so it can be checked later. |
| 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 10 evidence-carded questions checked for build 0.5.5, 8 passed and 2 did not.
The held pages cover the exact route to the Anomaly and the current Vacuum unload controls. Each has useful background evidence, but neither has a verified answer to the exact question in its title. 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.
Known gaps in the research itself
- The official wiki is publisher-hosted but community-contributed. Its pages are treated as documentation, not as a developer changelog, and version-sensitive details still need a freshness check.
- 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 the 2025 demo period are treated as expired and are only cited to mark them as outdated.