Code status, reward, cost, rate, formula, recommendation, official destination, or source identity receives a visible history entry.
Corrections Policy
Quick answer: corrections are judged by evidence, not by who submits them. The editor verifies the exact page and source scope, updates shared data before dependent pages, records a real modified date, and publishes a concise change note when the correction affects player decisions.
Manual evidence reviewShared data firstMaterial changes logged
Review workflow
From report to public correction
- 01
Receive
Log the affected URL, exact claim, proposed correction, source, date, and contributor permission.
- 02
Reproduce or corroborate
Check the exact game and current screen or verify the first-party source; preserve conflicts when evidence still disagrees.
- 03
Change the shared source
Update the code, Job, Property, item, region, source, or update-log row before dependent prose and calculators.
- 04
Verify every consumer
Run tests, types, build, link checks, schema checks, and inspect affected pages at desktop and mobile widths.
- 05
Disclose
Update dateModified only on genuinely changed pages and add a material revision to the page or update log.
Correction levels
What receives a visible note
A change that prevents a likely misunderstanding may be logged on the page even when the underlying row is unchanged.
Typos and layout repairs are corrected without pretending that game evidence was rechecked.
The disagreement remains public until stronger current evidence supports a status change.
Contributor privacy
Identity is private by default
A contributor's name or handle is not published without permission. Submitted captures are reviewed for account names, private messages, purchase data, and other personal information before any public use. Raw files are not promised publication.
Update history
What was rechecked
- Published submission, verification, severity, disclosure, and contributor-privacy rules.Site-wide correction standard