Hytale Chapter 1 Server Update: Exit Code 11, Protocol, Mods

Q: What does exit code 11 mean on a Hytale server?

Since Update 7 the server refuses to boot when its working folder, --universe, --prefab-cache or --backup-dir sits inside the Hytale launcher's install folder. It prints how to move them and exits with code 11. Move the server to a folder of its own, or add --allow-install-dir if you accept the risk of losing data.

Q: Why can't players join my Hytale server after Chapter I?

Usually because the server and the players are on different builds. Client and server must be on the exact same protocol version, so update the server to 0.7.2 and have players restart the launcher. Hypixel has not published the exact text of the mismatch message.

Q: Can I go back to Update 6 after my world loaded on Chapter I?

Not with an upgraded cubic world, which an older server cannot open. Hypixel does not say whether other worlds can go back, so restore the copy you made before the first boot on Update 7. Update 7 players cannot join an Update 6 server anyway.

Q: Do I need 0.7.2, or is 0.7.1 enough?

Use 0.7.2. It fixes a Linux crash in worlds with RocksDB chunk storage and a world crash that disconnected every player, and it is the current release on Hypixel's documentation site.

Q: Do my plugins still work after Update 7?

Many need a new build. Update 7 removed the old chunk accessor classes and changed TickProcedure.onTick, among others, and plugins that use removed methods will not compile. Install builds made for Update 7 and read the first boot log.

JochemCEO of Space-Node

Published on 2026-10-16

Chapter I (Update 7) for Hytale server admins: exact version match, the exit code 11 folder check, world upgrades, plugin API breaks and the 0.7.2 fixes.

Three Hytale players next to a wooden village notice board covered in pinned notes

After Hytale's Chapter I update, your server has to run exactly the same build as your players' game, and as we write this the current build is 0.7.2 from 14 October 2026. If the updated server stops at boot with exit code 11, it is writing into the Hytale launcher's install folder: move the server and its worlds to a folder of their own, or start it with --allow-install-dir if you accept the risk of losing data.

Chapter I: Out of the Breach is Update 7. Hypixel Studios released it to Exploration Mode on 12 October 2026 (announcement and full changelog) and shipped hotfix 0.7.1 on 13 October and 0.7.2 on 14 October (hotfix notes). The server side is spread over the modder-facing patch notes and the Hytale Server Manual, which Hypixel updated on release day. Everything below comes from those pages, and we say so where they stop. If you are setting up your first server, start with our Hytale hosting guide.

What Chapter I changes for your server

Change	What you need to do
Protocol changes	Run the same build on the server and in every player's game
New install folder check	Keep the server, its worlds and its backups out of the launcher's install folder, or it exits with code 11
New world format	Back up before the first boot, because worlds upgrade when they load
Plugin API rework	Install plugin builds made for Update 7
View distance cap	A `MaxViewRadius` above 32 is clamped to 32
Hotfixes 0.7.1 and 0.7.2	Update to 0.7.2, especially on Linux with RocksDB chunk storage

Server and players must be on the same build

The manual is blunt about it: "Client and server must be on the exact same protocol version. When we release an update, servers must update immediately or players on the new version cannot connect." Compatibility is checked on a hash of the protocol, and "If hashes don't match exactly, the connection is rejected." A tolerance of "±2 version difference" is still listed under "Coming Soon", so it does not exist yet (manual, Misc Details).

Update 7 changes the protocol in several places. The modder notes say "the protocol version was bumped" for a language field, that "Clients and servers have to be on matching protocol versions" after a change to how chunk environments are sent, and that "The client and the server have to be built from the same protocol build." An Update 6 server will not take Update 7 players, and an Update 7 server will not take players who have not updated.

Hypixel has not published the exact wording players see on a mismatch, so we cannot quote it. The manual only says the connection is rejected. Update 6 fixed "version mismatch and connection timeout messages" that did not show their text when a player was disconnected before fully joining (Update 6 notes), so a player on the wrong build should get a version mismatch message on the join screen rather than a bare timeout.

If your server is listed in Server Discovery, the list was built with "compatibility checks so players only see servers they can actually join" (Hypixel's server list post). Expect an outdated server to drop out of the list for players on the new build.

To check versions:

/update status on the server console shows the current version and update status, and /update check looks for a newer one.
./hytale-downloader -print-version prints the game version without downloading it.
Hypixel's server documentation lists 0.7.2 as the current release, and its Java API reference is labelled "Hytale Server API 0.7.2".

The hotfix notes don't say whether 0.7.1 or 0.7.2 changed the protocol hash. Don't test that on your players: put the server on 0.7.2 and ask everyone to restart the launcher. Players who switched the launcher to the pre-release patchline (Launcher → Settings → Pre-Release, as the Update 7 pre-release notes put it) can end up on a different build from a release server.

Exit code 11: the server refuses to boot in the launcher folder

This check first appeared in the 3 September pre-release and is now part of the release. The modder-facing notes describe it like this: "The server now refuses to boot when the content it writes would land inside the launcher's install folder, which every update patches or wipes." It covers the working directory plus the --universe, --prefab-cache and --backup-dir paths, and "it prints the steps to move them somewhere safe before exiting with code 11." Hypixel has not published the text of that console message, so read it on your own console before you change anything.

This mostly hits servers that run on the same PC as the Hytale launcher. The manual's quickest way to get server files is to copy the Server folder and Assets.zip out of the launcher installation, which it lists as %appdata%\Hytale\install\release\package\game\latest on Windows and $XDG_DATA_HOME/Hytale/install/release/package/game/latest on Linux. If you skipped the copy and started the server in place, or pointed --universe or --backup-dir into that folder, Update 7 stops you. Singleplayer worlds are not affected: "Singleplayer runs, --help, --version and a --bare start without --bootstrap skip the check already."

To fix it properly:

Stop the server and read the code 11 message.
Create a server folder outside the launcher folder, for example C:\HytaleServer or /opt/hytale, and copy the Server folder and Assets.zip into it.
Copy the files the server wrote into its old working folder to the new Server folder: universe/, mods/, config.json, permissions.json, bans.json, whitelist.json and your backups. Copy auth.enc and auth.key too if they exist, since those are the files the manual's bootstrap install carries over to keep a server signed in. Otherwise, sign in again with /auth login device.
Start the server from the new Server folder, with --assets pointing at Assets.zip and any --universe, --prefab-cache or --backup-dir paths pointing at the new location. There is a Linux example below.
For a server you plan to keep, reinstall with the Hytale Downloader CLI or the --bootstrap install. The manual calls the downloader "Best for: Production servers", and both set up the folder layout the built-in updater needs.

cd /opt/hytale/Server
java -XX:AOTCache=HytaleServer.aot -jar HytaleServer.jar --assets ../Assets.zip

If you really want to run from the launcher folder, Update 7 added an --allow-install-dir flag, "mirrored by the hytale.allow_install_dir system property, for anyone who wants to run there anyway and accept the data loss risk."

java -jar HytaleServer.jar --assets Assets.zip --allow-install-dir

The notes don't say which value the system property expects, so use the flag. Don't use either on a world you care about: that folder is the one "every update patches or wipes".

One trap with the official start.sh and start.bat scripts: if the server exits with an error after the script applied an update (on Linux only within the first 30 seconds), the script prints "This may indicate the update failed to start correctly." and explains how to roll back from updater/backup/. With code 11 the cause is the folder check, not a broken update. Rolling back only puts you on the old build that Update 7 players cannot join, so move the folder instead.

Worlds upgrade on first load, so back up first

The Chapter I changelog says: "Saved worlds now take up less disk space than before. Existing worlds will upgrade themselves the first time they load." Each world upgrades the first time it loads on Update 7, with nothing for you to run.

Going back is the problem. For cubic worlds, which can extend above Y 320 and below Y 0, the modder notes are explicit: "BlockSection blobs moved to version 7. Older servers cannot read those blobs, so a world loaded on this version cannot be opened on an older one." For other worlds Hypixel does not say whether an Update 6 server can still read an upgraded save. Treat the upgrade as one way.

Before the first boot, stop the server and copy universe/ plus mods/, config.json, permissions.json, bans.json and whitelist.json to a place outside both the server folder and the launcher folder. Name the copy after the version /update status showed. The built-in updater can also back up before it applies an update (RunBackupBeforeUpdate is on by default but "requires backup directory to be configured"), but the copy you made by hand is the one to restore if something goes wrong.

Three more world changes:

Entities with block models from Update 5 worlds now keep their position and scale in the upgrade, but "This will not repair entities that were already upgraded with the wrong position and scale."
Worlds with a placed treasure chest still load, even though the treasure map objective was removed.
Portal worlds reached through TeleportInstanceInteraction are now deleted from disk when their timer reaches 0.

Plugins and mods after Update 7

Update 7 moves block reads and writes from whole chunk columns to chunk sections, which "skips the blocking chunk load and the old 0 to 320 height cap". That breaks a lot of plugin code, and the notes say more than once that a plugin using the removed methods "will not compile". A plugin built for Update 6 that touches these APIs needs a new build from its author. The changes most plugins will hit:

Removed or changed	Use instead
`TickProcedure.onTick` with `World` and `WorldChunk` parameters	It now takes a `CommandBuffer<ChunkStore>` and the section `Ref<ChunkStore>`. Get the world from `commandBuffer.getExternalData().getWorld()`
`IWorldChunks`, `IWorldChunksAsync`, `IChunkAccessorSync`, `ChunkAccessor`, `OverridableChunkAccessor`, `LocalCachedChunkAccessor`	Deleted. Read through the section from `ChunkStore.getChunkSectionReferenceAtBlock`
`WorldChunk.setBlock` and `WorldChunk.breakBlock`	`BlockOperations.setBlock` on the section ref
`ChunkFlag.TICKING`, `ChunkFlag.INIT`, `ChunkFlag.START_INIT`	Ticking is now the absence of the `NonTicking` component
`TargetUtil.getTargetBlock` and `getTargetLocation` with a `World`	Pass `world.getChunkStore()`
`ItemMergeSystem#RADIUS`	`ItemComponent#getMergeRadius(ComponentAccessor)` and `ItemComponent#setMergeRadius(float)`
`com.hypixel.hytale.protocol.DurabilityOperator`	`ComparisonOperator`
Rule flags on `ClientFeature`, such as `DisplayHealthBars` and `AllowBlockBreaking`	The `GameplayConfig` asset
`IsMajor` on the `ShowEventTitle` packet	An `EventTitleStyle Style` field

Some changes compile fine but behave differently. Event listeners now keep running when another listener throws. ValidateBlockEvent fires concurrently and off the world thread, "so a handler must not keep state between events". The new server-side Noesis UI methods start with dev_, and Hypixel says they "should not be used yet".

Asset packs need attention too, even without any Java code:

Five density node types were renamed, for example SmallerThan to LessThan, Select to Selector and Equals to Equal.
Spectre_Void is now Void_Spectre, and "anything pointing at the old ids no longer resolves".
With the treasure map objective removed, "any asset that names one fails to load".
The Food_Instant_Heal_T2, _T3 and _Bread effects and the Potion_Stamina_Cooldown effect are gone.
Encounter asset files "must now declare the top-level Class key".

Running a proxy or a custom server? A server "must now declare the true asset size in AssetInitialize", and the client disconnects one that sends more. The 0.7.2 API constants list ProtocolSettings.PROTOCOL_VERSION as 3 and PROTOCOL_BUILD_NUMBER as 258, but compatibility is checked on a hash, so match the build, not only the version number.

For an admin it comes down to three steps:

Check each plugin's download page for a build made for Update 7, and leave out any plugin that does not have one yet.
Look at the ServerVersion range each plugin or pack declares. The Update 5 notes give >=0.5.0 <0.6.0 and ^0.5.0 as example ranges, so a pack that declares ^0.6.0 does not claim 0.7 support. The server checks this field (Update 3), but the notes don't say whether it refuses an out of range pack or only warns.
Start once without players and read the log for anything that fails to load.

Server mods still go in the mods/ folder, as the manual describes. Our Mod Browser guide explains which mods belong on the server and which on the client.

Server fixes in Update 7, 0.7.1 and 0.7.2

Update 7 (12 October)

From the Chapter I changelog and the modder-facing notes:

A freshly started server no longer freezes when several players join at the same moment.
One player's connection can no longer break networking for everyone else on the server.
Servers close connections cleanly when they shut down, so players are not left waiting for a timeout.
A saved view distance above the limit no longer stops servers and worlds from starting: "This value is now capped at 32 chunks." A MaxViewRadius outside 1 to 32 in config.json is clamped in memory with a warning, and the file keeps what you wrote.
Chunk saves borrow their buffers from a bounded pool, "which is what stops busy servers from running past the direct memory limit".
World config and player save writes get their own pool of four threads, "so a world tick can no longer starve waiting on a save".
Bans and kicks close every connection the account has open, including Asset Editor connections.
/auth login browser and /auth login device now work while the server is already signed in.

0.7.1 (13 October)

Joining a world hosted on Windows "should no longer time out after 30 seconds just as you enter the world", on LAN and over the internet.
A player whose IP address changes during a session, for example from Wi-Fi to Ethernet, can reconnect right away. Before the fix, the server refused that reconnect as "already logged in".
Going through a portal while your arrow or kunai is still in flight no longer disconnects you.
Spawn markers no longer fail to spawn large NPCs that have enough room to stand, and a marker with an invalid search range now logs a warning and is disabled.

0.7.2 (14 October)

"Fixed a world crash that disconnected every player in the world. It happened when a cave chunk loaded with an old goblin spawn beacon from Update 6 and goblins it had spawned." Worlds that were played on Update 6 are the ones exposed.
"Fixed a crash on Linux in worlds that use RocksDB chunk storage."
The Zone1_Plains1 region instance loads in the released game again.

To see whether a world uses RocksDB, open config.json in its folder under universe/worlds/ and look at ChunkStorage. The manual's example world shows "Type": "Hytale" there. If yours names RocksDB and the server runs on Linux, 0.7.2 is the build you need. RocksDB storage is built into the server (the 0.7.2 API reference lists a RocksDbChunkStorageProvider), so this is not a mod problem.

Commands that changed

/portal can now be used instead of /fragment, and /leave is replaced by /portal leave.
/cursethis is now /ephemeral.
/eventtitle takes --style in place of --major.
/worldevent enable switches world events on or off per world, and new Creative worlds start with them off.
The max view radius command now rejects anything above 32, instead of 512.

Update any scripts or bots that still send the old commands.

Update checklist

Run /update status and note the version. If AutoApplyMode in config.json is WhenEmpty or Scheduled, the server may already have updated itself and upgraded the world.
Check every plugin and pack for an Update 7 build, and decide what to leave out.
Tell your players when the server goes down, and that they need to restart the launcher to get 0.7.2.
With the built-in updater, run /update download while the server still runs, so the new build is staged.
Stop the server cleanly.
Copy universe/, mods/, config.json, permissions.json, bans.json and whitelist.json to a folder outside the server and launcher folders.
Check that the working folder and any --universe, --prefab-cache and --backup-dir paths are outside the launcher's install folder.
Swap the plugins in mods/ for their Update 7 builds, or take them out.
Check MaxViewRadius in config.json. Values above 32 are clamped, and the manual recommends 12 chunks (384 blocks) because view distance is the main driver of RAM use. Our RAM guide has the sizing table.
Put 0.7.2 in place and start the server with nobody online. With the wrapper scripts, starting start.sh or start.bat applies the staged build. Without them, download it with ./hytale-downloader or copy a fresh Server folder and Assets.zip from an updated launcher.
Watch the console for exit code 11, plugins that fail to load and the world upgrade.
Join with an updated client, place and break blocks, use a portal, restart and check that your changes were saved. Then open up, and keep the pre-update copy until the world has run on 0.7.2 for a while.

Hosting it with us

Our Hytale server hosting runs in nine regions: the Netherlands, Germany, Poland, Canada, USA (California), USA (Virginia), Singapore, India and Australia. Plans go from €4.00 a month for 4 GB of RAM and 20 GB of NVMe storage to €11.80 for 12 GB and 50 GB, with DDoS protection on every plan. You get full access to the server files, so you can copy universe/ before the update, swap plugin builds in mods/ and edit config.json yourself. If the world outgrows its tier, move up and your files come with you. Our support team is online from 08:00 to 20:00 UTC, seven days a week.

FAQ

What does exit code 11 mean on a Hytale server? Since Update 7 the server refuses to boot when its working folder, --universe, --prefab-cache or --backup-dir sits inside the Hytale launcher's install folder. It prints how to move them and exits with code 11. Move the server to a folder of its own, or add --allow-install-dir if you accept the risk of losing data.

Why can't players join my Hytale server after Chapter I? Usually because the server and the players are on different builds. Client and server must be on the exact same protocol version, so update the server to 0.7.2 and have players restart the launcher. Hypixel has not published the exact text of the mismatch message.

Can I go back to Update 6 after my world loaded on Chapter I? Not with an upgraded cubic world, which an older server cannot open. Hypixel does not say whether other worlds can go back, so restore the copy you made before the first boot on Update 7. Update 7 players cannot join an Update 6 server anyway.

Do I need 0.7.2, or is 0.7.1 enough? Use 0.7.2. It fixes a Linux crash in worlds with RocksDB chunk storage and a world crash that disconnected every player, and it is the current release on Hypixel's documentation site.

Do my plugins still work after Update 7? Many need a new build. Update 7 removed the old chunk accessor classes and changed TickProcedure.onTick, among others, and plugins that use removed methods will not compile. Install builds made for Update 7 and read the first boot log.