Hytale Chapter 1: What Changes for Server Owners

Hytale Chapter 1, “Out of the Breach,” released today. It’s also Update 7, the build that ran through five weekly pre-release parts in September and October. Most of the attention is on the goblins, the Gobliterator dungeon, and Rune abilities, but several changes in this update affect anyone running a server: a world save upgrade, plugin API breaks, a hard cap on view distance, and some command changes.

Here’s what changed on the server side and what to do before your first Chapter 1 start.

Update the Server and Every Client Together

Chapter 1 changes the network protocol. Hypixel’s notes are direct about it: clients and servers have to be on matching protocol versions. A server still on Update 6 can’t accept Chapter 1 clients, and a Chapter 1 server can’t accept players who haven’t updated.

In practice that means updating the server as soon as your group updates, then making sure everyone has the new version installed through the Hytale launcher. If one player can’t connect while everyone else can, an outdated client is the first thing to check.

WinterNode’s Hytale server hosting pulls the latest game files every time the server starts, so a restart is usually all the server side needs. Our Hytale server update guide covers what to do if it doesn’t pick up the new version.

Back Up Before the First Start

Chapter 1 changes the world save format. Saved worlds now take up less disk space, and existing worlds upgrade themselves the first time they load on the new version. You don’t need to do anything to trigger it.

The catch is that you may not be able to go back. In the plugin developer notes, Hypixel says cubic worlds moved to a new block data format and that “a world loaded on this version cannot be opened on an older one.” The notes don’t say whether other worlds can still open on Update 6 after upgrading, so treat the upgrade as one-way. If a mod you depend on isn’t ready and you want to wait on Update 6, start from a backup, not the upgraded world.

The same applies to singleplayer worlds. If you open an old save in the Chapter 1 client before you upload it to your server, expect it to be upgraded already. Keep the original copy until you’ve confirmed it loads.

Check Your Mods Before You Update

This is the change most likely to stop a server from starting. Update 7 removed or changed a long list of server plugin APIs, including:

• TickProcedure.onTick now takes a CommandBuffer<ChunkStore>
• WorldChunk no longer holds a World
• ChunkAccessor.performBlockUpdate and WorldChunk.setTicking are gone
• DurabilityOperator was renamed to ComparisonOperator
• World.validate was replaced by ChunkStorageValidator

You don’t need to know what any of those do. What matters is that plugins compiled against Update 6 that use these APIs can fail to load or break at runtime until their authors publish a Chapter 1 build. Check asset packs too, especially anything that adds blocks or items.

Before you update a modded server:

1. List every mod in your mods/ folder
2. Check each one’s CurseForge or GitHub page for a Chapter 1 or Update 7 release
3. Update the ones that have it. The Plugin Browser can check all of them at once
4. Hold off on updating the server if a mod your world depends on isn’t ready yet

If a mod adds blocks to your world and you remove it to get the server running, those blocks can show up as unknown or disappear. Test on a copy of the world first.

Performance Changes and the View Distance Cap

Chapter 1 includes several server-side performance improvements. Busy servers should see a difference without any configuration:

• Ticking blocks, fluids, and farmland costs less in busy areas
• World data is compressed more efficiently when saved, which lowers memory use
• Blocks, fluids, and creatures far above or below players pause until a player gets close
• Distant creatures scan for opponents less often
• Chunk saves no longer exceed the direct memory limit on busy servers, and a world tick can no longer stall waiting on a save

View distance now has a hard cap of 32 chunks. Before Chapter 1, a MaxViewRadius above the allowed limit in config.json stopped the server from booting. Now the server clamps it to 32, logs a warning, and starts anyway. The file keeps whatever value you wrote. The max view radius command also rejects anything above 32, down from 512.

For most servers, 32 is still far more than you want. View distance is the biggest factor in both RAM and CPU load, and 12 chunks is a good starting point for most servers. Our Hytale server performance guide covers how to change it, and the Hytale RAM guide explains how view distance and player count affect memory.

Command and Admin Changes

A few commands changed names or behavior:

Change	What to use now
/fragment	/portal can now be used instead
/leave	Replaced by /portal leave
New command	/worldevent toggles World Events on or off
Max view radius command	Rejects values above 32
/kit iron and /kit adamantite	Now include food and health potions matching their tier

Other admin-facing changes:

• Bans and kicks now close every connection an account has open
• Server rule changes now affect players immediately
• Shutdowns close player connections cleanly instead of leaving them to time out
• /auth login browser and /auth login device can now be run while the server is already signed in. The current session stays active until the new sign-in succeeds
• World Events can be turned off in custom world settings, alongside the /worldevent command

Hypixel’s notes don’t say outright whether Goblin Breaches count as a World Event for these toggles. If you want to run a server without Breaches, test the toggle on a copy of your world before relying on it.

If You Self-Host

One change only applies if you run the server yourself. The server now refuses to boot if the data it writes would land inside the Hytale launcher’s install folder. It exits with code 11 and prints steps to move the data. You can override the check with --allow-install-dir, but moving the server to its own folder is the better fix.

This doesn’t affect hosted servers, including WinterNode’s.

What Your Players Will Notice

You’ll get questions about the gameplay changes, so here’s the short version:

• Goblin Breaches start after a few in-game nights pass, or after players investigate a disturbance at the Forgotten Temple
• The Gobliterator is Hytale’s first handcrafted dungeon and multi-phase boss fight
• Rune abilities slot into a Runebinder’s Lattice, with up to two Ability Runestones plus Modifiers. Abilities use Mana, which now shows where the Stamina bar used to be
• Throwable barrels and transparent glass in Lost Civilization, Kweebec, Tavern, and Wind Temple windows
• Mods can contain whole worlds, which show up in the world list once installed, and a Minigames tab is coming to the Mod Browser

Chapter 1 Update Checklist

1. Check every mod for a Chapter 1 build, and wait if a critical one isn’t ready
2. Stop the server and back up the universe/ folder
3. Update the server
4. Start it and watch the console for mod errors and the world upgrade
5. Confirm every player has updated through the launcher
6. Set MaxViewRadius in config.json to what your plan can handle. 12 is a good starting point

---

The world upgrade means Chapter 1 is worth ten minutes of preparation instead of restarting and hoping. WinterNode Hytale servers update on restart, come with Performance Saver already installed, and are backed up automatically twice a day with 45-day retention, so the main thing left for you is checking your mods.

Get your Hytale server →

Questions about updating or a mod that won’t load after Chapter 1? Open a ticket or find us on Discord.