The Hytale server jar
"Server jar" is shorthand for the Hytale dedicated server program — the file you download and run to host a world without the game client. This page covers where it comes from, how it runs, and the update habits that keep servers alive.
What it is
The server software is the headless side of Hytale: it runs the world, holds the save, and accepts connections from game clients. It doesn't render anything, which is why it can run on hardware with no GPU and why providers can rent it out cheaply (see server hosting).
Where to get it — and where not to
What you're downloading: the current server build. What you're not downloading: your game license. The server software is the same for everyone; the client is what you own.
Running it
- Put the jar in its own folder. It writes config and world data next to itself — a dedicated folder keeps that data contained and easy to back up.
- Run it (double-click, or from a terminal for the full console experience). First boot generates config and the world.
- Read the console. The boot log tells you the port it bound and any errors. When something goes wrong later, this output is the first place to look — the failed-to-boot page walks the common errors.
- Configure and restart. Settings apply at boot; a server that "ignored" a config change usually just wasn't restarted.
Running it from a terminal (or script) is worth learning for one reason: the console accepts input while the server runs, and that's where you watch errors live instead of discovering them from player reports. Full setup context: the server guide.
Terminal basics for the terminal-averse
Four commands' worth of comfort covers most of server ownership:
| You want | You do |
|---|---|
| Start the server | Run the jar from its folder — a terminal open in that folder, then launch it there |
| Stop it cleanly | Use the server's own stop command or console input; force-closing is the corruption lottery |
| See what happened | Scroll the console, or open the log file it writes next to itself |
| Run it when you log out | A restart script or your platform's service mechanism — the difference between a server and a program you have to babysit, and the first step toward a proper dedicated setup |
When the jar misbehaves, fast
| Symptom | First move |
|---|---|
| Won't start at all | Read the boot log — it names the cause before you guess |
| Started, but nobody can connect | Version check, then port and firewall — the connection checklist |
| Crashes under load | Mods and player count first; hardware second |
| World problems after an update | The backup you made before updating — see the update procedure above |
Updating
The rule that prevents most failed to connect complaints: when the game client patches, the server must be updated too — mismatches refuse connections. Procedure:
- Back up the world folder. Always, before every update.
- Download the new server build from the same official source.
- Replace the old file, keeping the world and config in place.
- Boot, read the console, then connect once yourself before declaring it up.
Patch timing context lives on the update tracker.
Related pages
- Dedicated servers — hardware and 24/7 operation.
- How to host — the surrounding setup (firewall, router).