How to help
The best contributions make the site clearer, more accurate, or easier to verify. Good submissions are short, source-backed, and tied to a specific page or database row.
Avoid leaks, private test data, or any claim that cannot be checked against a reliable source.
Contribution tracks
Use these tracks to route help into the right workflow. This keeps community input useful without mixing translation, verification, corrections, and page requests into one vague inbox.
| Track | Best for | Route | Rule |
|---|---|---|---|
| Feedback routing | Choosing the right route for corrections, data, bugs, media issues, page requests, or language suggestions. | /feedback | Start with one exact page, issue type, and expected change. |
| Translation | Future multilingual notes, terminology consistency, and localized page suggestions. | /contributors | Do not translate unverified gameplay claims as confirmed facts. |
| Data verification | Checking official links, in-game screenshots, patch notes, dates, codes, events, and source status. | /data-verification | Attach a source and date for every high-impact claim. |
| Correction | Wrong wording, broken links, stale route text, missing related pages, or outdated status notes. | /corrections | Point to one exact page and one exact problem. |
| Page suggestion | New guide, database, Kibo, map, tool, or support pages with clear search intent. | /contact | Explain the search query and the closest existing page. |
Contribution types
| Type | Good contribution | Best page |
|---|---|---|
| Correction | Wrong wording, bad link, stale status, or missing internal route. | Corrections |
| Verified data | Official or in-game confirmation for a Kibo, map, event, or database field. | Submit data |
| Source check | A reliable source that supports a page update. | Official links |
| Issue report | Broken page behavior, missing hub link, or tracker problem. | Bug reports |
Contribution rules
- Use official pages, in-game screenshots, patch notes, or store pages whenever possible.
- Label beta data clearly until launch confirms it.
- Keep every submission attached to one page or one row.
- Use short notes that make it easy to verify and update later.