Troubleshooting
BusyFishing doesn't start
- "BusyFishing needs Paper or Folia 1.21 or newer": the server runs Spigot or CraftBukkit. Switch to Paper.
- Unsupported API version / class version errors: the server or Java is too old. See Requirements.
No custom fish are caught
Check, in order:
- The
fishmodule is on inconfig.yml. - The world isn't in
disabled-worldsinmodules/fish/config.yml. disable-all-fishingisfalse.catch-permission.enabledisfalse, or the player hasbusyfishing.fish.- No WorldGuard region sets
busyfishing-fishingtodenythere. custom-fish-only-during-tournamentsinmodules/tournaments/config.ymlisfalse, or a tournament is running.- The player isn't using an AFK fish farm (
allow-auto-fishers).
Then stand at the spot and run /fish simulate 100 to see what comes up.
A fish never shows up
Each fish has its own conditions in fish.yml: biomes, time, weather, height, worlds, regions,
season and a permission. A fish listed under a bait in bait.yml can only be caught with that
bait on the rod.
Selling pays nothing
Install Vault and an economy plugin, or turn on command-selling in modules/shop/config.yml.
Check money-limit too. See Vault.
A menu says "no permission"
menu-permissions in config.yml is on for that menu. Give the listed node or switch the gate
off. See Menus.
"Ambiguous plugin name 'PyroFishingPro'" at startup
The PyroFishingPro jar is still in plugins/. Paper won't load it next to BusyFishing, which answers
to that name for Pyro addons. This is expected and harmless; delete the Pyro jar. See the
Migration Guide.
Pyro data didn't move
Read plugins/BusyFishing/pyro-import-report.txt. Common causes:
plugins/BusyFishing/.pyro-migratedexists from an earlier run. Delete it, or run/fish import pyro all.- The Pyro folder isn't named
PyroFishingPro. Setsource-folderinmodules/pyro-import/config.yml. - A player already had BusyFishing data. They are never overwritten; use
/fish import pyro players --forcewhile they are offline.
See the Migration Guide.
Config changes don't apply
Run /fish reload after editing. Changes to command-aliases, pyro-compat and the database
settings need a restart.