Zombie
Minimum memory for Hytale
- 4096 MB RAM
- 2 CPU threads
- 25 GB NVMe storage
€5.95p/m
Cancel monthly
OrderThree knobs decide almost everything: view distance, player count and the mods you run. The rest is measuring.
Start with MaxViewRadius in config.json. In the server manual Hypixel Studios recommends at most 12 chunks (384 blocks), and view distance is what eats the most memory on a Hytale server. If memory fills up, go down in steps.
Set MaxPlayers to what you actually expect, remove the mods nobody uses and update the server as soon as Hytale ships an update. Still stuttering? Check whether the CPU or the memory is full before you buy anything.
In this order. Every step can be checked in the console or in your panel's statistics.
The setting lives in config.json next to HytaleServer.jar. The manual recommends at most 12 chunks; since Update 7 the server accepts values from 1 to 32. If memory fills up, go down in steps of two. Seeing twice as far means four times as many chunks.
A limit of 100 on a server for eight friends costs nothing as long as nobody shows up, but on a public server it sets your peak load. Pick what the memory can carry; the RAM guideline is on the requirements page.
The server reads config.json at startup and writes the file back itself. According to the manual, changes made while it runs are likely to be overwritten. Stop the server, edit the file and start it again.
Mods run server-side and load at start, even if nobody uses them. Remove what you do not need and test after a Hytale update whether everything still works before letting players in.
Client and server must run the exact same protocol version; a newer client cannot join an old server. Update the server as soon as an update is out. Update 7 converted existing worlds the first time they loaded, so make a backup first.
CPU full while memory is free? Then only less view distance, fewer creatures or fewer mods will help. Memory full? Then a bigger plan is the answer. A memory shortage often shows up first as high CPU load, because Java keeps cleaning up memory.
Why view distance weighs so heavily and why more memory does not give you a faster server.
Decides how many chunks around each player are loaded and generated. According to the manual the biggest factor in memory use. Twice as far is four times as many chunks. This is the setting to lower first when lag hits.
Every player loads their own piece of world. Ten players exploring in different directions need more memory than ten players building together.
Server-side, so memory and CPU time on the server. Plugins that do work every tick weigh more than an asset pack with new blocks.
The manual names the number of players and entities (NPCs and mobs) as the biggest CPU load. Each world runs on its own main thread, so one fast core helps more than many cores. Our Hytale servers run on AMD Ryzen and EPYC.
World generation and chunk loading are disk work. On NVMe a player who explores fast waits less for new chunks.
Decides how much world fits in memory at once. Full memory gives stutter and eventually a crash; free memory makes nothing faster.
If memory is not full, a bigger plan changes nothing about a tick that takes too long.
Hytale uses UDP 5520 (QUIC). A TCP rule does nothing for reachability or speed.
The server keeps sending world data to every player who explores. Wi-Fi and a power-saving laptop CPU give lag that no setting fixes.
At delivery Java 25 is ready, UDP 5520 is open and you manage config.json through the Pterodactyl panel's file manager or SFTP. The panel statistics show CPU and memory separately, so measuring is one glance.
From 4 to 10 GB. Unsure about the size? The RAM guideline is on the requirements page.
Minimum memory for Hytale
€5.95p/m
Cancel monthly
Order€8.95p/m
Cancel monthly
Order€11.95p/m
Cancel monthly
Order€14.95p/m
Cancel monthly
OrderUnsure about memory? The RAM guideline per player count is on the requirements page. Players cannot get on? See fixing connection problems.
The official Hypixel Studios documentation and patch notes this page is based on.