Editorial policy

Every page on this wiki is written under the same standing rules. This page states them, so you can hold our pages to them.

Last reviewed 11 September 2026

Sourcing: primary first, community second, nothing third

Release dates, pricing, platforms, patch contents and feature lists come from the official store listing and the developer’s own material. Achievement names and global unlock percentages are read from public Steam global stats; concurrent-player figures are read from public SteamDB charts. Those are the first tier, and they are the only tier treated as settled fact.

The second tier is community work — a mod author’s own documentation, a measured figure from someone who did the measuring. It is used, credited to whoever did it, and labelled as community work rather than presented as official. There is no third tier: a number that circulates widely with no traceable origin stays off these pages however widely it is repeated.

Unconfirmed is written as unconfirmed

This is the rule that costs us the most pages and matters the most. Where we reason from evidence rather than quote a source, the sentence says so. Where nobody has published a figure, we write that it is unpublished instead of filling the gap with a plausible-sounding number — the Rake’s health and spawn rate, per-weapon damage, the full melee weapon list and the author of the in-game newsletter are all currently in that state, and they are listed as open questions on the contact page rather than answered.

The reason is specific to this game: it launched with three hidden achievements that nobody had publicly solved, and vacuums like that fill up with confident guesses that then spread as fact. Following an invented requirement costs you runs. We would rather tell you we do not know.

Conflicts get printed, not quietly resolved

When two credible sources disagree, both appear with their origins and the page says why neither is being treated as settled. Picking the tidier figure would read better and inform worse.

Everything carries a date and a version

Each page shows when it was last verified and which game build it was checked against. That stamp is a commitment: it means someone re-read the page against that build’s public record, not that the page was merely touched. Statistics that drift — achievement percentages, player counts — are published with the date they were read, because a percentage without a date is not information. When a patch lands, the affected pages go through a pass and the patch notes page records what changed.

Corrections are public and fast

When we get something wrong, the fix is dated on the page rather than silently swapped in; where a claim was materially misleading, the page carries a visible note saying what it used to say. The endings page is the standing example — it still shows a note about the unlock percentages it previously displayed.

To report an error, email us via the contact page. Quote the exact passage and link the page; a report that comes with a screenshot, a patch-note line or a store link goes to the front of the queue. Verified corrections are applied within 48 hours and the page is re-dated.

Money cannot reach the copy

The site is funded by third-party display advertising, described in the privacy policy and the disclaimer. There are no affiliate links and no commissions, no advertiser previews or sponsors a page, and we do not accept payment for coverage, scores or placement. If any of that ever changes, this policy will say so before the page it affects goes live.