Bug Reporting Guidelines
Before submitting a bug report, please review the guidelines below. This helps us track issues efficiently and prevents duplicate reports.
What to Include in a Bug Report
- What happened: A clear description of the issue.
- What you expected: What should have happened instead.
- Steps to reproduce: How we can trigger the bug.
- Location: Coordinates or biome if relevant.
- Screenshot or video: If it helps explain the issue.
- Any error messages: Chat or console messages.
What NOT to Report
- Known bugs listed on the Known Bugs page.
- Issues caused by outdated clients or missing mods.
- Lag spikes during world generation or first-time chunk loading.
- Normal Cobblemon behavior (e.g., Pokémon despawning naturally).
Severity Levels
- Low: Visual glitch, typo, minor annoyance.
- Medium: Affects gameplay but not progression.
- High: Blocks progression or breaks a feature.
- Critical: Crashes server or corrupts data.
Before Reporting a Bug
Please check our Known Bugs page first. Many issues may already documented, and you may not need to submit a report.
Ready to Report a Bug?
If your issue is not listed on the Known Bugs page and follows the guidelines above, please submit it through our contact form: