Trust & transparency

Corrections

How to Report an Error

There is no published email address for this site yet, so there is no inbox to promise. This page documents the process anyway, because the standard does not depend on the channel: what makes a report actionable is the same either way.

A report is actionable when it names the page, quotes the sentence or table row that is wrong, states the value that should replace it, and points at a source that shows that value — an official post, a store listing, a timestamped recording, or a published guide with a date.

  • Page URL and the exact claim, quoted.
  • The correct value, and the platform, difficulty and patch it was observed on.
  • A link, screenshot timestamp or other checkable source for the correction.
  • Whether the same error appears on a translated version of the page.

What Happens Next

Report typeWhat this site does
Wrong value with a sourceThe source is read, the claim is re-graded, the page is revised and its revision date moves.
Conflicting sourcesBoth values are shown with attribution instead of one being picked — that is the normal state for a contested number.
Wrong value, no sourceThe report is noted, but the value does not change on an assertion alone; it waits for something checkable.
Missing coverageRecorded as an unknown for that page, not filled with an estimate.
Wording too close to a sourceThe passage is rewritten until it is this site's own phrasing.

What a Reader Can Check Without Contacting Anyone

Every page prints the date it was last revised, and every factual page lists its sources with publisher, URL and the date each was read. If the revision date predates a patch you have installed, treat the value as unconfirmed for your build until the page moves.

Conflicting values are visible on purpose. A table that shows two numbers with two publishers is not an unfinished page; it is the honest state of a contested fact, and you can pick the value that matches your own build.

The Sources & methods page states the grades used on every row, so a claim labelled single source can be weighed accordingly instead of being read as tested.

Correction Log

Changes that alter a published value are logged with the page, the old value, the new value and the reason. The log is empty because this site's pages are new, and it grows from the first accepted report rather than being back-filled with entries nobody can verify.

Cosmetic edits — a typo, a reordered list, a reworded sentence that keeps the same fact — do not enter the log; they only move the page's revision date.

DatePageChangeReason
——No corrections logged yetLog opens with the first accepted report

What This Page Does Not Cover

This is a corrections process for factual errors: values, conditions, locations, counts and dates. It is not a requests channel for coverage, a place to dispute a review score another outlet gave the game, or a way to get a page changed because a value is inconvenient.

Disagreements about game design, difficulty or whether a boss is fair are not corrections. They belong in the discussion of the game, not in this site's log.

Page Dates

Published November 2, 2026. Last revised November 2, 2026. The same two dates are emitted as datePublished and dateModified in this page's structured data, so what you read here matches what a crawler sees.

Also in this section