Skip to main content

Managing Snapshots

Snapshots are Blueprint's primary safety mechanism. This page covers recommended practices for keeping snapshot storage manageable in production.

Snapshot Storage​

Each snapshot is a full copy of the world folder stored on disk. Storage usage depends entirely on your world sizes — a 500 MB world will use 500 MB per snapshot.

Snapshots are stored alongside Blueprint's data files. Check your server's disk usage regularly if your worlds are large or you take snapshots frequently.

Snapshot Limits​

Blueprint does not automatically delete old snapshots. The max-snapshots-per-world value in config.yml (default: 25) is a soft warning limit — Blueprint will warn you when a world exceeds this count but will not block new snapshots.

Periodically review and prune old snapshots using:

/blueprint snapshot list <world>
/blueprint snapshot delete <world> <id>

Pre-Restore Safety Snapshots​

Every time you run /blueprint snapshot restore, Blueprint automatically creates a snapshot of the current world state before applying the restore. These safety snapshots are named with an auto_ prefix.

This means a failed or unwanted restore can always be rolled back:

  1. List snapshots to find the auto-generated one: 
    /blueprint snapshot list <world>
  2. Restore the auto-snapshot: 
    /blueprint snapshot restore <world> auto_<id>
  1. Create the competition world: 
    /blueprint create competition-round1
  2. Snapshot the clean state before teams begin: 
    /blueprint snapshot create competition-round1
  3. After the round, snapshot the final state for judging: 
    /blueprint snapshot create competition-round1
  4. Reset to the clean state for the next round: 
    /blueprint close competition-round1
    /blueprint snapshot restore competition-round1 <clean-snapshot-id>
    /blueprint open competition-round1