How to Create & Join Hytale Server: Setup Guide

What This Guide Covers

To play Hytale with friends on your own terms — persistent worlds, custom settings, no public-server chaos — you need three things working together: a machine that meets the server’s requirements, a correctly configured server build, and a network path that lets your friends reach it. Once those are in place, joining takes under a minute via a direct IP or an invite.

System Requirements: Server vs. Client

A Hytale server is a dedicated process, and it does not need the same hardware profile as the game client. The client needs a GPU and a display pipeline; the server needs single-core clock speed, RAM headroom, and a stable upstream connection. Because Hytale supports player-hosted and community-style world setups, treat these as working targets rather than fixed minimums — smaller servers (2–5 players) sit comfortably at the low end, larger worlds push toward the high end.

Hardware Targets by Server Size

Two numbers matter more than the rest. First, single-thread performance: world simulation ticks on one main thread, so a 4.0 GHz quad-core will out-serve a 2.4 GHz octa-core for most small servers. Second, upstream bandwidth, not download — home connections are usually asymmetric, and 10 Mbps down often means only 1–3 Mbps up, which is enough for 2–3 players and no more.

Step-by-Step: Creating the Server

1. Get the server files

Download the official Hytale server package from the game’s official distribution channel. Extract it into its own folder — for example C:\HytaleServer or /opt/hytale-server. Keep it separate from your game client install; mixing the two is the most common cause of version mismatch errors.

Why: a clean, isolated directory makes updates and backups a copy-paste operation instead of a hunt for stray files.

2. Install the runtime

Hytale’s server runs on Java. Install the version specified in the server package’s own documentation (the bundled readme or patch notes names the exact required major version). Install it system-wide rather than bundling a copy in the server folder, so future version bumps apply everywhere at once.

Why: running a newer or older Java major version than the server expects is the single most common startup failure, and the error messages are often unhelpful.

3. Launch once to generate configs

Run the server’s start script (typically start.sh or start.bat) and let it generate the default configuration files. It will fail or exit on this first pass — that’s expected. You’ll now see files like server.properties, world.json, and a mods folder.

4. Edit the key settings

Open server.properties in a plain-text editor. The settings worth changing immediately:

• server-port — default 5520. Change only if it conflicts with another service.
• max-players — set to your RAM tier from the table above, not higher.
• online-mode — keep enabled for public servers; disable only for a locked-down LAN test.
• view-distance — 8–10 chunks for small servers; 12+ will spike RAM and CPU with no visual payoff for distant players.
• difficulty and world-name — cosmetic and gameplay preference.

Why each matters: max-players above your RAM tier causes garbage-collection stutter, not a clean refusal — the server just gets laggy. view-distance is the cheapest performance lever you have.

5. Decide RAM allocation before you launch

Edit the start script’s Java flags to set a fixed heap. A worked example for an 8 GB machine:

• Operating system + background services: ~2 GB
• Java heap (-Xmx): 5 GB
• Headroom for native allocations and file cache: ~1 GB

Set -Xms equal to -Xmx (both 5G) so the heap doesn’t resize mid-session. Leaving -Xmx unset lets the server grab whatever it wants and eventually starve the OS.

6. Accept the EULA and start for real

Most server packages require acknowledging a EULA file before the first successful boot. Set it, launch again, and wait for the console to print a “server started” line with your port number. If it exits with a stack trace, check Java version first, then RAM flags, then port conflicts — in that order.

Port Forwarding, Explained Without Jargon

Your router hides every device behind one public IP. Port forwarding is a written instruction telling it: “traffic arriving on port 5520 should go to the machine at 192.168.1.42.” Without it, friends on the internet can’t reach your server even though it’s running fine.

Numbers you need before you start

• Server’s local IP: a static address you assign on the host machine (e.g. 192.168.1.42). If you skip this, DHCP can hand out a new address after a reboot and your forward rule silently breaks.
• Port to forward: 5520 UDP and TCP. Forward both protocols — some traffic uses each and partial forwarding causes intermittent “can’t connect” reports.
• External port: keep it identical to the internal port to avoid confusion.
• Your public IP: the address friends type in. It’s often dynamic, which is why many hosts use a dynamic-DNS hostname instead of a raw number.

The forwarding steps

1. Log into your router’s admin page (usually 192.168.1.1).
2. Find the Port Forwarding / NAT section — not DMZ, which exposes the whole machine.
3. Create a rule: external 5520 → internal 192.168.1.42:5520, TCP+UDP.
4. Reserve the host’s IP in the router’s DHCP reservation table so it never changes.
5. Test from outside your network — a phone on mobile data, not your own Wi-Fi. Testing from inside the same LAN will succeed even when forwarding is broken, which is the classic false positive.

If forwarding isn’t an option

Carrier-grade NAT (common on mobile-broadband and some fiber ISPs) blocks forwarding entirely — the public IP isn’t yours. Options in order of preference: rent a small VPS (see the cost column above), use a mesh VPN overlay that puts friends on a virtual LAN, or rent server hosting from a provider that handles networking for you. Don’t waste hours fighting a router you can’t win against.

How Friends Join

Method 1: Direct IP

Send friends your public IP (or dynamic-DNS hostname) and the port, formatted as 203.0.113.45:5520. In the game’s multiplayer menu they choose “direct connect” and paste that. If it times out, the problem is almost always forwarding or firewall — not the game.

Method 2: Invites

Where invite links are supported, the server generates a shareable token or code from the console. Anyone with the link joins without needing to know the IP. Treat invite codes like passwords: they bypass the “how do I find you” step but not whitelist rules, and a leaked code on a public channel can bring strangers in. Regenerate the code if it spreads beyond your group.

Method 3: LAN / virtual LAN

For a same-house group, the local IP plus port works with no forwarding at all. For friends in different cities, a virtual-LAN overlay makes them appear local — same connection method, no router changes, at the cost of slightly higher latency since traffic routes through the overlay.

Whitelisting: the step most people skip

An open server with a forwarded port gets scanned within hours. Enable the whitelist, add your friends’ exact usernames, then decide whether to publish. This also makes troubleshooting easier — “can’t join” becomes either a whitelist miss or a network issue, not both.

Performance and Ownership Realities

What wears down first

• Storage: world files grow continuously. A busy 10-player world can add several GB per month between world data and logs. Budget 25 GB for a mid-size server and prune logs.
• RAM pressure: the failure isn’t a crash, it’s stutter that gets worse each week as the world grows. If 8 GB was fine at launch, expect to need 12–16 GB by month three.
• Uptime expectations: a home-hosted server dies when you sleep, update, or lose power. Friends notice. If they expect a persistent world, a VPS with automatic restarts is the honest answer.

Maintenance that prevents most problems

1. Nightly backups of the world folder — copy it while the server is stopped or after a save command, not during writes.
2. Match client and server versions after every update. The client auto-updates; the server doesn’t. Update the server first, then tell friends to update.
3. Read the patch notes before updating. Server-format changes can invalidate plugins or mods, and rolling back is harder than waiting a day.
4. Watch the console for tick-time warnings — they appear before players feel lag, giving you time to trim view distance or reduce player count.

Frequently Asked Questions

Do I need a separate computer to host a Hytale server?

No — you can host on the same machine you play on, but you should subtract your client’s usage from the server’s budget. Practically, that means a 16 GB machine can serve a small group while you play, and an 8 GB machine struggles once the client is also running. A spare desktop or a cheap VPS avoids the competition entirely.

How much RAM does a Hytale server actually need?

Four gigabytes is workable for 2–5 friends in a fresh world; eight gigabytes is the comfortable entry point for 6–12 players; sixteen gigabytes and up covers larger worlds and mod load. The number that matters is the Java heap (-Xmx), which should be roughly three-quarters of total system RAM, leaving the rest for the operating system.

Why can’t my friends connect even though the server says it’s running?

Almost always one of three things: the port isn’t forwarded on both TCP and UDP, the host machine’s local IP changed after a reboot, or a firewall on the host is blocking inbound traffic. Test from outside your network using mobile data — connecting from another device inside your own house proves nothing.

Is a public IP necessary, or can I use an invite link?

Invite links remove the need for friends to know your IP, but they don’t remove the need for your server to be reachable from the internet — unless you’re using a virtual-LAN overlay. If your ISP uses carrier-grade NAT, invite links won’t save you; the overlay or a rented VPS is the real fix.

How many players can one home connection support?

Upstream bandwidth is the limit, not CPU. Each active player consumes roughly 1–2 Mbps of steady upstream traffic, so a typical 10 Mbps upstream connection tops out around 5–8 players before rubber-banding appears. Check your actual upload speed rather than your advertised plan.

What happens to the world if I update the server?

World data usually carries forward, but server-format changes can require a migration and can break mods. Back up the world folder before every update, update the server before the clients, and read the official patch notes first — if the notes flag a format change, wait a few days for community tooling to catch up.