Source priority
Primary official sources come first: the Steam store, developer-owned announcements and developer-published patch or troubleshooting posts. Stable in-game observation may support a practical workflow when clearly identified. Community reports are used to monitor symptoms, never promoted to official fact without corroboration.
Evidence labels
- Verified official: directly stated on the official store or equivalent first-party surface.
- Developer described: explained by the developer, but potentially patch-sensitive.
- Developer acknowledged: a reported behavior or fix the developer has explicitly addressed.
- Community reported: useful signal that is not treated as universal.
- Not verified yet: intentionally withheld details when current evidence is insufficient.
Freshness and release state
Pages show a real check date and distinguish a planned date from an observed live release. Calendar passage alone never changes the release badge. Patch-sensitive map, balance, reward and issue claims are rechecked against current first-party evidence.
Corrections and conflicts
When sources conflict, the newer and more authoritative first-party source normally controls. The page should preserve the relevant date, narrow the claim, and avoid silently combining obsolete development details with current behavior.
Safe troubleshooting
Destructive steps require an explicit scope and progress-loss warning. For example, deleting the developer-published old Playtest save folder resets local save progress and should only be considered when that exact guidance applies. A migration or backup-safe path is preferred whenever available.