Updates and backups
- Latest version
- 3.6.0
- Minecraft
- 1.21.4 - 26.3
- Platforms
- Spigot, Paper, Folia, Purpur
- Minimum Java version
- 21+
This article was written for 3.5.5. The latest stable release is 3.6.0; use the current requirements above.
Updates and backups
Updating the plugin
The plugin checks for new releases and can notify users with the update-check permission. This project has an update notifier, not an automatic JAR downloader or token-based updater. To update, stop the server, back up data, replace the JAR and start again. Keep only one active copy of the plugin JAR.
Backup and restoration
Back up the entire plugin folder, any configured MySQL table and managed world folders while the server is stopped. SQLite files and accompanying journal files must be backed up consistently. Keep Config.yml, Messages.yml, Worlds.yml, myEQ.yml and PlayerData mirrors with the database. Restore related data together from the same backup.
Startup adds missing default configuration/message entries while retaining custom values; PlayerData storage also adds its own defaults and can import legacy UUID records. Do not edit schema version markers manually. When testing an update, check permissions, command registration, flags, My EQ, stored player entries and world teleports. World deletion is permanent and has no built-in trash or rollback.
Updating the plugin
The plugin checks for new releases and can notify users with the update-check permission. This project has an update notifier, not an automatic JAR downloader or token-based updater. To update, stop the server, back up data, replace the JAR and start again. Keep only one active copy of the plugin JAR.
Backup and restoration
Back up the entire plugin folder, any configured MySQL table and managed world folders while the server is stopped. SQLite files and accompanying journal files must be backed up consistently. Keep Config.yml, Messages.yml, Worlds.yml, myEQ.yml and PlayerData mirrors with the database. Restore related data together from the same backup.
Startup adds missing default configuration/message entries while retaining custom values; PlayerData storage also adds its own defaults and can import legacy UUID records. Do not edit schema version markers manually. When testing an update, check permissions, command registration, flags, My EQ, stored player entries and world teleports. World deletion is permanent and has no built-in trash or rollback.