Server management basics

The Crafty controls#

Start launches a stopped server. Stop asks Minecraft to save players, chunks and world files before exiting. Restart performs a normal stop followed by start. Kill forcibly ends the process and risks unsaved data; use it only when normal shutdown has genuinely hung and a backup exists.

The Console shows live logs and accepts server commands. File manager edits and uploads files while respecting Crafty’s storage permissions. Player list shows connections and may expose kick/ban controls. Backups create restore points. Schedules automate backup, restart or commands. Logs preserve diagnostic messages. Metrics/resource usage show trends, not perfect hardware measurements.

A normal maintenance routine#

1. 1
   Tell players and wait for them to leave.
2. 2
   Run a manual backup before changes.
3. 3
   Click Stop and wait for the console to show a clean exit.
4. 4
   Edit or upload files.
5. 5
   Start, watch until Done, then join locally.
6. 6
   Reopen public access only after the local test passes.