Fact Checking Policy

Every factual claim about a game on this site is checked against that game. Here is how, and here is how to tell us when we get it wrong.

Last updated

What counts as a factual claim here

Most of what this site asserts is about how our own games behave: how many lanes a game has, what a control does, whether a landing angle is checked, how a multiplier decays, how long a run lasts. Those are all verifiable, and they are the claims this policy is mainly about.

A smaller amount of writing is opinion — which game is the best place to start, whether a mechanic is satisfying. We try to make it obvious which is which, and we do not dress up a preference as a fact.

How claims are verified

  1. Played. The writer plays the game enough to describe it from experience, not from memory of a similar game.
  2. Read. The specific claim is checked against the game module. Numbers — timer lengths, charge counts, lane counts, thresholds — come from the code rather than from an impression.
  3. Re-checked. A second person confirms the claim independently before the page goes live.
  4. Device-checked. Anything about controls is confirmed on both a keyboard and a touchscreen, because those are different code paths.

Keeping pages current

When a game is retuned, every page that describes the changed behaviour is reviewed in the same session — the game page, its category introduction and any guide that mentions it. The “Updated” date on those pages changes to reflect the edit.

We also re-read the full game library periodically to catch drift, because the most common source of an inaccurate page is not a mistake at the time of writing but a change afterwards.

How corrections work

If a published page turns out to be wrong, we fix it and we say so. A substantive correction — one that changes what a reader would do — gets a short note on the page saying what was wrong and when it was corrected. Typos, broken links and clarifications are fixed without a note.

We do not delete a page to make an error disappear, and we do not quietly rewrite a claim and leave the old date in place.

Reporting an error

Email hello@motorcyclearcade.xyz or use the contact form. The most useful reports name the page and say what is wrong — for example, “the controls table on Motorcycle Trial lists the hop as a tap, but holding it charges a higher hop”.

We aim to acknowledge error reports quickly and to correct clear factual errors as soon as we have confirmed them. If we disagree that something is an error, we will tell you why rather than ignoring the message.

What we do not do

We do not claim any professional fact-checking certification, membership of a fact-checking network, or third-party accreditation. This is a small independent site describing its own games carefully; that is the whole claim.

Questions about this page? Email hello@motorcyclearcade.xyz. Related: privacy, cookies, terms, disclaimer, editorial policy, fact checking.