Launch sale20% off everything — celebrating the launch of GHosting!
← All guides

How to Update a Hytale Dedicated Server

Hytale has a built-in staged update system. The safe sequence is to check for a release, download it to staging, make sure backups are enabled, then apply it through the official launcher script. The launcher preserves config, worlds and mods while replacing the server binaries and assets.

A persistent block-built fantasy homestead beside a river at night Apply official Hytale updates from a managed panel without rebuilding your world

Why Hytale updates cannot wait indefinitely

Current Hytale clients and servers compare an exact protocol hash. When the client moves to a new protocol version, an older server rejects the connection even if its process and UDP listener still look healthy. Plan a short update window when a release lands and verify one real join afterward.

Keep the official folder layout

The self-updater expects the game directory to contain Assets.zip and start.sh, with HytaleServer.jar below Server. Start the process from the Server directory through the official launcher. If that layout is missing, the update checker disables itself.

If you copied the files manually and do not have the launcher scripts, a running server can extract them:

/update setup

Use /update download --force instead when you also want fresh server files, assets and wrapper scripts staged.

1. Check the installed version and update status

Start in the writable server console:

/update status
/update check

The first command shows the current version and cached update state. The second asks the official update service for a newer build on the configured patchline.

2. Download the release to staging

/update download

The download goes to updater/staging instead of changing the running files. Run /update status again and wait until it reports that the update is ready before announcing the restart.

3. Confirm the backup policy

The Update block in Server/config.json should keep RunBackupBeforeUpdate and BackupConfigBeforeUpdate enabled. The first protects server data when a backup directory is configured. The second protects config.json, permissions.json, bans.json and whitelist.json.

For an important world, also keep an off-host copy of Server/universe. An automatic backup on the same disk is useful for rollback, but it is not protection from a disk failure.

4. Apply the staged update

Ask players to disconnect, then run:

/update apply --confirm

The server creates its update backup, shuts down with exit code 8, and relies on start.sh or start.bat to apply the staged files and launch again. A service that starts HytaleServer.jar directly will stop at this point instead of completing the update loop.

5. Verify the new process

  • Run /update status and confirm the expected release is active.
  • Read the first startup errors, not only the last lines in the log.
  • Confirm the QUIC listener is back on the configured UDP port.
  • Join with a current client and inspect the correct world.
  • Check that permissions and the intended mods survived the restart.

Automatic update modes

The Update block supports three application modes. Disabled checks and stages without applying automatically. WhenEmpty waits until no players are online. Scheduled applies after its configured delay even when players remain connected. WhenEmpty is the safer unattended choice for a community world.

If the new build does not start

Do not delete the universe. The official launcher keeps the previous update files under updater/backup and prints rollback guidance when a freshly updated process crashes. Preserve the failed state and its log, restore from that update backup, then check Java 25, the server and Assets.zip versions, and newly incompatible mods before trying again.

Managed Hytale updates

GHosting Hytale servers compare the installed build with Hytale's official release metadata and stage a clean managed refresh from the panel. Worlds, config, mods and backups stay in place, and lifecycle update commands are protected from the console so they cannot fight the managed process.

The command sequence, folder layout and update modes come from Hypixel Studios' official Hytale Server Manual.

More Hytale server guides