Getting Started with a Hytale Server
Choose a hosting approach, install Java 25 and the Hytale server files, authenticate, open the UDP port, and protect the first world.
Last updated: 2026-08-01
Start with a small private server, confirm that it works on the local network, and add public access, mods, and automation only after the basic installation is stable.
1. Choose where it will run
Use a PC you control when you want direct access and do not mind maintaining Java, updates, networking, and backups. Use a VPS, dedicated machine, or managed game host when the server must remain online independently of a home PC.
The official baseline is Java 25, at least 4 GB of memory, and an x64 or arm64 system. Actual CPU and memory use depends heavily on players, entities, independently loaded world areas, mods, and view distance.
2. Obtain the server files
The official server manual documents three supported paths:
- Copy
Server/andAssets.zipfrom a Hytale Launcher installation for quick testing. - Use the Hytale Downloader CLI for a production installation that is easier to update.
- Bootstrap an empty installation from
HytaleServer.jar.
Follow the dedicated-server setup guide for the commands and resulting directory layout.
3. Authenticate and test locally
Start the server and use /auth login device in its console. Complete the device flow through the official Hytale account page. Treat device codes and generated authentication files as secrets.
Connect from the host or local network before opening the router. This separates installation and configuration problems from public-network problems.
4. Open only the required network path
Hytale uses QUIC over UDP. The default bind port is 5520, so a default public setup needs UDP 5520 allowed through the host firewall and forwarded to the server's stable local address. TCP forwarding is not required for the default game connection.
If the ISP uses carrier-grade NAT or the router cannot accept inbound traffic, use a public server host or ask the ISP about a public address rather than disabling the firewall or placing the machine in a DMZ.
5. Protect the first world
The universe/ directory contains world and player save data. Enable automatic backups, keep a separate off-machine copy, and test restoration before installing experimental plugins.
Also preserve config.json, permissions.json, whitelist.json, bans.json, the mods/ directory, and authentication files in a restricted backup. Never publish authentication files with a support request.
Recommended first milestones
| Milestone | Why it matters |
|---|---|
| Local connection works | Confirms Java, files, authentication, and the server process |
| External connection works | Confirms UDP firewall, forwarding, and public reachability |
| Automatic backup enabled | Limits damage from crashes, updates, or operator mistakes |
| Update workflow tested | Reduces client/server version mismatches |
| Permissions and whitelist reviewed | Prevents relying on defaults for access control |
| Baseline performance recorded | Makes later mod or configuration regressions easier to identify |
Continue with server troubleshooting and backups and migration.