Emergency safemode

Safemode also bypasses all six Nusa security guards. Paper validation remains, but Nusa’s extra protection is reduced. Restrict player access during diagnosis. This is not everyday performance tuning.

Inspect without activating

nusa safemode status
nusa safemode json

These only read state. Use console/operator or nusaspigot.command.safemode. JSON includes transition state, cleanup failures, and retained resources.

Activate the runtime bypass

nusa safemode with no argument activates it until restart. It is not an on/off toggle and has no off subcommand. Configuration files are not rewritten. Fix the cause, then restart fully to use saved settings again.

The console path schedules main cleanup: discard AI/tracking candidates, stop pregen admission, handle pending tab/position delivery, clear caches, and restore channel pipelines in order. Accepted saves/packets drain safely. Check transition completion and preserve redacted failure details if needed.

Resources retained until shutdown

Region I/O ownership/executors, main chunk-commit ownership, native channels, listening-socket Fast Open, network dependency versions, and zstd readers retain their safe lifecycle. The process does not become an unmodified Paper binary.

Safemode does not convert zstd worlds, disable licensing, or establish identical startup resources to Paper. Management features such as setup/status keep their own settings.

Return to normal operation

Diagnose on staging, change only the relevant plugin/setting, back up, then stop and start again. Verify safemode is inactive, required guards are enabled, and the issue is resolved. See plugin troubleshooting.