Know the Hytale server requirements
The current official Hytale server manual requires Java 25 and documents a 4 GB minimum. Runic recommends more headroom for a normal persistent world because loaded world area, view distance, players, entities and plugins can increase resource use.
Hytale client/server traffic uses QUIC over UDP. Runic manages the production allocation and firewall path, so customers should use the assigned address instead of opening or changing arbitrary ports.
Authentication on a hosted service
Hytale requires authenticated dedicated servers. For a commercial hosting provider, Runic’s production workflow must use Hypixel Studios’ documented Server Provider Authentication flow so provider refresh credentials and per-server session/identity tokens remain server-side and can be rotated correctly.
Customers should not be asked to paste device codes, refresh tokens, session tokens or identity tokens into public tickets, screenshots, startup fields or browser-visible configuration.
Configuration, permissions and access control
Hytale keeps server configuration in config.json, permission data in permissions.json and world/player data under the universe directory. Manual file changes should be made while the server is stopped because the running server can rewrite configuration.
As of Hytale Update 6, whitelist access is permission-based through hytale.server.join, and legacy whitelist.json data is migrated. Use the current supported whitelist/permission commands and Runic’s validated panel workflow rather than treating manual edits to a legacy whitelist file as the long-term source of truth.
Updates, plugins and world safety
The current Hytale server manual warns that client and server protocol versions must match exactly until protocol-tolerance support ships. Runic should validate the running server release before an update is exposed to customers.
Install only plugins or mods compatible with the current server release and the validated Runic workflow. Keep a recovery point for the universe and configuration before a significant server update, plugin change or world-level configuration change.