Feedback overview
This page turns community help into a clean operating system for the guide. Readers can report a mistake, submit verified data, flag a media issue, request a page, or suggest future language work without guessing which support page to use.
Feedback should improve accuracy, freshness, navigation, media quality, or future search coverage.
Feedback types
| Type | Best for | Route | Evidence |
|---|---|---|---|
| Data correction | Wrong wording, stale status, missing source labels, or outdated page facts. | /corrections | Page URL, current text, corrected text, and source. |
| Verified data | Kibo habitats, map markers, codes, events, materials, boss drops, and database fields. | /submit-data | Official link, in-game screenshot, date, server or platform, and exact value. |
| Site bug | Broken links, missing pages, layout issues, bad routing, or tool behavior problems. | /bug-report | Affected page, browser or device, expected behavior, and what happened. |
| Media issue | Missing screenshots, broken video, weak image caption, wrong media source, or gallery gap. | /media | Media page, asset title, source link, and whether the asset is official or site-made. |
| Page request | New guide, database, Kibo, map, tool, event, or FAQ page ideas. | /contact | Search query, target player need, closest existing page, and proposed title. |
| Language suggestion | Future translation priority, localized wording, terminology consistency, or language folder planning. | /languages | Language, page URL, suggested wording, and source terminology if available. |
Feedback pipeline
| Step | Action |
|---|---|
| 1. Receive | Classify the request by type, target page, urgency, and whether a source is attached. |
| 2. Verify | Check official sources, in-game evidence, store pages, patch notes, or existing site data. |
| 3. Update | Patch the affected guide, database row, media caption, tool note, or support page. |
| 4. Record | Update the relevant change log, known issue, bug report, or verification queue when the change is broad. |
| 5. Recheck | Build the site and confirm the affected static HTML route is generated. |
Quality checklist
Exact page
Every request should name one page or one database row first.
Source status
Mark details as official, in-game verified, beta-only, pending, or unverified.
No rumors
Do not route leaks, private test data, or unsupported claims into public guide pages.
Search value
New page requests should include the player question or search phrase they answer.
Media source
Images and videos should keep a source label, caption, and route to the media hub.
Follow-up path
Each accepted report should point to corrections, submit data, bug report, media, or language planning.
Operation queues
| Queue | Examples | Action |
|---|---|---|
| High priority | Broken homepage links, wrong release or code information, incorrect official-source claims. | Fix first and connect to version history or known issues when needed. |
| Database priority | Kibo, character, material, map marker, boss, weapon, quest, or event data with evidence. | Route through submit data and data verification before changing database pages. |
| Media priority | Missing image slot, broken video, weak screenshot caption, or unverified asset source. | Route through media gallery and the relevant character, Kibo, map, or download page. |
| Growth priority | New long-tail page request, language suggestion, FAQ gap, or tool improvement idea. | Check all pages, search intent, and nearest existing hub before creating a new route. |