Rules for Bug Reporting
1. Scope of Valid Reports
A report is considered valid only if it meets all of the following:
- Related to the current update version
- Reproducible (not a one-time glitch unless clearly critical)
- Not already reported (check existing threads first)
- Not caused by:
- Browser extensions
- Scripts (e.g., Tampermonkey, addons)
- Unsupported browsers
2. Mandatory Environment Information
Reports must include:
- Account Nickname/ID: (Commander, 102589…)
- Account type (Collector, General, Discoverer)
- Device (PC, Mobile, Tablet)
- Browser + version (e.g., Chrome 124)
- Operating System
- Whether any scripts/extensions were active
If this is missing → report is invalid
3. Reproducibility Requirement
A valid report must include:
- Clear step-by-step reproduction
- Expected result
- Actual result
If testers cannot reproduce it → report may be closed
4. Evidence Requirement
At least one of the following is required:
- Screenshot(s)
- Video recording (preferred for UI/interaction bugs)
- Combat/Harvest/etc APIs (if applicable)
No evidence → low priority or rejected
5. Clarity & Structure
Reports must:
- Use the provided template
- Be written clearly (no “it’s broken lol”)
- Focus on one issue per report
