Backups

ScalaPlot includes a full backup system for plots, both automatic and manual.

Configuration

In the backup section of config.yml:

backup:
  auto_backup: true
  interval_minutes: 60
  max_backups_per_plot: 5
  storage_path: "backups"
  backup_on_deletion: true

Key	Description
auto_backup	Enables periodic automatic backups
interval_minutes	Interval (in minutes) between one automatic backup and the next
max_backups_per_plot	Maximum number of backups kept per plot (oldest ones are deleted)
storage_path	Backup storage path, relative to the plugin folder
backup_on_deletion	Automatically creates a safety backup before a plot is deleted/reset

Commands

/plot backup create
/plot backup list
/plot backup restore <name>

• create — manually creates a backup of the plot you’re standing in.
• list — lists all available backups for your plot.
• restore <name> — restores a specific backup, overwriting the plot’s current content.

Required permission for all subcommands: plot.backup. Only the plot’s owner or a member with plot.admin can manage backups.

Caution

Restoring a backup overwrites the plot’s current content. If you want to keep the current state, create a new backup first with /plot backup create.

Storage format

Internally, ScalaPlot stores blocks in a compact range-based format (block ranges instead of individual blocks), split at chunk boundaries. This drastically reduces memory usage during restores compared to a block-by-block format, keeping backups efficient even on very large plots.

Cloud backups (Premium)

The server_name field in config.yml is used by the Premium backup system, which can save backups to the storage provided by the license vendor instead of the server’s disk. This lets you, for example, find and restore a backup made on another server on a different one.