Set up a Hytale server

A dedicated server runs independently of your game client. For a short session with friends, opening a singleplayer world may be enough. This guide was checked on 15 October 2026 against the official support articles and the installed 0.7.2 release files.

Just playing with friends?

Add each other as Hytale friends first. In your world, open ESC → Online Play, enable Allow Other Players to Join, optionally set a password, then save. Your friend uses Servers → Join via Code and enters your code. Share codes reveal network addresses and can contain the password: send them privately. Use Copy Network Report when troubleshooting, and follow the connection result shown by the game before changing router settings.

Prepare a dedicated installation

The official minimum is Java 25 and 4 GB memory, on x64 or arm64. This is a starting requirement, not a player-capacity guarantee. Check Java in the terminal you will use:

java --version

Use a separate server directory. To copy an existing Windows installation, open %appdata%\Hytale\install\release\package\game\latest and copy Server/ and Assets.zip together. Keep the two from the same release. For the authenticated downloader and other operating systems, follow the official Server Manual.

Start and authenticate

For the copied layout, open a terminal inside the copied Server directory. The assets are one directory above it:

java -jar HytaleServer.jar --assets ../Assets.zip --backup --backup-dir backups --backup-frequency 30

This command intentionally uses paths matching that layout. A missing JAR or assets error usually means the working directory or path differs. To inspect the installed build's flags without starting a world, run java -jar HytaleServer.jar --help.

In the running server console, authenticate:

auth login device

Open the official device-authorization link printed by your own server and complete the account login. Then check auth status. The inspected release registers the Encrypted credential store. Select it with auth persistence Encrypted, inspect the result with auth persistence, and verify auth status again after a restart. Keep generated credential and key files private.

Install the normal launcher

With the server running from Server/, enter:

update setup
stop

Wait for shutdown. From the parent directory containing Assets.zip, use the generated launcher:

The bundled launcher starts inside Server/, supplies the parent assets path and enables periodic backups. It also handles the update restart exit code. See Backups and updates before your first upgrade.

Make the connection reachable

The default dedicated port is 5520/UDP. Hytale uses QUIC over UDP. Allow that UDP port in the host firewall; if hosting behind a router, forward it to the server machine. A TCP-only rule does not serve this connection.

For another port, the direct Java command accepts --bind 5521; use that same UDP port consistently in firewall, router and client address. A connection from outside your home is the useful acceptance test for a router forward.

Join through the game's server interface using your server address and port. If joining fails, check the process, auth status, Server/logs/, the selected port and network rules. Do not turn off authenticated mode as a shortcut for a network error.

Add administrators and limit joining

Use the dedicated console to grant the first trusted administrator access with op add <player-uuid>. The command reference explains OP, player context and whitelist commands. Add your intended players before enabling the whitelist.

Confirm a successful join, then shut down and restart through the launcher. Check that the world and settings remain available and that backups complete. These are your installation checks; this article does not claim that every router or hosting panel behaves identically.