Chunk and player storage settings
Configure I/O worker counts, region compression, and save-queue warnings.
When to change them
Start with automatic worker sizing. Long queues can mean slow/full storage, permissions, or repeated failures. More workers do not repair a saturated disk. Player-save warning thresholds are advisory; increasing them hides warnings rather than bounding retained snapshots.
Option reference
All options below belong in nusa-global.yml and require a full restart. Missing keys use defaults. Ranges include both ends unless marked >.
| Complete key | Type / default | Range / unit | Purpose, effects, and when to change |
|---|---|---|---|
async-chunk-io.threads | integer0 | 0..256 threads | Zero selects max(1, JVM processors / 2). More threads can increase disk contention; change only after queue/storage measurement.Applies when: feature-flags.async-chunk-io |
region-file-compression.level | integer3 | -5..22 level zstd | Zstd writer level. Higher values can increase CPU cost and do not change rollback compatibility.Applies when: feature-flags.region-file-compression |
async-playerdata-save.threads | integer0 | 0..256 threads | Zero selects min(2, max(1, JVM processors / 2)). Player mutations still happen on main.Applies when: feature-flags.async-playerdata-save |
async-playerdata-save.warn-queued-players | integer1024 | 1..2147483647 players | Advisory player-count warning threshold, not a rejection cap. The newest snapshots remain retained above it.Applies when: feature-flags.async-playerdata-save |
async-playerdata-save.warn-queued-mib | integer64 | 1..2147483647 MiB | Advisory queue-memory warning. Do not raise it to hide disk failures; retained memory can still grow.Applies when: feature-flags.async-playerdata-save |
Verify and recover
Restart, test chunk loads and login/logout, then stop cleanly to check save draining. Inspect disk and queue warnings. State capture/application still belongs to main. The storage guide explains formats and crash limits.
Read rollback compatibility before changing the zstd writer. Restore the prior config and restart if a tuning change does not help; never experiment on your only world copy.