Editorial policy
This page describes how our guides are made. It exists so you can judge how much to trust a given page, and so we have something to hold ourselves to.
Testing#
Fix guides. Every step in a fix guide falls into one of three categories, and we distinguish them on the page:
- Tested — we reproduced the problem and confirmed the step resolved it.
- Standard practice — an established fix for this class of problem on this platform, which we have applied before but could not reproduce for this specific case.
- Unconfirmed — reported by players, plausible, not verified by us. Labelled as such, always.
We do not present category 3 as category 1. A guide full of unverified steps that happens to contain the right one is not helpful; it is a lottery with your evening.
Sourcing#
Factual claims — release dates and times, patch contents, platform availability, subscription terms — are sourced from primary sources wherever one exists: the developer, the publisher, the platform holder, or official patch notes. We link to them.
Where no primary source exists yet, which is common in a launch week, we say what is known, say who reported it, and mark it as unconfirmed rather than laundering a forum post into a fact.
We do not copy guides from other sites. Where another outlet was first to something material, we link to them.
Dates and updates#
Every page shows a "last updated" date. It changes when the content changes materially — not when we fix a typo, and never as a trick to look fresh.
For games under active development we re-check guides after major patches. When a fix stops being necessary, we say so on the page rather than deleting the section, because readers arrive from search results that may be months old and deserve to know the ground moved.
Corrections#
When we get something wrong:
- We fix it promptly.
- If the error was material — wrong steps, wrong date, advice that could cost you progress — we note the correction on the page rather than silently editing.
- We do not delete pages to hide mistakes.
Report an error through the contact page. Include the page and what happened when you followed it; that is what makes a correction actionable.
AI and how these pages are written#
Our guides are written and edited by people. We use software tools for research, drafting support and formatting, as most publishers now do — but a person is responsible for every factual claim on every page, and nothing is published that has not been read and checked by one.
We do not publish machine-generated pages at volume, and we do not publish a guide for a game nobody on the team has played or tested.
Affiliate links and advertising#
Some links to stores are affiliate links, which means we may earn a commission on a purchase. These are labelled where they appear.
Affiliate arrangements do not influence what we cover or what we conclude. No publisher, studio or platform pays for coverage, for a review verdict, or for placement on this site. If that ever changes, this page changes with it.
Review and verdict independence#
Where we publish an opinion — a review, a tier list, a recommendation — it is ours. We do not run copy past publishers before publication, and we do not accept conditions on coverage in exchange for access.
Reader contributions#
A meaningful share of our fixes come from readers who hit a bug and worked out the answer. When we use a reader's finding, we credit them if they want credit and we verify it before publishing either way.