We start with a player question
A page should help someone decide what to watch, check, or do next. Similar search phrases are grouped under one page when they ask the same thing. We do not publish a separate page just because a wording variation exists.
Claims need a named source
Official developer sites, announcements, patch notes, storefront records, and official game accounts are preferred for game facts. The source register records the source, the date checked, and the claims it supports.
Search suggestions and community posts can reveal demand or lead to a source. They are not enough to confirm a release date, platform, character identity, plot point, or feature on their own.
Development footage has limits
We describe what is visible and audible in the cited build. If the publisher says the footage is from a development build or may change, that warning stays with the analysis. A visible mechanic is not automatically a launch feature, and an unidentified character is not given a name to make the story sound complete.
Confirmed, inferred, and unknown stay separate
Confirmed facts must be directly supported by a source. Visual observations are tied to a timestamp or build. Inferences are labelled as interpretation. When the available material does not answer a question, the page says so.
Updates and corrections
Long-running fact and explainer pages are updated when a reliable new source changes the answer. The checked date moves with the review. If an earlier statement becomes wrong, we correct it rather than leaving the old claim in place for search traffic.
A correction report should include the exact page URL, the disputed sentence, and a primary source that supports the change. The contact page explains the currently available route.
Tools and editorial review
Software may help collect public records, compare versions, transcribe media, or check links. It does not turn an unsupported statement into a fact. Pages are reviewed against their cited material before publication.