Hi Hytaler,
Chapter I: Out of the Breach went live on October 12. Everyone is talking about goblins, runestones and the Deepworks dungeon, fair enough. If you run a server though, the patch notes have a few lines that decide whether your players can join at all on day one. Same drill as with Update 6 for server owners, here's the server side boiled down.
1. Client and server have to match again
The protocol version got bumped and a bunch of packets changed their wire layout (
UpdateBossBar, ItemMovementSettings, ShowEventTitle and more). In plain words: a player on the new client can't join a server still on the Update 6 build. Update the server first, then tell people to update.If you run plugins, they need a rebuild against the new server jar too. Don't just drop the old jars back in and hope.
2. Plugin devs: the chunk/block API got gutted
This is the big one for modders. A long list of block and chunk accessors is gone, including
ChunkAccessor, IChunkAccessorSync, IWorldChunks, WorldChunk.breakBlock, WorldChunk.setTicking and several setBlock/getBlockType overloads. The replacement path is ChunkStore.getChunkSectionReferenceAtBlock together with BlockOperations.setBlock or BlockSection.Ticking also works differently now: there's no
ChunkFlag.TICKING anymore, a section ticks when it does NOT have the NonTicking component. If your plugin touches blocks at all, expect compile errors, not just warnings.A few renames that bite in asset packs:
Spectre_Void → Void_Spectre, Goblin_Miner → Goblin_Brave, density types like SmallerThan → LessThan, and the damage sensor Friendly flag had its logic inverted. Full list is in the modder-facing notes.3. Back up before the first boot on Update 7
Cubic worlds are now saved as
BlockSection blob version 7, and older servers can't open worlds saved that way. Existing worlds get upgraded automatically on load, which is nice, but it's also a one-way door. Copy universe/ (plus your JSON configs and mods/) somewhere safe before you start the new build. If you need a quick way to do that, the backup generator spits out a script for Linux or Windows.4. New boot check: don't run the server from the launcher folder
There's a new safety check. If the server's writable paths (working dir,
--universe, --prefab-cache, --backup-dir) sit inside the launcher install folder, it refuses to boot with exit code 11. You can override it with --allow-install-dir (or the hytale.allow_install_dir system property), but honestly, just give the server its own directory. If your server "suddenly won't start" after the update and you see exit code 11, this is why.5. View distance is capped at 32
MaxViewRadius outside 1–32 no longer blocks boot. It gets clamped in memory with a warning and your config file stays as it is. The command that sets view radius now rejects anything above 32 (it used to accept up to 512). If you had a silly high value in there, you'll see the warning in the log. Not a problem, just don't be surprised. The RAM calculator still assumes view distance is the biggest RAM driver, which hasn't changed.6. Small things that are actually nice
- Server rule changes apply immediately, players don't need to rejoin.
- Servers close connections cleanly on shutdown.
- A freeze when several players joined at the same time is fixed, and so is a bug where one player's broken connection could mess up networking for others.
- Chunk saves and document writes run on their own pool now, so saves compete less with world ticks.
- Bans and kicks now close all connections of that account, including Asset Editor connections.
/auth login browser|deviceworks while already signed in, which helps if your auth expired on a running server./cursethisis now/ephemeral, in case you had it in scripts.
7. Run 0.7.2, not 0.7.0
Two hotfixes already landed:
- 0.7.1 (Oct 13): joining a world hosted on Windows timed out after 30 seconds, fixed. Reconnect after an IP change (Wi-Fi → cable) no longer gets rejected as "already logged in".
- 0.7.2 (Oct 14): fixed a world crash that disconnected everyone when a cave chunk loaded an old goblin spawn beacon from Update 6. Also a Linux crash in worlds using RocksDB chunk storage.
That 0.7.2 crash is exactly the kind of thing that hits worlds created before the update, so if you're on an older world, update to 0.7.2 before you open the doors. Hotfix notes.
If your server won't come up after the update, open a thread in Help & Troubleshooting with the last ~30 lines of the log and your start command. And if you've already moved a big world over, tell me how it went below, especially how long the first boot took with the world upgrade.
Read next
Last edited: