🐛 Reporting bugs & ideas¶
Found a bug, or have an idea? Post it in the Discord — that is the whole process. You do not need a GitHub account. A bot turns your post into a tracked issue, replies in your thread with what it needs from you, and posts back there when it is closed.
One page for every mod: the process is identical, and the mod-specific detail is in the tabs below.
- You open a post in #mod-tickets and pick two tags: the mod and the type.
- The bot reads it within ~10 minutes and files a tracked issue, labelled from your tag.
- The bot replies in your thread saying what it still needs from you, if anything.
- shiero fixes it in a release.
- The bot posts back in your thread when the issue closes. 🎉
Pick the right tag¶
The mod tag sends the report to the right place. The type tag decides how it is handled — and what the bot asks you for. It is the one thing worth getting right.
| Tag | Use it when | What the bot does |
|---|---|---|
| 🚨 Crash | the game closes, freezes or fails to start | jumps the queue; asks for the crash report |
| 🐛 Bug | something works, but wrong | asks for versions, loader and steps |
| 💡 Idea | you want something that does not exist yet | files it as a feature request — no logs needed |
| 💬 Feedback | an impression, a balance opinion, a "this felt off" | recorded; nothing else needed from you |
What makes a great report¶
- What you did, what you expected, and what happened instead.
- The mod version, your loader (Fabric or NeoForge), and whether you are on a modpack.
- If the game crashed: attach
crash-reports/crash-*.txt, orlogs/latest.logif there is no crash report. The stack trace is what turns a hunt into a fix. - A screenshot or a short clip, if it is something you can see.
A report that gets fixed fast
Placing a picnic table underwater near coral crashes the client. MC 1.21.1, Cobblemon 1.7.3, Picnic 1.26.0, Fabric. Happens every time; crash report attached.
Where to find your logs¶
Both live in your game folder — the instance folder if you use a launcher with profiles:
logs/latest.log— the log of the last session. It is overwritten every launch, so grab it before starting the game again.crash-reports/crash-<date>.txt— one file per crash, written only when the game crashes.
| Launcher | How to open the folder |
|---|---|
| Modrinth App | open the profile, then the ⋮ menu → Open folder |
| CurseForge | right-click the profile → Open Folder |
| Prism Launcher | select the instance → Folder |
| Vanilla launcher | %appdata%\.minecraft on Windows, ~/Library/Application Support/minecraft on macOS |
Attach the file to your post. If it is too big, paste it on mclo.gs and share the link.
Extra detail, per mod¶
- Where it happened: the zone name the mod showed you — a route, an area, a town, or the Wild.
- Whether the world was generated with this version of Routes or an older one, since roads are baked in at worldgen.
- For map problems: which map mod (Xaero's Minimap, World Map, JourneyMap) and its version.
- Which rule misbehaved: one catch per zone, permadeath, nicknames, shiny clause, level caps, or a Soul Link pairing.
- Where you were: the zone name the mod showed you.
-
For Soul Link: how many players were linked, and what each was doing at the time.
-
Your Routes version as well as the Nuzlocke one — this mod is an add-on and the two move together.
Zone problems are usually Routes problems
"One catch per zone" is defined against Routes' zone model — the routes, areas and towns it generates are the capture zones. If the zone itself looks wrong (missing, badly shaped, oddly named), that is a Routes report, not a Nuzlocke one.
- Whether it was the re-roll, the social side (benches, shiny aura, care) or the trainer battles.
- What was around the table: biome, other spawners, and whether a modpack tuned the spawn rules.
- For furniture or model issues, which other furniture mods are installed.
- Which HM, whether it was a partner HM, an aura or a mount toggle, and which Pokémon was lending it.
Cooldowns are configurable
Before reporting "this HM is too slow", check Configuration — every HM's cooldown and power is a server-side setting, so a modpack may have tuned it away from the defaults.
Suggesting a new HM? Those are the most common request, and plenty of the ones that shipped started that way. The ones that get built fastest describe: the Pokémon move it is based on, what it should do in Minecraft, and whether it feels like an active (press to use, costs hunger) or a toggle (passive, blocks part of your hunger bar).
- The output of
/raidicons reportwhile aiming at the den that is misbehaving. It carries almost everything a report on this mod needs, and it goes tologs/latest.logtoo. (Plain/raidiconsopens the settings screen.) - Which Xaero mods you have — the minimap, the world map, or both — and their versions.
- Your Cobblemon Raid Dens version. The mod reads that mod's blocks by name, so a den it stops recognising is usually a Raid Dens update.
Icons fill in as you walk
The mod only sees dens in chunks your client has already been sent. A map that is not covered in markers after teleporting somewhere new is working correctly, not failing.
- The output of
/champions sp <slot>for the Pokémon involved. It shows whether the Pokémon is in training, its stat points, effort values and IVs, and its final stats. - What you pressed — Save, Train, Load, Store or Delete — and on which page of the summary.
- Whether the server changed any settings:
/champions configlists them all.
Stats look wrong?
A stat point is +1 to the stat at any level, applied before the nature. Compare with the numbers on Stat Points before reporting a formula bug.
- Your Minecraft version (1.21.1, or which 26.x) and loader: the mod ships a jar for each.
- What you carved and where: the block, the text or symbols, the font and the dye. For a face
that looks wrong, the output of
/treecarve whowhile looking at it (it needs operator level 2). - Whether the server changed any settings:
/treecarve configlists them all.
Carvings gone after an update?
A world moved from Minecraft 1.21.1 to 26.x loses its carvings. That is a known limitation, not something to report.
- The battle: wild, trainer or another player, single or double, and which Pokémon fought.
- The battle log lines around the knockout: they show what each Pokémon was paid.
- For the move screen: whether it opened, what you dragged, and whether the battle ended while it was open.
- Your Cobblemon version (1.7 or 1.8) and any EXP setting changed in Cobblemon's config.
The amounts are Cobblemon's
The mod pays at each knockout what Cobblemon would pay at the end. If the amount looks off, check the settings on Getting Started first: a Lucky Egg, Exp. Share or a modpack multiplier changes it here too.
- Which settlement: Village, Town or gym Town, and its coordinates (
/locategives them). - Whether the world was generated with this version of PokeTowns, since settlements are built as chunks generate.
- Whether PokeTowns: Replace Vanilla Villages is on, and the spacing chosen on the PokeTowns tab.
- For gym problems: whether the COBBLEVERSE datapack is installed, and its version.
What happens next¶
Your post becomes an issue labelled from its tag, and the bot replies in the thread so you know it landed. When the issue is closed, it posts back there — saying whether it was fixed or closed without a change, because those are not the same thing and you deserve to know which.
Everyone who reports gets thanked on the mod's community credits page: Routes · Nuzlocke · Picnic · Cobblemon HMs · Raid Icons · Champions Training · Mid-Battle EXP. 💚