Hytale Chapter 1 Server Preparation: A Dated Checklist for the Two Weeks Before October 12, 2026

Hytale Chapter 1 releases on October 12, 2026. That is fourteen days from today, and if you run a server you are planning an upgrade that nobody has published instructions for. This guide takes the one technical record that exists, the living pre-release patch notes for Update 7, and turns the parts that affect a server into a dated checklist. Where the notes say something, this article quotes it. Where they say nothing, this article says nothing. Read This First: Which Build Any of This Describes Everything technical below comes from the pre-release channel, build 0.7.0-pre.4. The stable documentation channel still pins Release 0.6.8, which is what most servers run right now and which contains none of it. Three things follow, and they matter more than any individual checklist item: Hytale has not published an Update 7 stable release note, and there is no "HOTFIXES: UPDATE 7" page: that URL returns a 404, and the live hotfix page is still the Update 6 one, topping out at 0.6.6 dated 14 September. Hytale has not published a Chapter 1 server migration guide, nor any statement that Chapter 1 ships as Update 7 stable. This article invents no version number for the Chapter 1 build, and you should be suspicious of anyone who quotes you one. Pre-release notes describe a moving target. The Update 7 page has grown in four parts through September and can grow again. Treat what follows as a preparation document, not an upgrade script. Our write-up of the 0.6.8 docs version covers the channel split, and our pre-release testing guide covers getting onto pre-release in the first place. The Short Version Back up before you touch anything, and keep the backup off the machine. Part 3 documents a one-way world upgrade: "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." Yes, plugins will break. Part 4 alone marks the whole legacy chunk read surface @RestrictedApi and deletes the last of the old write methods. Assets break too, and more quietly. Several JSON keys stopped decoding, which is a load failure rather than a compile failure. Client and server must match. Three separate protocol changes across Parts 1, 2 and 3 say so in different words. Chapter 1 content is partly undocumented on purpose, and nobody here has tested any of this on a live server. This is a careful reading of patch notes, not a field report. The One Fact That Makes Backups Non Negotiable Read one line from all of Update 7, and make it this one, from Part 3, dated September 17, 2026: Cubic worlds now use a new tree heightmap, and 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. That is a one-way door: once a world has been loaded on the new build, the old build cannot open it again. Part 3 adds the player-facing half of the same change: "Saved worlds now take up less disk space than before. Existing worlds will upgrade themselves the first time they load." The upgrade is automatic and it happens on load. There is no documented flag to defer it, no dry run and no downgrade, so the rollback plan cannot be "load the old build again". It has to be a copy of the world directory taken while the server was stopped, somewhere the upgrade never touched. Part 1 has a related detail: the server now refuses to boot when the content it writes would land inside the launcher's install folder, a check covering the working directory plus --universe, --prefab-cache and --backup-dir, exiting with code 11. If your backup directory sits there, the launcher has been a risk to your backups all along. Our guide to land claims, rollback and backups covers what makes a backup actually restorable. Will My Hytale Mods Break in Chapter 1? For anything that compiles against the server, the honest answer is probably, and loudly. The chunk access surface has been rebuilt across all four parts, and Part 4 is where the deprecations turn into build failures: WorldChunk.getBlock, BlockChunk.getBlock, World.getBlock and World.getBlockType are now @RestrictedApi, so a plugin that still calls them fails the Error Prone build. Read BlockSection.get on the BlockSection component of the section ref instead. Nine legacy column accessors go the same way. A plugin that still calls getBlockChunk, getFiller, getRotationIndex, getHeightmapColumn, getFluidLevel, getSupportValue, setState or setEnvironmentRange no longer compiles if errorprone is used, and the replacement in every case is the BlockSection component of the section ref from ChunkStore.getChunkSectionReferenceAtBlock. Writes moved too. Part 4 removed WorldChunk.breakBlock, IChunkAccessorSync.breakBlock, BlockChunk.getEnvironment(Vector3i), IChunkAccessorSync.setBlockInteractionState and the last WorldChunk.setBlock overloads. Block writes go through BlockOperations on the section ref instead, which the notes say skips the blocking chunk load and the old 0 to 320 height cap. Three more that catch specific plugins: Chunk storage providers "now take a readOnly flag on initialize and have to answer hasStoredChunks, and a cubic IChunkLoader has to implement forEachSection." A provider that cannot open read only should reject the flag rather than open writable. Validation moved. World.validate and WorldValidationUtil are gone in favour of ChunkStorageValidator, and ValidateBlockEvent moved to BlockValidator, where it "fires for chunk validation too, concurrently and off the world thread, so a handler must not keep state between events." That last clause is a correctness bug waiting to happen in any handler written against the old single-threaded assumption. The deprecated lookups are closed. IChunkAccessorSync.getChunk, getChunkIfInMemory, getChunkIfLoaded and every way to build a LocalCachedChunkAccessor carry @RestrictedApi. Resolve the column with ChunkStore.getChunkReference instead. Earlier parts are the same shape. Part 2 removed WorldChunk.getWorld() and moved block health onto the chunk section; Part 1 removed ChunkAccessor.performBlockUpdate and WorldChunk.setTicking and stripped nine fields off ClientFeature, noting that "a plugin naming one of them stops compiling". Our breakdown of the Update 7 server plugin breaking changes covers the first wave in more depth. The practical consequence: if you depend on a plugin you did not write, ask its author this week whether it has been built against 0.7.0-pre.4. The Breakages That Are Not Java Compile failures are the loud kind. The quieter kind is an asset that stops decoding, which surfaces as a pack failing to load rather than as a red build. Audio timing keys no longer decode in their old spelling. Part 3 turns StateTransition.DurationMs: 2000 into Duration: { "Ms": 2000 } and AudioState.DefaultSyncTo: "NextBar" into DefaultSyncTo: { "Point": "NextBar" }, and the MusicTransition fade fields each take an object instead of a number of seconds. Encounter asset files must declare a top-level Class key as of Part 3. Role files can still leave it out. The treasure map objective is gone as of Part 1, along with the TreasureMap task, the OpenTreasureContainer and DestroyTreasureCondition interactions and the TreasureChest block entity component. Any asset that names one fails to load, though a world with a placed treasure chest still loads because the server keeps the component as unknown data. Density asset types were renamed in Part 1: SmallerThan is now LessThan, Select is now Selector, Equals is now Equal and GreaterOrEquals is now GreaterOrEqual. Part 3 renamed the portal curse surface too, so CursedItems became EphemeralItems and /cursethis is now /ephemeral. Food model nodes were rebuilt in Part 3, and the notes warn that "custom animations that reference the old node names may break". Texture atlas overflow changed failure mode. Part 3 says custom content that overflows an atlas now falls back to the missing texture and logs a warning instead of vanishing without a word, and atlases pack across several pages, up to 16 for the block atlas and 4 for the others. Our write-up of the atlas limit covers what that warning means. A magenta block beats an invisible one, but catch it in staging. Protocol: Client and Server Have to Match Three parts say the same thing three ways, which is usually a sign it is going to bite somebody. Part 1 bumped the protocol version for UpdateLanguage.Language becoming a required field, and added the WorldGameplayConfig packet. Part 2 is blunt about it: ItemMovementSettings gained a trailing ExtraJumpLocalSoundEventIndex, "which changes its wire layout. The client and the server have to be built from the same protocol build." Part 3 restructured environment streaming so SetChunkEnvironments is keyed to section coordinates, then states: "Clients and servers have to be on matching protocol versions." Part 4 adds one that is specifically a server operator problem: A server must now declare the true asset size in AssetInitialize. The client disconnects a server that sends more bytes than it declared, and a single asset is capped at 256 MiB. The declared size is the server's job to get right, which matters for anything custom in your asset pipeline, and the 256 MiB per asset cap is a hard ceiling a very large custom asset could now hit. The operational shape: the day Chapter 1 lands, players on the new client cannot join a server still on the old build, and the reverse is equally true. Say that in your Discord before the day rather than during it, because launch day connection problems are hard enough to triage without a version mismatch in the mix. The double NAT write-up is a reminder of how much support traffic one connectivity issue generates. The Chapter 1 Content Your Server Will Host Hytale's official Chapter 1 page describes the world event you will be hosting: Once you answer the chapter's opening call and set things in motion at the Forgotten Temple, the new Goblin Breach world event can trigger from time to time, creating a temporary portal somewhere in your world. Look around or open the world map to locate it, then step through. You'll appear in an unstable fragment of Orbis, a set of biomes taken over by the Goblins, along with a growing Void presence. And inside: This world gets regenerated every time you enter, sometimes with content you haven't seen yet on your previous visits. While you're inside, the Void presses in and will eventually eject you back out to your world. That is a description of behaviour, and it is the whole public record. No source documents how a server configures the Goblin Breach, whether it can be disabled, rate limited or restricted to particular worlds. The server-side configuration surface is not documented anywhere this article could verify, and this article will not guess at it. The closest documented lever is the general world events toggle added in Part 4: /worldevent enable takes true or false and the WorldEvents plugin stores an EnableWorldEvents flag in a new WorldEventsWorldConfig. Whether that flag governs the Goblin Breach specifically is not stated. Our world events configuration guide covers the documented surface in full, and our Chapter 1 first look covers what has been shown publicly. Part 4's own introduction is candid that you cannot plan around all of it: "A lot of what you'll encounter in this second wave deliberately isn't mentioned in these patch notes, so you'll have to experience it for yourself!" The Fourteen Day Checklist: September 28 to October 12 The dates below are this site's recommendation built on the documented behaviour above, not official guidance: Hytale has published no schedule and no recommended cadence. Compress it for a small world, spread it out for a large one. Monday 28 to Wednesday 30 September: know what you have Write down your current build and whether it is stable or pre-release. Half the notes above are meaningless on 0.6.8. Inventory every plugin and pack, with the author and whether you can rebuild it yourself. The ones you cannot rebuild are your real risk list, and this is the week to ask those authors about 0.7.0-pre.4. Two weeks is enough notice for a maintained plugin and not enough for an abandoned one, which is useful to learn now. Take a full cold backup, server stopped, world directory copied off the machine, and check your backup directory is not somewhere launcher updates wipe. Thursday 1 to Saturday 3 October: stand up a staging copy Build a staging server on the pre-release channel from a copy of your world, never the live one, because of the one-way BlockSection version 7 upgrade. Let the world upgrade there and watch the log. This is the only rehearsal you get. Compile your own plugins against the pre-release build and work through the Error Prone failures. Each has a documented replacement in the Part 4 list above. Load every asset pack on staging and read the warnings, particularly atlas overflow, encounter Class keys and audio timing keys. Sunday 4 to Wednesday 7 October: fix, then test like a player Port the chunk calls to ChunkStore.getChunkSectionReferenceAtBlock plus BlockSection for reads and BlockOperations for writes, and audit any ValidateBlockEvent handler for shared state. Actually play on staging. Join, build, break, die, respawn, cross a portal, run your server's core loop. A clean compile is not a working server. Re-check MaxViewRadius. Part 1 clamps a value outside 1 to 32 in memory with a warning rather than refusing to boot, and the command now rejects anything above 32. Our write-up covers the setting properly. Thursday 8 to Sunday 11 October: freeze, communicate, confirm Freeze changes, so the list of possible causes on launch day stays short. Tell your players they will need the matching client build, which the protocol changes across Parts 1, 2 and 3 make unavoidable. Take a second cold backup and verify it by restoring it somewhere, not by looking at the file size. Keep it off the server's disk. Write the rollback decision in advance: what has to be true to restore, who calls it, how long you wait. Nobody decides that well at midnight. Re-read the Update 7 notes on the eleventh and post a maintenance window. Monday 12 October: launch day Stop the server cleanly, copy the world, then update, in that order and with no shortcuts on the middle step. Bring it up private first and read the log before you open it, watching for asset decode errors, atlas warnings, plugin load failures, protocol mismatch disconnects and anything naming chunk storage or validation. Keep one admin off building duty to answer the "I can't connect" messages, which will mostly be version mismatch. Do not delete the backup for a fortnight. The bugs you find on day four are the reason it exists. Our Update 6 launch day checklist covers how the last one actually went, which is a better guide to the hours themselves than anything written in advance. What Is Not Documented Yet There is no Chapter 1 server migration guide, no Update 7 stable release note and no "HOTFIXES: UPDATE 7" page: that URL is a 404 and the live hotfix page still tops out at 0.6.6. This article is not a substitute for any of them. There is no published version number for the Chapter 1 build. Hytale has not stated that Chapter 1 ships as Update 7 stable, and this article deliberately does not assert it. Everything technical here is pre-release, build 0.7.0-pre.4, against a stable channel still pinned to 0.6.8. Any of it can change before October 12. The Goblin Breach has no documented server configuration. No source says whether it can be disabled, rate limited or restricted per world. The behaviour quoted above is the entire public record. There is no documented deferral or downgrade for the world upgrade, no documented auto-update mechanism for servers, no stated update ordering and no stated maintenance window. If you need one, you are inventing it, as this checklist openly does. Nobody here has tested any of this on a live server. This article is a reading of published patch notes and one official Chapter 1 page, not a report from a running Hytale server, and the checklist is opinion built on documented behaviour rather than experience of this upgrade. The Bottom Line Two weeks is enough time, but only if you spend the first of them finding out what breaks rather than the second. The documented risks are unusually concrete for a pre-release: a world format that moves one way and does not move back, a chunk API that fails builds rather than warning about them, asset keys that stopped decoding, and a protocol that will not tolerate a mismatched client. The undocumented risks are equally real and there is nothing useful to say about them, which is why the staging copy and the cold backup are worth doing even if you skip everything else on this list. The date is settled: Chapter 1 releases on October 12, 2026, and our coverage of Part 4 is the closest thing to a preview of the build. Getting a server ready for the twelfth? List it on HytaleCharts so players can find it the day Chapter 1 goes live.