Start with MaxViewRadius in config.json. The default of 12 chunks is right for most servers; on 4 GB set it to 8 to 10, on 10 GB you can go to 16.

Set MaxPlayers to what you actually expect, remove the mods nobody uses and restart the server after every Hytale update. Still stuttering? Check whether the CPU or the memory is full before you buy anything.

Step by step

How to set up a Hytale server properly

In this order. Every step can be checked in the console or in your panel's statistics.

  1. 01

    Match MaxViewRadius to your memory

    In config.json next to HytaleServer.jar. Default 12. Guideline: 8 to 10 on 4 GB, 10 to 12 on 6 GB, 12 to 16 on 8 GB, 16 to 20 on 10 GB. Every extra chunk costs quadratically more.

  2. 02

    Make MaxPlayers honest

    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 (see the RAM table).

  3. 03

    Clean up your mods

    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.

  4. 04

    Restart after every update

    Hytale ships an update every two to six weeks and the protocol changes with it. Update the server, restart, and only then let players on. A daily restart at a quiet hour keeps memory clean.

  5. 05

    Measure before you buy

    One CPU core at 100% while memory is free? Then only less view distance, fewer entities or fewer mods will help. Memory full? Then a bigger plan is the answer.

  6. 06

    Put the server near your players

    Latency is not a setting but a location. If your friends play from the Netherlands and Belgium, a Dutch server shows in the responsiveness right away.

What each knob does

Why view distance weighs so heavily and why more memory does not give you a faster server.

MaxViewRadius

Decides how many chunks around each player are loaded and generated. Twice as far is four times as many chunks. This is the setting to lower first when lag hits.

MaxPlayers

Every player loads their own circle of chunks. Ten players far apart load the server more than ten players building together.

Mods and plugins

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 CPU

Hytale does its heaviest work on one thread. A high clock speed counts more than many cores. That is why we run on AMD Ryzen.

Storage

World generation and chunk loading are disk work. NVMe makes a visible difference for players who explore fast.

Memory

Decides how much world fits in memory at once. Full memory gives stutter and eventually a crash; free memory makes nothing faster.

What does not help

01

More RAM against CPU lag

If memory is not full, a bigger plan changes nothing about a tick that takes too long.

02

Opening a TCP port

Hytale uses UDP 5520 (QUIC). A TCP rule does nothing for reachability or speed.

03

Hosting from a laptop on Wi-Fi

Exploring players pull a few megabits per second each. Wi-Fi and a power-saving CPU give lag that no setting fixes.

How our servers are set up

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 step five is one glance.

See the Hytale plans
  • AMD Ryzen with a high clock speed, two cores per server
  • NVMe storage for world generation without waiting
  • config.json and the mods folder editable right in the panel
  • Console and logs live in the panel
  • Hosted in the Netherlands on our own network

Plans

From 4 to 10 GB. Unsure about the size? The RAM guideline is on the requirements page.

Hytale - 4GB

€9.50 /mo

Or €114.00 €100.00 /yr Save 12% · 1 month free

hytale-4gb
Order now
  • 4GB RAM
  • From 25GB NVMe SSD
  • AMD Ryzen/EPYC processors
  • 5-10 players recommended
Most popular

Hytale - 6GB

€14.00 /mo

Or €168.00 €160.00 /yr Save 5% · 1 month free

hytale-6gb
Order now
  • 6GB RAM
  • From 25GB NVMe SSD
  • AMD Ryzen/EPYC processors
  • 10-20 players recommended

Hytale - 8GB

€18.00 /mo

Or €216.00 €200.00 /yr Save 7% · 1 month free

hytale-8gb
Order now
  • 8GB RAM
  • From 25GB NVMe SSD
  • AMD Ryzen/EPYC processors
  • 15-30 players recommended

Hytale - 10GB

€24.00 /mo

Or €288.00 €250.00 /yr Save 13% · 2 months free

hytale-10gb
Order now
  • 10GB RAM
  • From 25GB NVMe SSD
  • AMD Ryzen/EPYC processors
  • 20-40 players recommended

Unsure about memory? The RAM guideline per player count is on the requirements page. Players cannot get on? See fixing connection problems.

FAQ

Frequently asked questions about Hytale settings

Stuck? Send us a message or ask in our Discord.

The default of 12 chunks for most servers. On 4 GB set MaxViewRadius to 8 to 10, on 10 GB you can go to 16 to 20. Higher than your memory can carry gives stutter, not a better view.

In config.json, in the same folder as HytaleServer.jar. It holds ServerName, MaxPlayers and MaxViewRadius among others. With us you edit that file in the panel or over SFTP; restart the server to apply changes.

Then the CPU is full. Lower MaxViewRadius, remove plugins that do work every tick and check whether one player far from the rest is generating world. Buying more memory does not help here.

After every Hytale update at least, because the protocol changes with it. Beyond that, a daily restart at a quiet hour is a good habit during early access.

Some plugins dynamically lower the view distance when it gets busy, and that can help. But every mod costs memory and CPU time first. Start with fewer mods, not more.

On a hosted server you do nothing: the memory of your plan is the memory of the server. Running it yourself, give Java slightly less than the machine's total memory with -Xmx, so the operating system keeps room.