Installation

Setting up BusyHub on your Minecraft server is a quick, config-only process — no database, no external dependency. See Requirements for supported versions.

Setup Steps

  1. Download: Get BusyHub.jar.
  2. Install: Place the .jar file into your server's plugins/ directory.
  3. Start Server: Start (or restart) to generate config.yml, menus/main.yml, and data.yml under plugins/BusyHub/.
  4. Set your spawn: Stand where you want players to land and run /busyhub setspawn.
  5. Point the compass at your servers: Edit the [BUNGEE] targets in menus/main.yml — see Server-Select Compass.
  6. Reload: Use /busyhub reload to apply any config change while the server is running.

Verifying the install

BusyHub logs which schedulers/Folia detection it resolved on startup:

[BusyHub] BusyHub enabled. Folia detected: false

If you're on a Folia build and this reports false, you're actually running classic Paper — that's expected, not an error; BusyHub schedules identically either way.

Updating

Drop the new jar in and restart. BusyHub does not migrate configuration automatically — back up config.yml, menus/*.yml, and data.yml before updating across a version that adds new config keys, and re-apply your customizations to the regenerated defaults if needed.

Troubleshooting

  • The compass does nothing when right-clicked. Check compass.enabled in config.yml — it's the master switch, checked before anything else, and applies to every player with no exceptions. See Server-Select Compass.
  • Menu items don't send players anywhere. [BUNGEE] requires an actual BungeeCord/Velocity proxy in front of the server; on a standalone server it logs a warning and no-ops. See Menus & Actions.
  • A world isn't being protected. Check disabled-worlds in config.yml — it exempts a world from every protection.* flag, including invincibility. See World Protection.

More issues are consolidated in Common Issues.