Official facts
Steam store data, developer announcements, official patch notes, and the live achievement list are the preferred sources for platforms, features, requirements, dates, and unlock conditions.
Evidence protocol / public standard
A launch-week guide can become wrong after one patch. This policy explains which sources win, how uncertainty is labeled, and what happens when a page needs correction.
Steam store data, developer announcements, official patch notes, and the live achievement list are the preferred sources for platforms, features, requirements, dates, and unlock conditions.
Controls, objectives, routes, and bugs should be checked in the current build when possible. Pages identify the build or review date instead of implying permanent accuracy.
Steam discussions, Reddit posts, reviews, videos, and screenshots can reveal a problem or theory. They do not become official facts simply because several people repeat them.
Claim labels
Confirmed means the claim is supported by an official source or directly verifiable game data. Observed means the current build demonstrates the behavior, but a patch could change it. Based on early feedback means multiple player reports point in the same direction without an official statement. Theory is reserved for lore interpretation and is never presented as settled canon.
When sources disagree, the newest applicable official source normally wins. A current patch note outranks a launch announcement; an in-game prompt outranks an old trailer. The page should explain the conflict when it matters to the player.
Corrections
Corrections should change the inaccurate statement, update related pages, and revise structured data or FAQ answers that repeat the same claim. A “Last updated” date changes only when the page receives a meaningful factual or instructional revision. Dates are not refreshed merely to make old content look new.
Time-sensitive pages—local co-op, matchmaking, fixes, Steam Deck behavior, and patch notes—receive priority after an official update. General rules and achievement descriptions are reviewed when players report a discrepancy or Steam changes the underlying data.
Testing notes
When a page uses “verified” or “tested,” the review is tied to a named game build and the setup described on the page. Troubleshooting notes are checked with reversible steps on a normal Steam installation; they are not promises that one workaround fixes every GPU, controller, storefront, or network configuration.
Because this is an anonymous fan project, personal identities and private contact details are not published. Accountability comes from dated review notes, source links, change history, and clear labels when a detail is based on early access feedback rather than a developer statement.
Production
Automation may assist with HTML structure, consistency checks, link validation, metadata formatting, and early drafting. It is not treated as a factual source. Claims about Machine Party must trace back to official material, documented gameplay, or clearly attributed community reports. The editorial team remains responsible for what is published.
Mass-producing near-duplicate pages is avoided. A new page should answer a distinct player question and provide enough verified value to stand alone.