Key takeaways
- Server name and MOTD — what players see in the server browser.
- Port — the listening port. Change it only if something else already occupies the default.
- Max players — set this below your RAM headroom, not at your hardware’s absolute ceiling; a full server with no spare memory is one boss fight away from a crash.
- View distance / simulation distance — the single biggest performance lever. Halving view distance can cut CPU and RAM load substantially, at the cost of players seeing terrain pop in.
- Whitelist toggle — for a private friends-only world, turn this on immediately. It is the difference between “our server” and “a public server that happens to have our name.”
- Difficulty and PvP flags — decide these before inviting anyone, because changing them mid-world resets expectations rather than saves.
How to Create Hytale Servers: Complete Setup Guide
Creating a Hytale server means running the standalone server build that ships alongside the game, opening the port it listens on (the server’s configuration file sets this; 5520 is the conventional default), and then tuning world settings, permissions, and backups so the world survives a crash or a bad update. The single biggest determinant of stability is not the mod list — it is RAM and disk type: a small 4–10 player world runs comfortably on 4 GB of RAM and an SSD, while heavily modded worlds with large view distances want 8–12 GB and a dedicated CPU core per two or three concurrent players. Everything below is the order that works: requirements, install, config, networking, permissions, backups, then performance.
Server Requirements: What Actually Matters
Hytale runs on a modified Java-based engine, so the server’s resource profile resembles a Minecraft Java server more than a lightweight lobby daemon. Per the game’s official documentation, the dedicated server supports both Windows and Linux, and the client can connect over the local network or the internet.
Our top picks
As an Amazon Associate we earn from qualifying purchases at no extra cost to you.
| Scope | vCPU | RAM | Storage | Bandwidth | Typical host price/month |
|---|---|---|---|---|---|
| 1–4 players, vanilla, private | 1–2 cores | 2–4 GB | 5 GB SSD | 2–5 Mbps up | $5–10 (VPS) or $0 (home PC) |
| 5–10 players, light mods | 2–3 cores | 4–6 GB | 15 GB SSD | 6–12 Mbps up | $10–20 |
| 10–30 players, mods + events | 4 cores | 8–12 GB | 40 GB NVMe | 15–30 Mbps up | $20–45 |
| 30+ players, minigames/regions | 6–8 cores | 16 GB+ | 80 GB NVMe | 50 Mbps+ up | $45–120 |
Three rules keep sizing honest. First, Hytale’s server is more sensitive to single-core clock speed than to core count, so a 4-core host at 3.5 GHz usually beats an 8-core at 2.2 GHz for the same player count. Second, storage type matters more than capacity — world saves and chunk loading are random-I/O heavy, and an SSD can cut chunk-load stutter dramatically versus a mechanical drive. Third, home hosting is limited by your upload speed, not download: 10 players at roughly 100–200 KB/s each means you want 10–20 Mbps of sustained upload, which many cable plans do not deliver.
Step-by-Step: Installing the Hytale Server
The installation is a short, linear sequence. Each step has a reason, and skipping the reason is what causes the “it works for me but not my friends” outcome.
- Install a current Java runtime. The server build requires the Java version named in the game’s official release notes — install that exact major version, because a newer runtime can break engine hooks and an older one simply refuses to start. Verify with
java -versionbefore going further. - Download the dedicated server package from your official account’s download page. Do not run a server binary from a third-party file host; you cannot audit what is inside it, and server binaries execute with your machine’s privileges.
- Unpack into a dedicated folder — for example
C:\hytale-serveron Windows or/opt/hytaleon Linux. Keep it out of your user profile and out of a synced cloud folder; sync clients lock files mid-write and corrupt world data. - Run the server once with defaults so it generates its config files and directory tree (worlds, logs, mods, and a config folder). Starting a server before you know where its files live is how people lose a world during a migration.
- Accept the end-user license and any server terms the first run prompts for, and confirm the server banner in the console lists the version you intended.
- Stop the server cleanly with its console stop command rather than closing the window. An unclean stop is the most common cause of a truncated world file.
Configuration: The Settings That Change the Experience
Configuration lives in the server’s text config files, typically one for networking and one for gameplay. These are the settings worth changing on day one.
- Server name and MOTD — what players see in the server browser.
- Port — the listening port. Change it only if something else already occupies the default.
- Max players — set this below your RAM headroom, not at your hardware’s absolute ceiling; a full server with no spare memory is one boss fight away from a crash.
- View distance / simulation distance — the single biggest performance lever. Halving view distance can cut CPU and RAM load substantially, at the cost of players seeing terrain pop in.
- Whitelist toggle — for a private friends-only world, turn this on immediately. It is the difference between “our server” and “a public server that happens to have our name.”
- Difficulty and PvP flags — decide these before inviting anyone, because changing them mid-world resets expectations rather than saves.
As a worked example: a 10-player server set to a moderate view distance with a max-player cap of 12 will typically sit around 4–5 GB of RAM in use during normal play. Dropping view distance one notch often frees 1–1.5 GB — roughly the headroom you need to add a modest mod pack without renting a bigger machine.
Networking and Port Forwarding
Port forwarding is the step that fails most often, so treat it as three separate checks rather than one.
- Give the host machine a static local IP (a DHCP reservation in your router is cleaner than setting it on the machine). If the host’s local IP changes on reboot, your forwarding rule silently points at nothing.
- Forward the server’s TCP port to that local IP in your router’s port-forwarding page. Forward the port the config file actually uses; many “my server won’t accept connections” cases are a forwarding rule for a port the server does not listen on.
- Allow the server through the host firewall for the same port, on private and public profiles if the connection comes from outside.
- Confirm from outside using a port-check tool while the server is running. Testing from inside your own network does not prove anything — routers often loop local traffic back regardless of the rule.
If port forwarding is not an option (carrier-grade NAT, shared housing, strict ISP), the alternatives are a hosted game server from a provider or a tunneling service that gives players a public address without touching your router. Hosting on a VPS also removes the upload-bandwidth ceiling entirely.
Permissions: Who Gets to Break the World
Set permissions before you invite the second person, not after the first incident. A workable default structure looks like this:
- Owner/Admin — you. All commands, including world-editing and stop/restart.
- Moderator — kick, mute, teleport, roll back a build. No access to server files or the stop command.
- Builder — creative-style building rights in designated areas only. This prevents a well-meaning friend from flattening the spawn town.
- Member — normal survival play, no world-editing commands.
- Guest/Whitelisted-visitor — read-and-walk only until you trust them.
The rule of thumb: never grant a permission because it is convenient during setup. Permission changes are reversible in seconds; a griefed world is not, and restoring from backup costs you everyone’s progress since the last save.
Backups: The Part That Saves You
Backups are cheap and the alternative is starting over. Per common hosting practice, run two tiers:
| Tier | Frequency | Retention | Where it lives | Purpose |
|---|---|---|---|---|
| Automatic snapshot | Every 30–60 min | Last 12–24 copies | Same machine or host panel | Recover from crashes, bad mods |
| Off-machine archive | Daily | Last 7–14 days | External drive or cloud storage | Recover from disk failure, ransomware, deletion |
| Milestone copy | Before any update or mod install | Keep indefinitely | Clearly named folder | Roll back a broken update |
Two mechanics to know: stop the server (or use its save command) before copying world files, because a live copy can capture a half-written region; and always test-restore one backup into a throwaway folder before you need it. An untested backup is a hope, not a plan. On disk cost, a modest world occupies a few hundred MB; a heavily explored world with mods can pass 5–10 GB, which is why 15 GB of storage is a realistic floor for a small server and 40 GB is comfortable.
Performance Settings That Hold Up Under Load
- Cap view and simulation distance first, then add players, then add mods. Tuning in that order means you always know which change caused a regression.
- Pre-generate anything you can. Generating new terrain while ten players explore in different directions is the heaviest sustained load a Hytale server takes.
- Watch memory, not CPU, for crashes. Consistent CPU at 70% is fine; RAM climbing until the server dies is the classic failure.
- Check the log after every restart. Errors before the “server ready” line predict tomorrow’s crash.
- Restart on a schedule (weekly is common) during a low-activity window, right after a save and backup.
The durable-upgrade order, if you are paying for a host: NVMe storage first, then RAM, then CPU clock speed, then extra cores. People routinely buy cores they cannot use and then wonder why the server still stutters when someone crosses a chunk boundary.
Frequently Asked Questions
How much RAM does a Hytale server need?
For a small private world with 1–4 players, 2–4 GB is workable; 5–10 players with light mods usually wants 4–6 GB; and heavily modded worlds with 10–30 players are comfortable at 8–12 GB. Size for headroom rather than the exact figure you observe at idle, since memory use climbs as players explore new terrain. If the server gets killed by the operating system, RAM is almost always the cause before CPU is.
Do I need port forwarding to host a Hytale server?
If friends connect from outside your home network, yes — the server’s listening port must reach the host machine, which normally means a port-forwarding rule plus a firewall exception. If your ISP uses carrier-grade NAT or you cannot change router settings, use a hosted game server or a tunneling service instead. Testing connections from inside your own network will not tell you whether the rule works.
Can I run a Hytale server on my gaming PC while I play on it?
Yes, and a modern gaming PC often outperforms a cheap VPS for a handful of players. The constraints are your upload bandwidth and the fact that the server competes with the game client for CPU and RAM. Close background apps, cap the player count, and expect that a 10-player server plus local play is about the practical ceiling for a mid-range machine.
How often should I back up a Hytale server world?
Take automatic snapshots every 30–60 minutes, keep an off-machine archive daily for one to two weeks, and make a separate named copy before every update or mod installation. Back up with the server stopped or after issuing a save command, because copying live region files can capture partial data. Test-restore at least one backup so you know the archive is actually usable.
Which server settings hurt performance the most?
View distance and simulation distance are the largest levers — reducing either meaningfully lowers CPU and memory load at the cost of visible terrain pop-in. After that, the number of loaded mods, the number of players exploring new terrain simultaneously, and an oversized max-player cap all compound. Change one setting at a time so you can attribute any stutter or crash to a specific edit.
How do I stop random players from joining my Hytale server?
Enable the whitelist and add players by name before opening the server, and keep the max-player cap tight. Set up permission tiers so a new arrival starts as a guest or member rather than a builder, and never hand out admin rights during setup. If you later want public access, add a moderator role before you remove the whitelist, not after.
