Installation
Installing
- Check your server meets the Requirements.
- Put
BusyFishing-<version>.jarin your server'splugins/folder. - Start (or restart) the server. Don't use
/reloador plugin managers to load it. - Watch the console for BusyFishing's startup block:
[BusyFishing] BusyFishing v26.11.0 on Paper
[BusyFishing] Storage YAML
[BusyFishing] Modules 25/25 enabled
[BusyFishing] Fish 71
[BusyFishing] Hooks Vault, PlaceholderAPI
[BusyFishing] Ready in 109ms
It lists the storage in use, the modules that are on (and which are off), the fish loaded and the
plugins it hooked into. A Pyro row shows up only on servers moving from PyroFishingPro.
What gets created
plugins/BusyFishing/
config.yml root settings and module toggles
messages.yml shared messages (prefix, help, errors)
modules// config.yml, messages.yml and gui.yml for each module
modules/fish/fish.yml the fish
modules/bait/bait.yml the baits
playerdata/ one file per player (unless MySQL is on)
Moving from PyroFishingPro
Remove the PyroFishingPro jar, keep its plugins/PyroFishingPro/ folder, and start the server.
Everything else happens on its own. See the Migration Guide.
Updating
- Stop the server.
- Replace the old jar with the new one.
- Start the server.
Your config files are never overwritten. Keys added in a new version use their built-in default
until you add them to your file, so an older config keeps working. fish.yml and bait.yml are
never touched by the plugin.