What to send
Use this page as the guide for corrections, missing links, and content updates. Keep every request short, specific, and source-backed when possible.
Pre-submit checklist
| Item | What to include |
|---|---|
| Page URL | Include the exact page where the issue or idea belongs. |
| Issue type | Choose correction, missing page, stale update, broken link, verified data, or source question. |
| Evidence | Add an official link, in-game screenshot, store page, or patch note when possible. |
| Expected change | Explain the wording, route, field, date, reward, marker, or database row that should change. |
| Verification status | Say whether the detail is official, in-game verified, beta-only, or still uncertain. |
Issue types
| Issue | What to include | Best follow-up page |
|---|---|---|
| Wrong fact | Page URL, wrong line, and correct source. | Source policy |
| Missing page | Topic idea, search intent, and related pages. | All pages |
| Stale update | Old date, new date, and supporting source. | Version history |
| Broken link | Source page, link target, and browser context. | Bug report |
| Unclear route | Issue type, page URL, and what you want changed. | Feedback hub |
Priority order
- Broken links and wrong URLs.
- Official-source corrections.
- Stale launch timing or event data.
- New page requests and content expansion notes.
Contact FAQ
Can I request a new page?
Yes, as long as the topic has clear search value and fits the site structure.
Support routes
Help center
Start here if you are unsure where a request belongs.
Feedback hub
Route corrections, data submissions, media issues, and page requests.
Community hub
Use this for submissions, fixes, and source links.
Contribute
Review the full verified-data workflow.
Version history
Check what changed before sending a correction.