Build a Hytale Multi-Server Network with Player Referral
Connect Hytale lobby and game servers with Player Referral, connection redirect, signed payloads and secure QUIC deployment.
Hytale includes native mechanisms for sending a player to another server; a BungeeCord-style proxy is not required. Player Referral sends a target host, port and optional payload up to 4 KB to the client, which opens a new connection. That payload passes through the client and must be treated as mutable.
Choose the architecture
A simple network contains:
- a public lobby that authenticates players and presents destinations;
- separately authenticated Hytale game servers;
- a server-side matchmaking service or database as authority;
- stable DNS and a unique UDP/QUIC port per process;
- independent world backups and updates.
The lobby must not be the only source of truth for rights, inventory or currency. The target server should revalidate sensitive state against a trusted service.
Use Player Referral securely
The documented API is:
PlayerRef.referToServer(host, port, data)
data is optional and limited to 4 KB. The client presents it during the target handshake. The manual warns that clients can tamper with it: sign it with HMAC using a secret shared only by servers. Include a random session ID, destination, short expiry and replay nonce; never put the secret or a permanent privilege in the payload.
The target verifies signature, expiry, destination and one-time use, then retrieves authoritative session data from the backend. Reject invalid referrals cleanly and log an identifier without logging the secret.
Redirect, fallback and proxies
| Mechanism | When | Use |
|---|---|---|
| Player Referral | Already connected | Move from lobby to game server |
| Connection Redirect | During handshake | Regional routing, balancing or lobby-first policy |
| Disconnect Fallback | After unexpected loss | Return to a lobby |
| Netty QUIC proxy | Custom interception | Advanced protocol and routing needs |
The October 12, 2026 manual still marks fallback packet implementation as “Coming Soon”. Do not promise automatic recovery without checking the deployed release. Provide a clear manual way back to the lobby.
A custom proxy is possible with Netty QUIC and packet definitions in HytaleServer.jar, but it substantially increases security and protocol maintenance. Start with native Referral and Redirect.
Deploy and validate the network
Isolate every instance
Configure reachability
Implement a signed ticket
Test failure modes
Observe and back up
Production checklist
Security and operations
- •No secret or permanent privilege crosses the client in clear text.
- •Tickets are signed, short-lived and one-time.
- •Every target revalidates the session with a trusted authority.
- •UDP ports are public only when client connections require them.
- •Lobby and game servers use the same protocol build.
- •A failed target does not delete world or player state.
- •Fallback support is detected, not assumed.
Use the UDP/QUIC guide for network basics and the Hytale backup guide on every instance.
Deploy multiple Hytale servers
Compare Hytale hosting with multiple instances, UDP networking and scalable resources.
Frequently asked questions
Does a Hytale network require a proxy?
Can the Referral payload be trusted?
Is crash fallback guaranteed?
Primary source: Hytale Server Manual — Multiserver Architecture.
Ready to launch your Hytale server?
Here are the best Hytale hosting deals right now, promo codes included. Still unsure? Our quiz finds the ideal host for you in under 2 minutes.
My box 8
Minestrator
Specifications
Compatible games
Features
- ✓Mods en 1 click
- ✓DDoS Protection
- ✓Backups
Copper
Shockbyte
Specifications
Compatible games
Features
- ✓DDoS Protection
- ✓Backups
- ✓Support 24/7
Hytale — 6 Go
WinterNode
Specifications
Compatible games
Features
- ✓6 Go de RAM au minimum
- ✓CPU sans limite fixe, sous politique d'usage raisonnable
- ✓Stockage NVMe sans limite fixe, extension sur demande
- ✓Sauvegardes automatiques toutes les 12 heures
- +2 more features