Skip to main content

​
The plugin will not load

Check the for the real error.
  • Server version. Paper or Spigot 1.19 or newer.
  • Java version. 17 or newer. Verify with java -version on the host, not the control panel.
means Java is too old.

​
Database errors on startup

See Storage and databases.

​
/k10 and above do not exist

Slots above 9 need kits.max-slots raised, and register only at startup. Full restart required; a will not do.

​
Config migration failed

Fix the file or folder named in the console error, then restart. The original config remains in place; backups are beside it.

​
Kit data is still loading

Wait for the database read to finish. If the plugin says data is unavailable, fix the storage error and rejoin. Editing stays blocked to protect existing kits.

​
A kit save failed

The console reports the storage error. Failed writes are retried after a successful connection check. If shutdown still has failed writes, it retains them in failed-kit-writes-<time>.yml in the plugin folder. Keep that file with your database backup and ask for help before switching backends. See Backups and Upgrading.