How to use the generator
Change a setting and the file updates as you go. Changed settings get a bright line and their own undo button, so you always know what differs from the default.
Already have a config.json? Load it with “Load my file”. Everything this page does not edit, like mods, log levels and connection timeouts, stays in the file exactly as it was.
Stop the server, copy or download the file, and put it next to HytaleServer.jar. The server reads it when it starts.
The settings that matter most
MaxPlayers caps how many people can be online. MaxViewRadius is the view distance in chunks of 32 blocks; keeping it at 12 or below saves a lot of memory.
Defaults sets the world new players land in and their game mode. Hardcore gives each player a number of lives, or one shared pool for the whole server.
RequireJoinPermission turns the whitelist on. Only players you add with /whitelist add can join.
Updates and backups
The server checks for updates every hour. AutoApplyMode decides when a downloaded update goes in: WhenEmpty waits until nobody is online, and Scheduled warns players and applies it after a delay.
An update shuts the server down with exit code 8. Only Hytale’s start.sh and start.bat scripts restart it and apply the files, so use them if you turn on auto updates.
Backups need a folder. Hytale’s scripts already pass --backup-dir backups, so with them a backup runs every 30 minutes.
The start command, explained
-Xmx sets the most memory Java may use. -Xms claims that memory right away, which can smooth out lag spikes on a machine that only runs the server.
-XX:AOTCache=HytaleServer.aot uses the ahead-of-time cache that ships with the server, so it boots faster. --assets points at Assets.zip, and --bind sets the address and UDP port.