How to update a Hytale server and verify the new build

By Niko Catarino

Updated 5 October 2026

Before installing a new build, save a backup and check how your service applies updates. Afterward, confirm the reported build and test the world and mods before reopening to players. Stopping and starting the process alone won’t tell you whether an update was downloaded or installed.

Begin here after the server has completed its first start and you can open the Console tab. Otherwise, follow the Hytale Game Server Setup guide first.

Use the procedure for your hosting model: managed Hytale hosting in VXPanel or a VPS/dedicated machine you administer. The official Hytale Server Manual describes the game updater; a panel may use a different startup workflow.

Back Up Your World First

Do this before anything else

Stop the service and let it finish saving. Back up the world, mods and configuration before editing files, wait for completion, and download a copy to storage outside the server.

1. Open Backups from the left sidebar.
2. Select Create Backup.
3. Give it a name that identifies the change, such as “Before Update v1.0”, so you can locate it when needed.

Retain the backup and its old server-build identifier until you have joined the updated service and verified the world and mods. A restore can overwrite progress made since the backup. Preserve the current state before restoring.

Confirm the update method

Follow the update method supported for your managed VXPanel service. If you see power buttons alone or do not know whether startup installs updates, have VYKIX confirm the method before you edit the launcher or upload binaries.

Check update state through these console commands while Hytale is running:

/update status
/update check

Send an unsupported-command response or disabled-checker result to support so we can identify the update workflow. Don’t reinstall the world based only on either response.

Self-managed servers using the publisher’s updater

The publisher’s updater requires its launcher scripts and folder layout. Run the server from Server/, with Assets.zip and start.sh or start.bat one directory above. After verifying the layout and completing a backup, use that launcher and enter:

/update check
/update download

Allow the download to finish, then read /update status. Once the files are staged and players have disconnected, apply the update:

/update apply --confirm

On exit code 8, the publisher’s wrapper applies the staged files and launches the updated build. Without that wrapper, the process may stop before the update completes. Use the installation manual rather than substituting another host’s startup command in VXPanel.

Stop the server for manual file changes

1. Select the Console tab.
2. Use Stop at the top right.
3. Wait until the console confirms an offline server before editing files.

Stop lets the server finish writing its world to disk before shutdown. Reserve Kill for a process that no longer responds to other controls.

Start the Server and Watch the Console

Once the supported update workflow finishes, use Start if the process is stopped. Keep the Console tab open and compare its reported build with the intended version before inviting players.

• Continue to mod checks once the reported build matches the intended update.
• Follow the next section if startup pauses with a device code or URL.
• If a complete stop and start still reports the old build when you expected an update, send VYKIX a console screenshot on Discord using the instructions at the end of this page.

Verify the resulting build

Use the Hytale change record to save the previous build, intended build and build reported after startup. Inspect /update status; keep any unsupported-command or disabled-checker response.

If the reported build stays unchanged, check the wrapper and folder layout described above. For a managed instance, give VYKIX the old and intended build identifiers and the update output before changing its launcher.

Test authentication status, player joining and gameplay against the reported build. Keep the pre-update backup and current state while investigating a fault. Check mod compatibility even after the download finishes.

Re-Authenticate If the Server Asks

For an authentication error, begin with /auth status. Complete the active request if you receive a downloader or server-login prompt. Don’t assume your credentials expired just because the server was updated.

1. Take the current link or code from the console.
2. Log in to the Hytale account holding the game license.
3. Authorise the browser sign-in request and wait for the console to confirm success and continue startup.

Complete the request within the expiry shown. Start a fresh server-login request with /auth login device, then approve it at https://accounts.hytale.com/device. The setup guide separates file-download and server-login stages; a completed stage may not ask you to log in again.

Make Your Token Survive Restarts

Inspect the current store through /auth persistence. With Memory, credentials disappear when the process stops. After login, choose the supported encrypted store:

/auth persistence Encrypted

Verify the command result and resolve storage errors before depending on persistence. The publisher’s authentication guide treats storage and refresh as separate mechanisms. Encryption does not prevent revocation or refresh failure.

Check Your Mods and Scripts

Mods or scripts built for the previous Hytale version may break after an update. Before reopening the service:

1. Connect as a player and test the gameplay your community uses, including mods and custom scripts.
2. For a mod update, check supported server builds and dependencies. Stop the service before replacing files through Files or SFTP.
3. Start it, inspect mod-loading output and join again to verify the edit.

Verify compatibility between server and client builds. Test joins and mod gameplay even when the process starts successfully.

If the Update Breaks Something

1. Keep the error and both build identifiers. Stop the process and retain its current files before attempting recovery.
2. Check the pre-update backup’s contents against the intended build. If world formats changed or backup coverage is uncertain, ask VYKIX to review the rollback.
3. After confirming the restore, open Backups, select Restore in the backup’s … menu and test the recovered world before reopening.

Contact VYKIX on Discord with the error text and build identifiers. Before sharing screenshots, hide passwords, tokens, authentication codes and sign-in URLs that contain codes.