Skip to content
GAMEVERITY

Change control

Corrections become part of the record.

A corrected fact should not disappear without context. Material changes are tied to a version entry and the page returns to verified only after review.

Last updated September 2, 2026

Submit a correction

Point us to the exact page and claim. A report opens an internal review; it does not become verified until the evidence is checked.

Do not include passwords, account data, or other sensitive details.

What triggers a correction

  • A value conflicts with the named live build.
  • A screenshot, route, or layout belongs to a different patch.
  • A probability or count was presented with more certainty than the evidence supports.
  • A game update changes the entity or invalidates an earlier method.

How corrections are handled

  1. Downgrade the affected field to partial when the claim is in doubt.
  2. Preserve the stable URL and register the issue against a version.
  3. Recheck the live build or primary source.
  4. Publish the corrected value and a concise material-change note.

Correction standard

A correction must identify the game version and the field in dispute. Community reports can open a review, but a repeated claim does not become verified until it is checked against the live build or an authoritative primary source.