How to Configure Your Hytale Server

Understanding How Configuration Works

Hytale uses two main configuration layers:

1. The Settings tab in your panel – quick access to the most important options.
2. The config.json files – full configuration for the server and each world.

Panel settings always override the values in the main config.json when the server starts. If something doesn’t seem to stick, it’s because the panel setting is taking priority.

Panel Settings → What They Modify in config.json

The Settings tab exposes several common options. These directly update fields in your server’s main config.json.

Examples:

• Server Name → "ServerName"
• Message of the Day → "MOTD"
• Password → "Password"
• Max Players → "MaxPlayers"
• Max View Radius → "MaxViewRadius"

When you change a value in the panel:

• It overwrites the value inside config.json during startup.
• You do not need to edit these fields manually.

If you edit config.json instead of using the panel, the panel will still override those values.

Selecting Which World Loads

Your Hytale server loads a specific world based on the World field inside the main config.json:

"World": "default",

If you upload your own world with a different name, simply replace default with your world folder’s name.

Example:

"World": "Hytale",

This tells the server to load the Hytale world folder inside /universe/worlds/.

If the name doesn’t match, the server will create a new empty world instead—so double-check spelling.

Configuring World-Specific Settings

Each world also has its own configuration file:

/universe/worlds/<worldname>/config.json

This file controls gameplay behavior inside that world, such as:

• Fall damage
• PvP
• Time progression
• Environment settings
• Ticking and simulation rules

Examples:

To disable fall damage:

"IsFallDamageEnabled": false,

To enable or disable PvP:

"IsPvpEnabled": true,

These settings only apply to the selected world. Editing them does not affect other worlds.

What You Don’t Need to Touch

Hytale includes many technical config fields meant for internal systems, development tools, and engine behavior. In normal use, you do not need to change:

• Mods
• RateLimit
• ConnectionTimeouts
• ChunkConfig
• ClientEffects
• Engine/config flags

Changing these incorrectly can break world loading or cause server instability.

Stick to the panel settings and world toggles unless you know what you're doing.

Summary

• Use the Settings tab for common options — these override config.json.
• Update the World field in config.json to load a custom world.
• Modify the world-level config.json to change gameplay behaviors.
• Most advanced settings should be left alone unless necessary.