How to Update a Hytale Server Without Losing Your World or Mods

Before updating: back up your world and settings

Pause new connections and tell your players when the server will restart. Download an off-server copy of universe/ (worlds and player data), mods/, config.json and, if used, permissions.json and whitelist.json. Check that the archive includes universe/worlds/. A backup stored only on the same machine will not help if that machine fails.

The official configuration enables RunBackupBeforeUpdate by default, but that backup requires a configured backup directory. Verify where it is written and keep your independent copy.

Use Hytale's built-in update commands

Run these commands in the server console, in order:

/update status
/update check
/update download
/update apply --confirm

The final command performs the configured pre-update backup, then exits with code 8. The official start.sh and start.bat wrappers detect that code, apply the staged game files and assets, and restart the server. This selective replacement normally preserves configuration, saves and mods/. If you launch the JAR directly, that wrapper-managed apply and restart will not happen in the same way. A hosting panel may handle the process for you: confirm that its update button keeps your data and restarts the server.

By default, AutoApplyMode is Disabled: the server checks for updates automatically but does not apply them automatically. After restart, run /update status again and test with an updated Hytale client. The current protocol requires an exact client-server version match.

If the server will not start or a mod fails

1. Read the latest entries in logs/ to separate a game-version issue from a mod or world-loading error. Exit code 8 is the expected update signal, not proof of a crash.
2. Check that the server uses the official wrapper or your host's supported update workflow. If needed, /update setup writes the official wrappers when the server is running from a Server/ directory.
3. If the logs point to a mod, stop the server, keep a copy of mods/, and update that mod. To isolate a conflict, temporarily remove the affected mods and test on a copy of the world. Do not remove a mod from a live world without understanding the data it owns.
4. If startup fails immediately after updating, inspect updater/backup/ and the independent copy you made. Restore a consistent set of files from the same version; restoring only the world alongside mismatched server files or mods can hide the cause.

Hytale mods are .zip or .jar files in mods/. A new game release does not guarantee compatibility with every mod, so check each author's supported version before reopening the live world.

When should you compare Hytale hosts?

If logs and monitoring point to an actual resource limit during play, inspect CPU and memory use under load before upgrading. Hytale's manual says player and entity counts mainly drive CPU use, while view distance and loaded world area affect RAM. For a move to another host, ask how to export universe/, mods/ and the configuration, and how updates are applied.

See the Hytale server comparison for available plans and the Hytale server cost guide for budget details. Check update and backup support before choosing on price alone.

Frequently asked questions

Will an update delete my world? The official wrapper selectively replaces game files and preserves saves, settings and mods. Still download a separate backup before any major update.

Why can players no longer join? First check versions with /update status: Hytale currently requires an exact protocol match between client and server. Then check logs for a mod or connection error.

Can I update while players are online? Applying an update shuts down and restarts the server. Warn players and schedule a quiet time. You can set AutoApplyMode to WhenEmpty to apply a staged update once no players remain.