How to update a Hytale server (Chapter 1 and every patch)
To update a Hytale server on berrybyte, stop it, back up, turn on Auto Update with the release patchline, and start it. Self-hosted servers use /update download and /update apply --confirm with the official start scripts. Clients and servers must run the same version.
To update a Hytale server on berrybyte, stop it, take a backup, check that Auto Update is on, and start it again. The server downloads the latest build for its Patchline as it boots. Players need the same version, so they update their game too.
Hytale Chapter 1 released on October 12, 2026. Back up before your server's first Chapter 1 start, because existing worlds upgrade themselves the first time they load. The Chapter 1 update guide covers the update step by step.
Update on berrybyte
Stop and back up
Ask players to leave, stop the server, and wait until it's offline. Then create a backup and wait for it to finish. Stopping first means the backup has the latest save, not a copy taken mid-write.
Check Auto Update and the patchline
Open Settings → Game Settings. Turn on Auto Update and set Patchline to release
for the normal game. Auto Update checks the selected patchline each time the server starts.
Check your mods
Install builds whose authors support the new version. Removing a mod that adds blocks or items can affect the world, so test changes on a copy first. See install mods.
Start and watch Console
Start the server and let the download and boot finish. If Hytale asks for authentication again, complete Hytale Link.
Test with one player
Update one player's launcher to the same patchline, then join by address. Check the world, inventories, and important mod features before inviting everyone.
Why the server has to match the client
Hytale checks a protocol hash when a player connects. If the client and server aren't on the exact same protocol version, the connection is rejected. So when Hypixel releases an update, players who update can't join until the server updates too.
The Hytale Server Manual lists a ±2 version tolerance as "coming soon". As of the manual's last update (June 15, 2026), it isn't available, so plan to update the server as soon as a release lands.
Release vs pre-release
Hytale ships builds on a release and a pre-release patchline:
| Patchline | Use it for |
|---|---|
release | The normal game. Keep your main world here |
pre-release | Testing upcoming content before it ships |
The client and server must be on the same patchline, so everyone joining a
pre-release server switches their launcher to pre-release too. Chapter 1
was tested there as Update 7 before it released. See the
modder-facing patch notes
for the server changes.
Run pre-release only on a separate test server with a copy of your world.
A world opened on a newer build may not load on your release server again.
Update a self-hosted server
This section is for servers you run yourself. On berrybyte, use Auto Update. Don't replace
the launch files or run /update apply --confirm to copy the self-hosted flow.
Hytale has a built-in updater. It checks for a new version (every hour by
default), downloads it to updater/staging/, and shuts the server down with
exit code 8 when it's ready to apply. The start script sees exit code 8,
copies in the new server binaries and assets, and starts the new version. Your
config, saves, and mods are kept.
Required folder layout
The updater only works with this layout. Start the server from Server/, with
Assets.zip and the start script in the parent folder. If the layout isn't
detected, the update checker is disabled.
game/
├── Assets.zip
├── start.sh (or start.bat on Windows)
├── jvm.options (optional, custom JVM arguments)
└── Server/
├── HytaleServer.jar
├── HytaleServer.aot
└── config.jsonInstalls made with the Hytale Downloader or java -jar HytaleServer.jar --bootstrap
already use this layout. If you copied files by hand, run /update setup on the
running server to write start.sh and start.bat to the parent folder.
Update commands
Run these in the server console:
| Command | What it does |
|---|---|
/update check | Checks for an available update |
/update download | Downloads the update to updater/staging/ |
/update apply --confirm | Backs up files, then shuts down with exit code 8 so the start script applies the update |
/update cancel | Cancels and deletes the staged update |
/update status | Shows the current version and update status |
/update patchline [name] | Shows or sets the update patchline |
/update setup | Writes the start scripts to the parent folder |
/update download --force downloads the current version again, including the
start scripts and assets. To turn updates off completely, set the
HYTALE_DISABLE_UPDATES environment variable.
Update settings in config.json
The updater's settings live in the Update block of config.json. These are
the defaults:
{
"Update": {
"Enabled": true,
"CheckIntervalSeconds": 3600,
"NotifyPlayersOnAvailable": true,
"Patchline": null,
"RunBackupBeforeUpdate": true,
"BackupConfigBeforeUpdate": true,
"AutoApplyMode": "Disabled",
"AutoApplyDelayMinutes": 30
}
}| Key | What it does |
|---|---|
Enabled | Turns automatic update checks on or off |
CheckIntervalSeconds | Seconds between checks (3600 is one hour) |
Patchline | Overrides the patchline. null uses the build's own patchline, usually release |
RunBackupBeforeUpdate | Runs a full server backup before applying. Only works if a backup directory is configured |
BackupConfigBeforeUpdate | Backs up config.json, permissions.json, bans.json, and whitelist.json before applying |
AutoApplyMode | When staged updates apply on their own (see below) |
AutoApplyMode | Behavior |
|---|---|
Disabled | Never applies on its own. You run /update apply --confirm |
WhenEmpty | Applies when no players are online |
Scheduled | Applies after AutoApplyDelayMinutes (default 30) even with players online, warning them periodically |
The official start scripts pass --backup --backup-dir backups, so
RunBackupBeforeUpdate works out of the box. If you launch the JAR another
way, add a backup directory yourself. See
Hytale backups.
Start scripts and exit code 8
The server doesn't restart itself. start.sh and start.bat loop only on exit
code 8. Any other exit, including a normal stop or a crash, ends the script.
That's why you need them for updates to apply. The scripts also read custom JVM
arguments from jvm.options, one per line.
Roll back a bad update
If the server crashes shortly after an update, the start script points you to
updater/backup/, which holds your previous files. To roll back, delete
Server/ and Assets.zip, then move the files back from updater/backup/.
Those are server files only. If the new version already opened your world, restore your pre-update world backup too.
Hytale Downloader
The Hytale Downloader CLI gets server files and assets for a fresh install or a manual update:
./hytale-downloader # latest release
./hytale-downloader -print-version # show the game version without downloading
./hytale-downloader -patchline pre-release # download from pre-releaseIf the update fails
| Problem | Fix |
|---|---|
| Players can't join after the update | Update the client and server to the same patchline and version. See can't connect |
| A mod fails to load | Find the mod's file name in Console, then install a build for the new version or remove it for now |
| Server asks to authenticate again | Complete Hytale Link |
| World looks wrong or won't load | Stop the server and keep the current files before restoring anything |
| Self-hosted server crashes right after updating | Roll back from updater/backup/ and restore your world backup |
Restoring a world backup doesn't change the server version. A world already opened by a newer build may not load on an older one. On berrybyte, contact support with the backup date and startup log before you try a downgrade.
Related guides
Frequently asked questions
How do I update a Hytale server on berrybyte?
Stop the server and create a backup. In Settings → Game Settings, turn on Auto Update and check that Patchline is release, then start the server. It downloads the latest build as it starts, so wait for the boot to finish before players join with an updated game.
Will updating my Hytale server delete my world?
No. The update replaces the server files and assets and keeps your config, saves, and mods. A major update can upgrade the world the first time it loads, though, so take a backup before you start the new version.
Does restoring a world backup downgrade Hytale?
No. Restoring a backup replaces the world files but doesn't change the server version. A world opened by a newer build may not load on an older one, so keep your pre-update backup and contact support before you try to downgrade.
How do I switch a Hytale server to the pre-release patchline?
On berrybyte, stop the server, set Patchline to pre-release in Settings → Game Settings, and start it with Auto Update on. Self-hosted servers use /update patchline pre-release. Use a separate test server with a copy of your world, and switch every joining player's launcher to pre-release too.
How often does a Hytale server check for updates?
On berrybyte, Auto Update checks the selected patchline each time the server starts. A self-hosted server with the built-in updater checks every hour by default, set by CheckIntervalSeconds in config.json.