How we write & check guides

One page, one useful job

A guide starts with the answer to its main question, then gives the steps, assumptions and exceptions needed to use it. We do not add a game or a platform solely to fill a directory slot.

Sources and verification

We prefer official documentation, support pages and maintained technical references. Each article lists the material that supports its claims and records when it was checked. Community observations, when used, must be distinguished from official rules.

“Documentation reviewed” means the cited material was checked. “Tested” would require an actual recorded test of the relevant behavior, with enough context to know what version and environment it applies to. The initial guides on this site are documentation-based.

Tools show their assumptions

A calculator must show its units, formula and limits. Inputs that cannot be used produce a visible error, and stale results are hidden. Formula checks do not establish that every possible in-game layout can deliver the calculated output.

Dates describe real work

The publication date is when a guide first appears. The updated date changes when the answer or useful guidance materially changes. The source-check date records a review. Rebuilding the website does not refresh those dates.

Corrections and changes

Send the page URL, the questionable statement and a supporting source through Contact. We investigate the specific claim and update the page when a correction is supported. A changed rule may need a revised scope or an explicit version note.

No manufactured coverage

We do not claim popularity, playtesting, reader counts or release dates without evidence. Announcements and available features are different states. A search phrase alone is not confirmation that a feature exists.