Snapshots & Rollback
Mistakes happen: a misfired TNT cannon, a grief from a trusted player who turned out not to be trustworthy, a build that went sideways. Snapshots let an island save a point in time and roll back to it, without an operator or a manual world edit.
| Command | What it does |
|---|---|
/is snapshots | View and restore your island's snapshots |
/is admin snapshot <player> | Staff: open and restore any player's snapshots |
How it works
A snapshot captures the state of the island so it can be restored later. Players manage their own snapshots from the menu and restore one when they need to, which takes the recovery burden off your staff entirely.
snapshot:
enabled: true
auto-interval-minutes: 0 # automatic captures of every island; 0 = manual only
max-per-island: 5 # oldest pruned once past this
radius: 64 # captured square's half-extent (blocks), clamped to island size
min-y: 50 # keep this band tight to where islands actually have blocks
max-y: 150
blocks-per-tick: 4096 # restore speed; higher = faster but more work per tickCapture and restore are Folia-safe and throttled (blocks-per-tick) so a rollback never freezes a region, and snapshots are stored compressed (a block palette), so keeping a few per island stays cheap. After a restore, the island's worth and level are recomputed from a fresh scan so the leaderboard reflects the rolled-back terrain. Staff can open and restore any player's snapshots with /is admin snapshot <player>.
Rolling back to a snapshot replaces the current island state with the saved one. Anything built after that snapshot is lost, so confirm before restoring. IgniteSky asks first.
Snapshots make trusting people far less risky. If an invited player damages a build, the owner restores a snapshot instead of filing a report, which keeps your moderation queue empty.