Hytale: getting started, joining, mods and performance

Besides console, files, backups, schedules and SFTP, your Hytale server has three tabs of its own: Server for the settings, Mods and Players.

Getting started

1. 1

   Start

   GoodFlare downloads the game files (about 1.7 GB, 4 GB on the server) straight from Hytale during the install and checks them. Then press Start on the overview.

2. 2

   Sign-in

   A Hytale server has to be signed in with Hytale before players can join. GoodFlare does this for you at every start: you do not need /auth login in the console.

3. 3

   Set up

   After the first start Hytale creates config.json. Under Server you then set the name, password, player slots and view distance.

Joining

Hytale connects over UDP (QUIC), not TCP. Your friends add the address with its port in Hytale's server list, exactly as the overview shows it, for example 203.0.113.10:5520 or your server name with the port. The port always belongs to it: Hytale does not support SRV records yet, which could replace it.

Client and server need exactly the same version. At every start you trigger (button, schedule, API), GoodFlare checks whether your channel has a new version and applies it before the start; after a Hytale update a restart is enough. When our system restarts the server by itself after a crash, it keeps running the installed version.

Settings

• Server name, message of the day, password and player slots are in Server/config.json. The form changes only what you change; everything else in the file stays.
• Hytale writes the file itself while the server runs. When it is running, the button therefore says Stop, save, start.
• Update channel: release is the published version, pre-release gets new things earlier and may have bugs. The channel applies to updates and to a reinstall.
• Everything else you edit under Files, for example permissions.json, whitelist.json and bans.json in the Server folder.

Mods

Mods are .jar or .zip files in the Server/mods folder. In the Mods tab you upload them (for example from CurseForge), switch them off and on again or delete them; deleted files stay in the recycle bin for seven days. Changes take effect at the next start.

We add the plugin hytale-sourcequery.jar ourselves: through it the portal reads the player count and the player list. Switch it off and both are gone.

Players

The Players tab shows who is playing right now and for how long, refreshed every 20 seconds. Permissions, bans and the whitelist are managed with Hytale's commands in the console.

Performance

What needs the most memory is the view distance: the server keeps everything within that distance of every player loaded. Hytale recommends at most 12 chunks (384 blocks), so the Server tab offers 4 to 12. Players who spread out far from each other need more memory than a group in one place.

2 to 4 players

4 to 6 GB

5 to 8 players

6 to 8 GB

10 to 16 players

10 to 16 GB

These are rules of thumb, not limits. Under Performance you see how much memory and processor the server really uses; if it is not enough, move to a larger package under Change plan. Many creatures and players mostly load the processor.