Hytale Known Issues, Workarounds and Fixes

Server save data and configuration are separate files

The manual identifies universe/ as world and player save data, while config.json and permissions.json are configuration files. A live configuration edit can be overwritten by the running server. This is a documented persistence rule, not evidence that every unexpected setting comes from a lost world save. [1]

The bootstrap installer shuts down after installing

The JAR bootstrap process downloads and extracts the installed payload and then shuts itself down. That exit is part of the documented installation procedure, so it is not by itself evidence of a crash. The installed launcher script starts the actual server afterward. [1]

Documented steps

1. After the bootstrap installation completes, start the installed host with start.bat on Windows or ./start.sh on Unix. Its authentication credentials carry over from the installer. [1]

Rising server CPU usage may reflect memory pressure

The server manual describes increased CPU usage from garbage collection as a typical symptom of memory pressure. More entities or players also raise CPU demand, and loaded world area affects memory use. Those different load factors mean high CPU alone does not prove a single cause. Monitor actual usage before treating a Java heap change as a verified repair. [1]

Documented steps

1. Monitor RAM and CPU during the player count and play style you intend to host. The manual recommends doing this to understand normal consumption for that workload. [1]

Server starts but is not authenticated

After first launch the server needs device authentication before it can accept player connections. [1]

Documented steps

1. Enter /auth login device in the server console and complete the authorization using the displayed Hytale accounts address. [1]

Live edits to configuration files get overwritten

The server reads configuration files at startup and writes changes from in-game actions. Manual changes while running can be overwritten, so coordinate settings changes with the server lifecycle. [1]

TCP-only forwarding does not match Hytale networking

The documented server transport is QUIC over UDP. The default port is 5520; the guide specifically says TCP forwarding is not required. Diagnose a wrong-protocol rule without turning off the firewall. [1]

Documented steps

1. If you control a router hosting the server, check that the relevant forward is UDP 5520 or the custom port you selected. [1]

Client/server protocol mismatch rejects connections

Hytale’s server manual says client and server must use the exact same protocol version. It describes a hash check that rejects mismatches. The proposed tolerance is listed as Coming Soon, so do not assume it is available. [1]

Documented steps

1. Update the server when clients move to a new protocol version. [1]