How we write our guides

A guide is only useful if you can trust it. Ours earn that trust the boring way: by labeling what we know, citing where it came from, and admitting what we don't know yet.

The confidence system

Every page — and any individual claim that needs it — carries one of four labels:

• VerifiedConfirmed in-game or from an official source (developer posts, patch notes, store pages).
• ReportedMultiple independent community reports, not yet confirmed. We never round "reported" up to "verified".
• PatchedBehavior changed by a patch — the page notes which version.
• UnverifiedA single or unclear report. Treat as a lead, not a fact.

Sourcing

Every entry cites at least one source: the official site, the developer's X account, store pages, patch notes, named press, or named community posts (labeled as reported). When reports disagree, we say so in a visible conflict callout instead of picking a winner.

What we don't do

• No invented testing or made-up benchmarks.
• No fake author personas or bylines.
• No "guaranteed fix" language — troubleshooting is honest about odds.
• No rehosted official art, screenshots from other sites, or film stills.

Content is written with AI assistance and reviewed by a human editor.

Corrections

Spotted something wrong? Use the contact page. Corrections are reviewed against sources and the page's updated date reflects every change.