Hytale Server Config Generator
Build both config files a Hytale dedicated server needs — the server config.json (name, password, player cap, view radius, default game mode) and a world config.json (PvP, NPCs, world generation, day/night, visuals) — from toggles and dropdowns, then copy or download. Every key and default is taken from the real shipped config files, not guessed.
config.json files & the server docs · values that disagree between docs/stock or vary by build flagged ⚠ verify · we track patches and re-verify
Server identity
The server's name, access and basics — the root config.json in your server folder.
The name shown in the server browser.
Greeting message players see on join. Blank for none.
Players must enter this to join. Blank = open server.
Concurrent player cap. Keep it within your CPU/RAM — more players need more memory.
Render/sim distance in chunks (1–64). 12 is a safe default; higher hits performance hard. (Docs and the stock file disagree between 12 and 32 — 12 is the safer pick.)
Game mode new players spawn in.
Which world new players load into. Matches a folder under universe/worlds/.
World gameplay
Per-world rules — the config.json inside universe/worlds/
Allow player-vs-player combat in this world.
Players take damage from falls. Turn off for build/creative worlds.
Override the server's default mode for this world. Leave on inherit to use the server default.
Which gameplay ruleset this world uses. 'Default' unless you've defined a custom one.
Whether NPCs (creatures/mobs) spawn in this world.
Whether spawn markers are active in this world.
Show objective markers in the world.
Whether the compass tracks/updates in this world.
World generation & time
How the world is generated and how its day/night runs.
Generation seed. Leave blank for a random seed on first generation.
Which generator builds the world. Flat/Void are for creative or minigame worlds.
Named generator config (Hytale generator only).
Freeze the day/night clock (eternal noon, etc.).
Override how long daytime lasts, in seconds. Blank = game default.
Override how long nighttime lasts, in seconds. Blank = game default.
Force a single weather type. Blank = normal dynamic weather. (Exact weather strings vary by build — verify in-game.)
Freeze every NPC in place. Niche — handy for screenshots or builds.
Advanced — networking & storage
Server-side performance, anti-flood and storage. Sensible defaults — only touch with a reason.
Network compression for LAN play. Usually left off.
Debug/dev display of temporary tags in strings. Leave off.
Where player data is stored. Disk keeps it in local files.
Flood protection. Keep on unless debugging.
Max packets per second per client before rate-limiting kicks in.
Allowed short burst above the per-second limit.
How the server's auth credentials are stored.
Connection timeout, ISO-8601 duration (PT10S = 10s, PT1M = 1 min).
Authentication timeout (ISO-8601 duration).
Play-session timeout (ISO-8601 duration).
Advanced — persistence & ticking
What the world saves and simulates. Defaults are right for almost everyone.
Whether chunks in this world simulate (tick) at all.
Whether blocks tick (growth, fluids, etc.).
Persist player data for this world.
Persist chunk changes to disk.
Mark newly generated chunks for saving.
Allow distant chunks to unload from memory.
DESTRUCTIVE — wipe and regenerate this world every server start. For rotating minigame worlds.
Delete the world's files when it's removed from the server.
Advanced — client visuals
Per-world sky and post-processing the server pushes to clients. Purely cosmetic — tune the mood.
Sun height as a percentage.
Sun angle in degrees.
Sunlight intensity.
Bloom post-processing intensity.
Bloom post-processing power.
God-ray (sunshaft) intensity.
God-ray scale factor.
About the Hytale Server Config Generator
A Hytale dedicated server is configured by JSON: a server-wide config.json in the server root, and a separate config.json for each world under universe/worlds/. The server file sets the name, password, player cap, view radius and the default game mode; the world file sets PvP, NPC spawning, world generation, the day/night clock and the client visuals. This tool builds both as complete, valid JSON — every key and default pulled from the real shipped config files (server v3, world v4), with the handful of values that disagree between the docs and the stock file flagged ⚠ verify.
Two files come out of this tool: the server config.json (root of your server folder) and a world config.json (in universe/worlds/). Each is a complete, ready-to-use file — paste over the matching default.
Keys, defaults and enums are from the real shipped config files (server v3, world v4). Hytale is in Early Access, so a couple of values that disagree between the docs and the stock file (or whose exact strings vary by build) carry a ⚠ verify flag.
Stop the server before editing config files — Hytale reads them on startup and may overwrite them if you edit while it's running. Restart to apply.
Running a Hytale server needs Java 25 and a free UDP port (default 5520). It also needs an account that owns the game, authenticated once via the Hytale Downloader — that part isn't a config setting, it's account linking.
Installing the server (Java 25 + account auth)
The Hytale dedicated server is a Java app — you need Java 25 (Adoptium/Temurin), at least 4 GB of RAM, and a free UDP port (default 5520; Hytale uses QUIC over UDP, so forward UDP, not TCP). Get the server files via the free Hytale Downloader, then authenticate once — the server has to be linked to an account that owns the game (open the URL it prints and enter the code). A typical launch line:
java -Xms4G -Xmx8G -XX:AOTCache=HytaleServer.aot -jar HytaleServer.jar --assets PathToAssets.zip
Scale memory to your player count (-Xmx 4 GB for a handful, 8 GB for ~10–20, 12 GB+ beyond). Drop the config.json from this tool in the server root, the world file under universe/worlds/<world>/, and start it.
Server won't start or won't connect?
- Won't start: it's almost always Java — Hytale needs Java 25 and refuses to run on 21 or older. Check
java -version. - Can't connect: forward UDP 5520 (not TCP) to the server machine, and make sure the server finished its one-time account authentication.
- Edits don't stick: Hytale reads config on startup and can overwrite it if you edit while running. Stop the server first, paste the file, then restart.
FAQ
Where do these files go?
The server config.json goes in the root of your Hytale server folder (next to HytaleServer.jar). The world config.json goes in universe/worlds/. Stop the server, replace the file, restart.
What's the difference between the two files?
The server config.json controls the whole server (name, password, max players, view radius, default mode). The world config.json controls one world (PvP, NPCs, generation, time, visuals). A server can host multiple worlds, each with its own world config.
Do I need to set a seed?
No — leave Seed blank and the world generates a random seed on first creation. Set one only if you want a specific, repeatable world.
Why is a value marked ⚠ verify?
Hytale is in Early Access. A few values disagree between the official docs and the stock config file (view radius), or are free-text whose exact strings depend on your build (forced weather, timeouts). We flag those so you double-check them against your own config.json.
Does this set up the server for me?
It builds the config files. You still need the Hytale server itself: Java 25, the server files via the Hytale Downloader, account authentication (the server must be linked to an account that owns the game), and UDP port 5520 forwarded. The config is the part this tool nails.
Related tools
- All GamesOMG server config generators
- Minecraft villager trades — for the other big block-builder.
- Valheim Server Config Generator — another co-op survival server.
Hytale is in Early Access, so config keys and defaults will move. We re-verify against the real config files and the server docs when they do. Spot a value that's drifted or a key we should add? Hit Report an issue above.