Bug report database
This table keeps site maintenance visible while the guide grows. It separates actual page bugs from pre-launch data gaps so Google-facing pages stay accurate and easy to update.
| ID | Area | Status | Priority | Issue | Affected page | Next action |
|---|---|---|---|---|---|---|
| BR-001 | Data gap | Waiting verification | High | Character material costs are not verified yet, so calculators must keep editable placeholder values. | Open page | Replace defaults only after official or in-game upgrade tables are confirmed. |
| BR-002 | Map marker issue | Open | High | Kibo, material, boss, enemy, quest, shop, and region markers still need verified coordinates. | Open page | Collect region labels, route screenshots, coordinates, and repeatable location evidence. |
| BR-003 | Media issue | Monitoring | Medium | Media sections rely on official assets and should avoid fan edits, low-quality crops, or unsourced uploads. | Open page | Add only official trailers, screenshots, logos, and source notes. |
| BR-004 | Tool issue | Waiting verification | Medium | Reset timer defaults are configurable placeholders until official server reset time is confirmed. | Open page | Update UTC hour, weekly reset day, shop reset behavior, and event timing after launch verification. |
| BR-005 | Site issue | Monitoring | Medium | Large database growth can create stale internal links if new pages are not connected from hubs. | Open page | Check sitemap, all-pages index, tool hub, database hubs, and related cards after each content batch. |
| BR-006 | Data gap | Open | High | Codes, banners, pity rules, event rewards, shops, and currencies still need official or in-game source confirmation. | Open page | Process launch findings through submit-data, corrections, known-issues, and verification queue pages. |
Report areas
| Area | Use this for |
|---|---|
| Site issue | Broken links, bad canonical paths, layout overlap, missing navigation, or page generation problems. |
| Data gap | Missing official names, costs, dates, rewards, routes, kit fields, or verification status. |
| Media issue | Missing official image, wrong video link, weak screenshot source, or outdated gallery item. |
| Map marker issue | Missing coordinates, wrong region, unverified route, marker category mismatch, or duplicate marker. |
| Tool issue | Incorrect default setting, calculator mismatch, unsaved state, unclear placeholder wording, or broken workflow. |
Status rules
| Status | Meaning | When to change it |
|---|---|---|
| Open | The issue is real and still needs work. | Move after a fix is made or evidence changes. |
| Waiting verification | The page structure exists, but final facts are not confirmed. | Move when official or in-game evidence is available. |
| Fixed | The issue has been corrected and generated successfully. | Keep the row if the fix may need future monitoring. |
| Monitoring | The issue is controlled but should be checked after major updates. | Return to Open if the page breaks or data becomes stale. |
Verification flow
- Check Known Issues before adding a duplicate row.
- Use Submit Data when the report includes a new verified fact.
- Use Corrections when an existing page has wrong wording, source status, or links.
- Use Community Hub for repeat contributors, source discussion, and broader update coordination.
- Record the final page change in Page Updates or Version History.
Bug Reports FAQ
Why keep a public bug database?
It gives the site a clean maintenance trail, helps contributors avoid duplicate work, and supports trustworthy SEO pages as the database gets deeper.