How to Update Your Hytale Server

Back up the server before updating, confirm how your service installs the new build, then test the world and mods before players return. A stop and start alone does not prove that an update was downloaded or applied.

This page assumes your server has started at least once and you know your way to the Console tab. If not, start with the Hytale Game Server Setup guide.

The instructions below distinguish managed Hytale hosting in VXPanel from a self-managed VPS or dedicated server. The official Hytale Server Manual documents the game’s updater; a hosting panel’s startup process can differ.

Back Up Your World First

Do this before anything else

Stop the server so it can finish saving, then back up the world, configuration and mods before changing files. Wait for the backup to complete and keep a downloaded copy outside the server.

1. Click the Backups tab in the left sidebar.
2. Click Create Backup.
3. Name it after the moment, e.g. “Before Update v1.0”, so you can find it later without guessing.

Keep this backup until you have joined the updated server and checked your world and mods. Record the old server build with it. Restoring a backup can remove progress made after it was created, so preserve the current state before a restore.

Confirm the update method

On managed hosting, use the update procedure provided for your VXPanel service. If you only see power controls or do not know whether your startup process installs updates, ask VYKIX to confirm the method before changing the launcher or uploading server binaries.

While the server is running, these Hytale console commands can report its update state:

/update status
/update check

An unsupported command or disabled update checker is useful information for support. It does not mean your world needs to be reinstalled.

Self-managed servers using the publisher’s updater

The built-in updater needs the publisher’s folder layout and launcher scripts. The server runs from Server/, with Assets.zip and start.sh or start.bat in the parent folder. After confirming that layout and completing your backup, start the server through the supplied launcher and run:

/update check
/update download

Wait for the download to finish and check /update status. When the update is staged and players have left, apply it:

/update apply --confirm

The server exits with code 8; the publisher’s wrapper applies the staged files and starts the new build. A process launched without that wrapper may stop without completing the update. Follow the manual for your installation rather than copying a different host’s startup command into VXPanel.

Stop the server for manual file changes

1. Open the Console tab.
2. Click Stop in the top right.
3. Wait for the console to show the server is offline before you change anything.

Use Stop, not Kill. Stop gives the server time to finish writing world data to disk before it shuts down; Kill is for a server that no longer responds to anything else.

Start the Server and Watch the Console

After the supported update procedure completes, click Start if the server is stopped and keep the Console tab open. Read the reported build and compare it with the intended update before inviting players back.

• If the reported build matches the intended update, continue to checking your mods.
• If startup pauses and prints a URL or a device code, continue with the next section.
• If you expected a new version and the console still reports the old build after a complete stop and start, ask VYKIX on Discord and include a screenshot of the console; see the last section on this page.

Re-Authenticate If the Server Asks

Run /auth status if the console reports an authentication problem. If a file-download or server-login prompt appears, complete the active request. An update alone does not establish that your credentials have expired.

1. Copy the link or code from the console.
2. Sign in with the Hytale account that owns the game license.
3. Approve the sign-in request in your browser. The console confirms success and startup continues.

Use the expiry shown in the prompt. For a new server-login request, run /auth login device and complete it at https://accounts.hytale.com/device. The setup guide shows the file-download and server-login stages; a service that has completed one stage may not ask for it again.

Make Your Token Survive Restarts

Check the active credential store with /auth persistence. If it reports Memory, the process loses those credentials when it stops. After authentication, switch to the supported encrypted store:

/auth persistence Encrypted

Check the command’s result. A storage error needs attention before relying on persistence. The publisher’s authentication guide distinguishes credential storage from token refresh; encrypted storage does not prevent revocation or a failed refresh.

Check Your Mods and Scripts

A game update can break mods or custom scripts that were written against the previous build. Before you tell your players the server is back:

1. Join the server yourself and test the things your community uses; custom scripts, mods, anything that touches gameplay.
2. If a mod needs a new version, confirm its supported server build and dependencies. Stop the server before replacing files through Files or SFTP.
3. Start the server, read the mod-loading messages, and join again to test the change.

Check that the client and server use compatible builds. A successful startup does not confirm that each mod or player connection works.

If the Update Breaks Something

1. Save the error and the old and new build identifiers. Stop the server and preserve its current files before attempting a restore.
2. Confirm which files the pre-update backup contains and whether they match the intended server build. Ask VYKIX to check the rollback if the update changed the world format or you are unsure what the backup covers.
3. Once the restore is confirmed, open the Backups tab, use Restore from the backup’s … menu, and test the restored world before reopening it to players.

Ask VYKIX on Discord with the build identifiers and error text. Remove passwords, authentication codes, tokens and sign-in URLs containing codes from screenshots.