Chapter I (Update 7) went live on 12 October 2026, and every player's game updated itself. Your server did not: as long as it stays on Update 6, nobody can join it. This is also the trickiest update since Early Access began, because it converts your world with no way back and breaks a large share of existing mods. Here is a step-by-step checklist, checked against version 0.7.2, for updating an existing server without losing anything.
What Chapter I changes for an existing server
If you are starting from scratch, our guide on how to create a Hytale server covers the full install. This article assumes you already run a server on Update 6. According to Hypixel Studios' official patch notes, these are the changes that affect you directly:
| Change | What it means for you |
|---|---|
| New network protocol version | An updated client cannot join a server still on Update 6, and vice versa. |
| New storage format for block sections | Worlds are converted the first time they load. They use less disk space, but can no longer be opened by an older server. |
| Many modding API methods removed or replaced | .jar mods built for Update 6 can stop the server from starting. |
| Renamed assets and a new format for some audio fields | Content packs that rely on the old names may fail to load. |
| New check on the launcher install folder | The server exits with code 11 if its working directory, world or backups sit inside the launcher's install folder. |
MaxViewRadius capped at 32 | Values outside 1 to 32 are clamped with a warning instead of blocking startup. |
| Renamed commands | /fragment becomes /portal, /leave becomes /portal leave and /cursethis becomes /ephemeral. |
Which version to install: 0.7.2 or later
Do not stop at the 0.7.0 launch build. Two hotfixes followed, and both matter for servers:
- 0.7.1 (13 October): joining a world hosted on Windows no longer times out after 30 seconds, and a player whose IP address changes mid-session can reconnect instead of being rejected as "already logged in".
- 0.7.2 (14 October): fixes a crash that disconnected every player in a world when a cave chunk loaded an old goblin spawn beacon created under Update 6. That is exactly the situation of a converted world. 0.7.2 also fixes a Linux crash in worlds that use RocksDB chunk storage.
At the time of writing, 0.7.2 is the latest Chapter I hotfix. Before you start, check what is available with /update check or ./hytale-downloader -print-version.
Step 1: plan the maintenance window
Warn your players and set aside about an hour for the backup, the first start and some testing. Then note your current version from the console:
/update statusFinally, take stock of your mods/ folder: the file name and version of each mod, and whether its author has released a Chapter I build. You will need this list in step 3 and when you put mods back.
Step 2: back up your world, your only real safety net
The universe/ folder holds your worlds and player data. Because the conversion is one-way, a copy taken before the first start on 0.7.x is your only route back. Stop the server cleanly with /stop, then archive the world, config files and mods, ideally outside the server folder:
# Linux, from the Server/ folder
tar -czf ~/hytale-update6-$(date +%F).tar.gz universe mods config.json permissions.json whitelist.json bans.json# Windows (PowerShell), from the Server\ folder
Compress-Archive -Path universe, mods, config.json, permissions.json, whitelist.json, bans.json -DestinationPath ..\hytale-update6.zipCheck that the archive is not empty and that its size is roughly that of universe/. If one of the listed files does not exist on your server, just remove it from the command.
The built-in updater can also run a full backup before applying a new version through the RunBackupBeforeUpdate option, but only if a backup directory is configured (--backup-dir). Treat it as an extra layer, not as your only copy.
Step 3: set your mods aside
Chapter I removed or replaced a long list of methods that mods use to work with chunks, blocks and worlds. A mod that calls a method that no longer exists can fail to load or even stop the whole server from starting. For a predictable update, start the new version with no mods at all:
mkdir mods-update6
mv mods/* mods-update6/On Windows, simply move the contents of mods into a mods-update6 folder in File Explorer.
Be careful with mods that add blocks or items. If you load your real world without them, those blocks may disappear or be replaced. In that case, do the first mod-free start on a copy of the world, and only open your main world once Chapter I builds of those mods are installed.
Step 4: install the new version
Option 1: the built-in /update command
This is the official method if your server follows Hypixel's expected layout: a parent folder containing Assets.zip and the start.sh or start.bat script, with the server running from the Server/ subfolder. Without that layout, the updater disables itself. The server must also be authenticated with /auth login device.
/update check # look for a new version
/update download # download it to updater/staging/
/update apply --confirm # back up, then shut down (exit code 8)The server does not restart itself. It exits with code 8, and the start.sh or start.bat script detects that code, copies the new files (HytaleServer.jar, Assets.zip and the scripts) while keeping your config, worlds and mods, then starts the server again. If you launch java directly, or through a service that does not use these scripts, the update stops there. Copied your files by hand and have no scripts? /update setup writes them to the parent folder.
Changed your mind before applying? /update cancel deletes the staged update.
Option 2: the Hytale Downloader
On a VPS, the official command-line tool is the most predictable method. Update the tool first, then download the new version to a temporary folder:
./hytale-downloader -check-update # update the tool itself if needed
./hytale-downloader -print-version # show the available version
./hytale-downloader -download-path hytale-0.7.2.zip
unzip hytale-0.7.2.zip -d new-versionThen copy only the game files into place: Server/HytaleServer.jar (plus HytaleServer.aot if present), Assets.zip, and start.sh and start.bat. Never overwrite config.json, universe/ or mods/ with the ones from the archive.
Option 3: with a hosting provider
On a hosting panel, updating usually means reinstalling the game version or pressing a dedicated button. Still take your step 2 backup and download it to your own computer before you start.
Step 5: first start and world conversion
Start the server and watch the console. On first load, each world is converted to the new format, which can make startup slower on a large world: do not interrupt it. Then check:
- that
/update statusshows the new version; - that the
logs/folder contains no errors; - any warning about
MaxViewRadius: if you see one, stop the server and set the value inconfig.jsonto 32 or lower; - that one player with an updated game can join before you reopen the server to everyone.
If the server exits straight away with code 11, its data is inside the launcher's install folder: move the server folder somewhere else. The --allow-install-dir flag forces startup anyway, but Hypixel warns that it risks data loss.
Also update any scheduled tasks or admin scripts that still use /fragment, /leave or /cursethis.
Step 6: add your mods back one at a time
For each mod on your list, get the build its author lists as Chapter I compatible, drop it into mods/, restart and read the logs. One mod at a time: if the server refuses to start, you know at once which one is to blame. A mod with no compatible build stays in mods-update6/ until its author updates it.
Common errors after the update
| Symptom | Cause | Fix |
|---|---|---|
| Every player is refused with a version mismatch message | The server is still on Update 6 | Update the server and restart it |
| Only one player is refused | Their game is outdated, or they are on another patchline (pre-release) | Restart the launcher and check the release patchline |
| The server exits with code 8 | Normal behaviour during an update | Start the server with start.sh or start.bat |
| The server exits with code 11 | Data inside the launcher folder | Move the server to its own folder |
| A mod fails to load | Mod built for Update 6 | Remove it and wait for a Chapter I build |
| Everyone is disconnected while exploring caves | Old goblin spawn beacon (fixed in 0.7.2) | Install 0.7.2 |
| A world crashes on Linux | RocksDB chunk storage (fixed in 0.7.2) | Install 0.7.2 |
| Joins time out after 30 seconds on a Windows server | Bug fixed in 0.7.1 | Install 0.7.2 |
/leave no longer works | Renamed command | Use /portal leave |
How to roll back if things go wrong
After an update through /update, the previous server files are kept in updater/backup/. The official script explains the procedure: delete Server/ and Assets.zip, then move the files back from the backup folder. Those files do not include your old world: since it was converted, you also need to replace universe/ with the copy from step 2.
Keep one thing in mind: a server rolled back to Update 6 will not accept players whose game is already on Chapter I. Rolling back is mainly a way to recover an intact world, not to keep playing on the old version. In most cases, the right move is to restore the backup, remove the faulty mod and run the update again.
Automate future updates
As long as client and server must run exactly the same protocol version, every new release forces you to update quickly. Hypixel has announced a tolerance of two versions between client and server, but it is not available yet. Until then, the Update section of config.json can do the work for you:
"Update": {
"Enabled": true,
"CheckIntervalSeconds": 3600,
"RunBackupBeforeUpdate": true,
"BackupConfigBeforeUpdate": true,
"AutoApplyMode": "WhenEmpty",
"AutoApplyDelayMinutes": 30
}With WhenEmpty, the update is applied as soon as nobody is online. Scheduled applies it after the set delay, even with players online, warning them first. The default, Disabled, waits for your /update apply --confirm. On a heavily modded server, keep the manual mode: an automatic update could restart the server with mods that no longer work. To switch the updater off entirely, set the HYTALE_DISABLE_UPDATES environment variable.
Stress-free updates with a hosting provider
At OuiHeberg, every Hytale-ready OuiBox plan includes backups you can take before an update: 5 with the OuiBox 8G at €9.98 per month, 10 with the OuiBox 12G at €16.79 per month and 15 with the OuiBox 16G at €21.59 per month. Take a backup from the panel, update, and restore it if anything goes wrong, with no command line needed.
FAQ
Will I lose my world when moving to Chapter I?
No. The world is converted automatically and keeps your builds. The conversion is permanent, though: without a copy taken before the update, there is no way back to Update 6.
Why can't my friends join my server since 12 October?
Their game moved to Chapter I and your server is still on Update 6. Both must run exactly the same protocol version, so update the server.
Do my mods still work with Update 7?
Not necessarily. A large part of the API mods rely on has changed. Only mods rebuilt by their author for Chapter I are safe.
Do I need to authenticate the server again after updating?
Normally not, as the authentication files stay in the Server/ folder. If the server asks, run /auth login device again: since Chapter I, it works even while a session is already active.
How do I check my server's version?
Type /update status in the console. To see the latest version available, use /update check or ./hytale-downloader -print-version.