Troubleshooting¶

divider

Custom catches do nothing¶

Confirm features.permissions.enabled matches your setup. With permissions enabled, players need at least mythicrod.drops.global.
Run /mythicrod validate. The output names every disabled or malformed entry.
Check plugins/MythicRod/drops.yml actually contains entries for the biome you're fishing in.

Run /mythicrod testroll <biome> 5000 and look at the histogram.
Verify that the drop's weight is at least 1 (load-time clamping logs a warning when it isn't).
Verify that the drop's permission (if any) is held by the player.
Verify that the drop's biomes: list (if any) actually contains the player's current biome key.

Confirm Nexo is installed and enabled on the server.
Confirm the identifier matches an existing Nexo item.
NexoItemProvider consults NexoItems.exists(id) before resolving; check the server log for the corresponding warning.

Reload is single-flight. If a reload is already in progress, subsequent /mythicrod reload invocations report already_running rather than bouncing. Wait a second and retry.
The reload swaps DropManager's live drop table only after the new file parses cleanly. A parse error keeps the previous valid state in place; the exact error appears in the console.

Inventory mutations, scheduled tasks, and entity calls all go through PlatformScheduler. If you see a region-thread warning, open an issue with the stack trace and the exact build numbers of Folia and the plugin.
paper-plugin.yml declares folia-supported: true. A live smoke test on Folia 26.1.2 build 8 covered the GUI, drop rolls, statistics writes, language reload, and /mythicrod give. /mythicrod status reports Runtime: Folia when the plugin is running on a Folia jar; if you see Runtime: Paper while booted on Folia, the detection failed and is the bug to report.
The first place to look on a Folia-only crash is the schedulers list in the developer docs at Folia threading. A common cause is third-party code touching Bukkit state inside a MythicRod async callback.

bStats setup is best-effort. A runtime issue during initialisation logs a warning and the plugin continues without metrics. Restart the server and check the log.