BoostedTrees — Updates & backups

BoostedTrees — Updates & backups

Update notifications
The plugin checks SpigotMC for a newer version and reports it in the console; players with boostedtrees.update receive join notifications. It does not download or install updates automatically.

Updating and backing up

1. Stop the server and create one consistent backup of the worlds and the complete BoostedTrees folder, including database, task files, queue and transaction journal.
   
2. Replace the plugin JAR with the intended release. Keep the existing data folder and use a full restart.
   
3. Check startup errors, /boostedtrees status and saved task states. Resume only the tasks you want to continue.
   
4. For recovery, stop the server and restore matching worlds and plugin data from the same backup. Restoring an old backup also reverts later world changes. There is no built-in backup or undo command.
   

Migration and reload
A legacy boostedtrees: configuration is copied to config-backups/config-before-cleanup-<timestamp>.yml before migration. Activation, world selection, custom-tree chance, speed and disabled species are migrated. Old observation/off modes stay disabled. Old technical options and custom mapping overrides are replaced by built-in rules; their original values remain in the backup.

Reload updates configuration and services; it does not replace the running JAR, regenerate existing forests or automatically resume saved tasks. Keep boostedtrees.db, forest-tasks/, replacement-journal/ and large-tree-queue.yml when upgrading.