Migration Guide

Moving from PyroFishingPro takes one restart. BusyFishing reads Pyro's folder (and its MySQL database, if it used one) and never changes them, so you can always go back.

The short version

  1. Back up your server, as you would before any plugin change.
  2. Stop the server.
  3. Remove the PyroFishingPro jar (and PyroLib if nothing else needs it). Keep the plugins/PyroFishingPro/ folder.
  4. Add the BusyFishing jar.
  5. Start the server.

Switch on the same Minecraft version Pyro ran on, or a newer one. Items stored in Pyro's fish bags are saved for that version, and a server can't load items from a newer version than its own.

On that first start BusyFishing moves everything over by itself and writes a report to plugins/BusyFishing/pyro-import-report.txt. The startup block shows a Pyro row while this is going on.

What moves over

From PyroFishingPro To BusyFishing
config.yml settings The matching module configs (each changed file is first copied to <file>.pre-import)
fish.yml, bait.yml Taken over whole: BusyFishing reads the same format
tournaments.yml settings modules/tournaments/config.yml
Menu layouts Item positions and materials in each module's gui.yml
Player data (PlayerData/*.yml or the four MySQL tables) Level, XP, XP needed, entropy, skill points, skills, stats, delivery upgrades and active deliveries, boosters, fish bag, money limit
codexdata.yml The codex
totemdata.yml Totems, with their upgrades, slots and passives

Items need no import. Pyro's fish, crab claws, entropy crystals, lures, baits and augmented rods keep working as they are, while pyro-compat is on.

Messages are not moved by default. BusyFishing keeps its own wording. If you rewrote Pyro's messages and want to keep them, set import-messages: true in modules/pyro-import/config.yml and run /fish import pyro configs.

Players nobody misses

  • Players who are online during the first import are moved the next time they log in.
  • A player who has Pyro data but no BusyFishing data is moved as they log in, at any time later, and told their progress came with them.
  • A player who already has BusyFishing data is never overwritten.
yaml
# modules/pyro-import/config.yml
auto-migrate:
  # Move everything over once, the first time the folder above is found.
  on-first-start: true
  # Move a player who has PyroFishingPro data but no BusyFishing data yet as they log in.
  on-join: true
  # Tell those players their progress came with them.
  notify-player: true

The first-start move runs once. It is marked done by plugins/BusyFishing/.pyro-migrated; delete that file to run it again on the next start.

If the Pyro jar is still in plugins/

Paper won't load PyroFishingPro next to BusyFishing, because BusyFishing also answers to the name PyroFishingPro so that Pyro addons keep working. The console then shows errors like these, which are expected:

[ModernPluginLoadingStrategy] Ambiguous plugin name 'PyroFishingPro' for files ...
[ModernPluginLoadingStrategy] Could not load plugin 'PyroFishingPro-4.9.35.jar' ...

Pyro stays off, so its data can't change during the move, and BusyFishing takes over as usual. BusyFishing logs a warning naming the jar. Delete the jar to get rid of the errors.

Running it by hand

/fish import pyro configs     # config files, fish, bait, menus
/fish import pyro players     # player data, the codex and totems
/fish import pyro all         # both, configs first

Add --force to overwrite players who already have BusyFishing data. Online players are skipped and moved on their next login. Permission: busyfishing.command.import.

After the move

  • Ranks keep working: Pyro's pyrofishingpro.* permission nodes are accepted while pyro-compat is on.
  • Scoreboards and holograms keep working: %pyrofishingpro_*% placeholders answer too. Switch them to %busyfishing_*% when convenient.
  • /pyrofish still works.
  • Addons written for PyroFishingPro keep loading, see Developer API.
  • Once every player has logged in at least once, you can switch the pyro-import module off in config.yml. Keep the Pyro folder if you want pyro-compat: auto to stay on.

What is different

BusyFishing has its own fish set, wording and winter event (Frostfall instead of Crabmas), and adds bosses, a crafting menu, fish bag items and invitation parties. Your imported fish.yml replaces the default fish set.