Once your server is running, check its backup and restart path before players invest time in the world. These notes describe the 0.7.2 release command definitions and bundled launcher inspected on 15 October 2026.
Configure backups before requesting one
The bundled launcher supplies --backup --backup-dir backups --backup-frequency 30. Because it runs from Server/, this relative backup destination is Server/backups/. A direct Java launch needs its own backup arguments; the following example assumes the same directory layout:
java -jar HytaleServer.jar --assets ../Assets.zip --backup --backup-dir backups --backup-frequency 30In the running console, enter backup and wait for the completion message. The inspected backup command refuses to start before boot finishes or when no backup directory is configured. A request being accepted is not evidence that the archive finished writing.
Keep another copy outside the server machine and test a restore in a separate directory. This is an operating recommendation: the existence of an archive alone does not prove that your recovery process works.
Understand the directories
| Under Server/ | What to preserve or inspect |
|---|---|
universe/ | World and player saves. |
config.json | Server settings. |
permissions.json | Built-in permission settings. |
whitelist.json, bans.json | Join restrictions. |
mods/ | Installed extensions; check compatibility before upgrades. |
logs/ | Startup and runtime diagnostics. |
Stop the server before manual configuration edits. Otherwise a later write from the running server can replace the file you just edited. Keep a known-good copy before changing values. Use the command reference for supported runtime access-control commands.
Use the launcher for updates
The expected structure has Assets.zip and start.sh or start.bat above Server/. Run the generated launcher from that parent directory. update setup can create the embedded launchers when the running server is in Server/.
Use this sequence in the server console, checking the result after each command:
update status
update check
update downloadAfter staging completes, notify players and verify your backup. Then deliberately apply it:
update apply --confirmThe bundled launchers restart for the update exit code; they are not a general crash supervisor. The updater's WhenEmpty and Scheduled application modes are optional configuration, not a promise that an arbitrary copied installation will update itself. Check your build's help and current configuration before enabling automatic application.
After the restart
Read startup logs, check update status, join the world and verify saves, permissions and any mods you use. If an update fails, stop repeated restarts and inspect the logs and available backups before replacing files. Avoid a blind rollback over the only copy of your world.
The official manual documents the full update configuration and wrapper layout. This page's restore and post-update checks are recommendations; no live server update or recovery was performed to publish the article.