World Snapshot Configuration

snapshot.yml controls the virtual world view used by systems that read snapshots. Review its coverage and capture limits before changing them.

What this file controls

Defaults enable virtual snapshots with horizontal and vertical subchunk radius of one, a 15,000 ms inactive-subchunk expiry, up to 60 capture jobs per tick, and up to 27 synchronous subchunks during joins or teleports.

Complete movement coverage is required; inactive queued loads are canceled and debug logging is off by default. These values control snapshot collection, not a server performance guarantee.

Only checks that use snapshot state are affected by snapshot coverage. Check the relevant setting before changing this file to address a specific detection.

Adjust snapshot coverage with its consumers in mind

  1. Back up snapshot.yml and compare its coverage and capture limits with the defaults.
  2. Review complete-movement-coverage, inactive-load cancellation, and debug logging before changing expiry or capture limits.
  3. Confirm the check you are tuning uses snapshot state; coverage changes do not affect every check.
  4. Change one value at a time and review server behavior before applying another change.

Apply and verify changes

After editing a setting, use the reload command when that setting supports reload. If the change does not take effect, check the configuration troubleshooting guide for the setting’s restart requirements.

Browse all documentation