World Backups
Last updated
BuildSystem includes a database-linked backup subsystem. Backups copy region files and world configurations, sending them to local or remote storage drivers.
If configured in config.yml (world.backup.auto-backup.enabled), backups run on a recurring schedule.
Interval: Set in seconds via interval (e.g., 900 for 15 minutes).
Active World Filtering: If only-active-worlds is set to true, background timer counts increment only when a registered builder is present in the world.
Administrators or builders can force an immediate backup of their current world:
Command: /worlds backup create
Permission: buildsystem.backup.create
To view the history of backups for the current world:
Command: /worlds backup
Permission: buildsystem.backup (requires being the world creator or having the buildsystem.admin bypass permission).

Open the backups list (/worlds backup).
Click on the target backup item (named with the timestamp of creation).
Confirm the restoration prompt.
Restoring a backup overwrites the current world directory and is non-reversible. To avoid database locks or data corruption, restoring the server's primary spawn world (usually world) is highly discouraged without taking a manual backup first.
Last updated