Hytale server: tutorials & guidesYour Orbis, reachable around the clock

For a server of your own, Hytale brings quite a few things that other games only add through extensions. A server manages one universe, and several worlds can sit side by side inside it - each with its own configuration for seed, PvP, fall damage and NPC spawning. That way, a peaceful building world runs next to a PvP arena without you needing a second server for it. Each world computes on its own thread, and that is exactly what you should keep in mind when choosing a plan: two active worlds mean nearly twice the work.

When it comes to modding, Hytale takes a different route from Minecraft. Mods and plugins sit as .zip or .jar files in the mods folder on the server, and the game is designed for server-side modding: the content comes from the server when players connect, so your fellow players usually do not have to install anything themselves. For a community server, that is a big advantage - nobody fails anymore because the wrong version of a mod is sitting on their computer.

The most important lever for performance is the view distance. In the official server documentation, Hypixel calls it the biggest driver of memory usage and recommends limiting it to at most 12 chunks - that is 384 blocks. For comparison: a Minecraft server sees 160 blocks by default. Processor load, on the other hand, depends on the number of players and entities, meaning NPCs and creatures. If you keep the two apart, you will find out faster whether an upgrade helps or whether a setting is the real bottleneck.

Two things the server takes care of on its own with us. On the first start, a link and a code appear in the console, which you use to link the server to your Hytale account once - you do not need a command for that. And because Hytale only allows connections when client and server use exactly the same version, your server is updated automatically after an update. The server also backs up the world automatically; an additional copy stored outside the server is still a good habit.

We do not sell slots. You set the maximum number of players yourself in config.json, and the plans differ in memory and performance. In this order, you get to a server that needs no rework the fastest:

1. On the first start, confirm the link and code in the console and join yourself - with the full address made of IP and port.
2. Make yourself an admin with op add in the console before anyone else enters the server.
3. Decide whether a fresh world is created or a single-player save comes along - and finish the move before the first shared evening.
4. Set view distance, player count and password in the central config.json, and PvP and fall damage in the world's configuration.
5. Close the group with the whitelist, add mods and only then pass on the address.

Getting started: connect and manage

These four guides cover the first evening: connecting, giving yourself admin rights, knowing the most important commands and closing the group. The order is no coincidence. If you switch on the whitelist before making yourself an operator, you may lock yourself out in the worst case - so add yourself and your admins to the list before switching it on, and keep the console in the web interface as a fallback. And if you pass on the address before the server is closed, you may end up with guests you never invited.

Worlds, mods & settings

A Hytale server has a clear structure, and once you know it, you will find every setting right away. The server directory holds the central config.json with name, password, player count and view distance, next to permissions.json and bans.json. The universe folder contains player data and, under universe/worlds, all worlds - each with its own config.json for seed, PvP and fall damage. Mods and plugins belong in the mods folder. The same rule applies to all files: only edit them while the server is stopped, because Hytale reads them at startup and rewrites them when something changes in the game.

Operation: updates, backups, performance

Once the server is running, the work shifts to three ongoing topics. We apply updates automatically, because Hytale only allows matching versions on client and server - the construction site afterwards tends to be mods that lag behind their authors. The Hytale server backs up the world itself, but a copy stored elsewhere still belongs in the routine before major updates and new mods. And when things stutter, a look at the view distance helps first, before a bigger plan is the answer.

Troubleshooting

Almost every "Failed to connect" message has one of a few causes: the port is missing from the address, the server has not finished starting or is waiting for account linking, client and server are on different versions after an update, or the whitelist turns the player away. The checklist goes through these points in the order in which they occur most often.

Before you order

In Hytale, view distance, play style and mod load decide the plan - not a sold number of players. These guides help with the choice and show how billing works without a contract.

Technology & security

Hytale connects via the QUIC protocol over UDP, and the default port is 5520. With us, what counts is always the port assigned to your server - how the address is put together and what the server brings for protection is explained in these guides.

Frequently asked questions