Fact-Checking Policy

Three kinds of claim

Almost everything we publish falls into one of three categories, and each is checked differently.

1. Claims about our own games

These are the majority of our content: “the jab recovers in 0.115 seconds”, “you recover 20% health between fights”, “the Expert preset uses a 0.26-second reaction window”.

Every one of these is verified against the source code before publication. The figures are read from the relevant file — /js/game/combat.js, /js/game/difficulty.js, or the individual game's own script — not recalled or estimated. Because the site is open in its construction, you can check any of them yourself.

When we change a game's balance, updating the affected pages is part of the change. If you find a page that disagrees with the game, the game is authoritative and the page is a bug.

2. Claims about how browsers and web technology behave

Things like input latency ranges, Canvas performance characteristics, or what localStorage does in a private window. These are checked against primary documentation — specifications, MDN, browser vendor documentation — and, where practical, tested directly. Where behaviour varies between browsers, we say so instead of generalising.

3. Claims about the real world

Boxing terminology, rules, and the history of boxing video games. These are the claims we are most cautious about, because they are furthest from our direct expertise.

For these we use reputable, checkable sources; we prefer primary sources over aggregators; we date anything that could become outdated; and we distinguish clearly between what is documented and what is our interpretation. If we cannot verify something to a standard we are comfortable with, we either leave it out or state plainly that it is uncertain.

Sources

We cite sources where a reader would reasonably want to check us. We link to the original document rather than to coverage of it. We do not cite sources we have not read, and we do not manufacture citations to make a claim look sturdier than it is — a fabricated reference is worse than no reference.

Where a guide has references, they appear in a labelled section at the end with working links.

What we never publish

• Statistics we cannot source
• Quotes from people we did not speak to
• Studies we have not read
• Player counts, download numbers or popularity rankings for our own games, because we do not measure them
• Review scores or star ratings, because we operate no review system
• Credentials, qualifications or affiliations we do not hold

Before a page goes live

1. Every numeric claim about a game is traced back to the line of code it comes from.
2. Every internal link is followed to confirm it resolves to a real page.
3. Every external link is opened to confirm it is live and says what we claim it says.
4. Every game referenced is actually played, at the stage described, to confirm the advice is accurate rather than theoretical.
5. Claims outside our direct knowledge are either sourced or removed.

Corrections

When we find or are told about an error:

• Minor errors — typos, broken links, formatting — are fixed silently and the page's updated date changes.
• Factual errors that change the meaning of a passage are corrected, and a dated correction note is added to the page saying what was wrong and what it now says.
• Substantial errors that undermine a page's conclusion get a correction note at the top of the page, not buried at the bottom.

We do not quietly delete pages to make mistakes disappear. If a page is withdrawn, the URL explains why.

How to report an error

Email hello@boxingarcade.xyz or use the contact page. Tell us the page, the claim, and what you believe the correct position is. If you have a source, include it. We aim to respond within a few days and to correct confirmed errors immediately.

A note on our own limits

We are game developers and writers, not boxing professionals. On questions of real-world boxing technique, training or physiology we defer to people who actually have that expertise, and we say so rather than filling the gap with confident prose. See the author page for what we do and do not claim.