Daily operations
Keep routine checks short, changes deliberate, and cleanup recoverable.
At startup
Check readiness, plugin enablement, licensing, and nusa link status when cloud access is used. Run nusa status and investigate new warnings. Initial samples may not represent normal load.
Confirm the latest backup and free disk space. Track world/log/backup growth before the disk becomes full.
While players are active
Use nusa status watch for a bounded investigation, then nusa status off. Correlate reports with profiles, GC, storage, and network behavior. Crowded hubs and spread survival need different context; see measurement.
Avoid changing many flags or deleting entities/world data to chase TPS. Record the reason, before/after values, and gameplay result of each change.
Maintenance routine
- Back up and confirm the archive can be read.
- Test JAR/plugin/config changes on staging.
- Run
stopand wait for exit. - Apply reviewed changes and start again.
- Verify login, saved data, important plugins, and monitoring before ending maintenance.
Use your hosting/backup tools to schedule jobs. These docs do not assume a built-in Nusa backup or restart scheduler.
Safe cleanup
Archive old logs while stopped or through the logging system’s supported rotation. Review backup retention and keep important copies off-machine. Do not delete region/playerdata/UUID/plugin files because they look large without understanding their role.
Runtime files and caches may be needed at startup. If cleaning them, arrange a backup, downtime, and download access first. Prepare a support report before deleting evidence of an unresolved failure.