Hytale multiplayer not working
Multiplayer failures come in two shapes: you can't connect to anything (that's the failed to connect page), or the specific arrangement between you and your friends is broken (this page).
Check 1: everyone on the same version
The most common friend-group failure, and the cheapest to fix: after a game patch, one of you updated and the rest didn't. Mismatched versions refuse connections with errors that look network-ish.
- Everyone checks their game version.
- Everyone updates — or the host downgrades, if the server hasn't updated yet (server owners: server update procedure).
- Retry. Patch weeks make this check worth doing first every single time.
Check 2: whose end is broken?
One test cuts the problem in half:
- Can the host connect to themselves? Host joins their own server address locally. Failure here is a server problem — see server failed to boot.
- Can one specific friend connect while another can't? The problem is that friend's machine or network — their firewall, their VPN, their NAT.
- Nobody can connect except the host? It's the host's network: port forwarding and firewall, both covered in how to host.
Check 3: NAT and home networks
Strict NAT — common on mobile hotspots, some ISPs, and hotel/campus networks — breaks direct connections in ways no game setting fixes:
- Test by connecting from a different network (mobile hotspot is the standard isolation tool).
- It works on hotspot but not home Wi-Fi → the router or ISP is filtering; router-level fixes are in the server guide.
- If no share code appears at all when the host clicks Save in Online Play, the game couldn't negotiate a path out — enable UPnP on the router first, then regenerate the code.
- If the host is behind CGNAT (the router's WAN IP is a private 10.x/192.168.x/172.16–31.x range, or differs from your public IP), inbound IPv4 joins can't reach you, period. The community-standard workaround is Tailscale: install it on the host's and friends' PCs, join the same network, then regenerate the share code — Hytale detects the virtual addresses and adds them as high-priority candidates, so friends connect through the tunnel and skip the router entirely.
- For groups where NAT is unavoidable and Tailscale isn't acceptable, moving the world to rented hosting sidesteps home networking entirely.
Check 4: mods, when they're in the picture
If the server runs mods, clients may need matching versions — the mismatch shows up exactly like a network failure. Multiplayer mods run on the server: they belong in the server's mods directory (e.g. C:HytaleServermods), not the client's UserData folder. Diagnosis and fix: how to install mods, server section.
Invite codes specifically
Friend joins run on share codes, and codes go stale: they encode the session's candidate addresses including its UDP port, so any network change invalidates them. The fixes, in order:
- Regenerate the code — Online Play → Save again. Most "the code stopped working" cases are just this.
- Regenerate after enabling UPnP or forwarding a port — the new code includes the forwarded port; the old one doesn't.
- Generate a fresh code if the host's session reconnected (router restart, PC sleep) — the old candidates are dead addresses now.
One table to isolate the failure
| Observation | Broken side | Go to |
|---|---|---|
| Host can't connect to their own server | Server | Server failed to boot |
| Everyone except one friend connects | That friend | Their firewall, VPN or NAT |
| Nobody outside the host's network connects | Host's network | Port forwarding |
| Nobody can connect, host included | Server | Boot log |
| Worked until the game updated | Versions | Update everyone, then the server build |
| Works on mobile data, not home Wi-Fi | Router/ISP | Router filtering, below |
The pre-game-night check
If you play on a schedule with the same group, two minutes before session start prevents the classic evening-ruining discoveries:
- Host: is the server up, and is it on the current version? The console tells you both in ten seconds. Do this before anyone asks "why can't I join?"
- Everyone else: did the game update since last session? Auto-updates pick the worst moments. A version check before launch takes one click.
- If anything updated: do the mods match? Server mods plus client mods plus game version is three things that must agree — see the mod browser guide for keeping sets aligned.
The pattern worth internalizing: almost every multiplayer failure is a mismatch — version, mod, address, or expectation. When something breaks, ask "what doesn't match?" before "what's broken?"
The reset button
When you've worked the list and it's still broken: have the host restart the server and read its console output while one friend attempts to connect. The console shows the attempt arriving or not — that one observation tells you which side to keep debugging.
- Attempt visible, connection fails → negotiation problem: versions or mods.
- Attempt never arrives → network: firewall, forwarding, NAT — walk the firewall page.
Related pages
- Multiplayer overview — how it works when it works.
- Failed to connect to server — the general connection checklist.