Hytale Update 7 Part 3 Patch Notes: A One-Way World Format Change, the Texture Atlas Fix We Said Had No Date, and a Debug Overlay You Can Finally Rearrange

Hytale added a third section to its Update 7 pre-release patch notes on 17 September 2026, and nothing announced it. No new post appeared on the news index. No new byline appeared on the page. The heading "Pre-Release (Update 7 Part 3)" was simply appended to the top of the same living document that has carried Part 1 since 3 September, under an intro that still says: "Below you will find the pre-release patch notes for Update 7, which we will update weekly!" We checked the page directly on the morning of 18 September: three parts exist, dated 17 September, 10 September and 3 September, the byline still reads "Posted by Hytale Team September 3, 2026", and hytale.com/news still lists the 3 September post as its newest entry. There is no Part 4. The Short Version of Hytale Update 7 Part 3 There is a one-way world format change. The notes state it plainly: "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." Back up first. The texture atlas ceiling finally has a fix with a date on it. Overflowing content now falls back to the missing texture and logs a warning, and atlases pack across multiple pages. Clients and servers must match protocol versions again. Environments now stream per chunk section, and SetColumn no longer carries them at all. Several asset schema spellings stop decoding, including the audio timing keys, and Encounter asset files must now declare a top-level Class key. The F7 debug overlay was rebuilt into movable, resizable, hideable panels with saveable layouts. Part 3 carries no version number. It is not labelled 0.7.0-pre.3 anywhere, and when we checked, pre-release.docs.hytale.com still pinned 0.7.0-pre.2 while docs.hytale.com still pinned Release 0.6.6. On the stable branch the newest hotfix remains 0.6.6 from 14 September, covered in our 0.6.6 joining and connecting write up. There is no 0.6.7. Why the Hytale Update 7 Part 3 Patch Notes Went Unnoticed This is now a pattern rather than an accident. Part 1 arrived as a normal news post on 3 September, covered in our Update 7 Part 1 breakdown. Part 2 was appended silently on 10 September, as we noted in our Update 7 Part 2 write up, and Part 3 repeated it exactly. The practical consequence for anyone running a Hytale server is that the news index will not tell you when a breaking change has shipped. The only reliable signal is the patch notes page itself, and Part 3 contains a world format change that cannot be undone. Part 3 does open with something the earlier parts did not. It credits contributors by name: A huge thank you to tssan1ty, NoctuaAstrum and Fullavatar for the fixes, features, and polish they've brought to this update. Your community contributions make Hytale better for everyone! Back Up Your World Before Loading Hytale Update 7 Part 3 This is the section to act on. Under "For Plugin Developers", Part 3 states: 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. Read that last clause twice. It is not "may cause problems" or "is not recommended". Loading a world on this build upgrades it, and the upgrade is one directional. Two Performance entries describe the same migration from the player side: "Saved worlds now take up less disk space than before. Existing worlds will upgrade themselves the first time they load", and "Improved how servers compress world data as it's saved, which lowers memory use on busy servers." Smaller saves are the reward. The automatic upgrade is the price. So the checklist before you touch Part 3 with anything you care about is short and non-negotiable. Take a full copy of the world directory while the server is stopped, and store it somewhere the test server cannot reach. Test on a copy, never the original. A world that has been opened once on Part 3 is a Part 3 world permanently. Update clients and servers together. Part 3 says "Clients and servers have to be on matching protocol versions", so a staggered rollout will simply fail to connect. Read the asset schema section before restarting your content pipeline, because several old key spellings no longer decode at all. If you maintain plugins, the wider migration picture is in our Update 7 server and plugin breaking changes guide, and Part 3 layers on top of it. The Texture Atlas Fix: An Update to Our 16 September Report On 16 September we published a piece on the texture atlas limit causing missing textures on modded servers. In it we stated that the live Update 7 notes contained zero occurrences of the word "atlas" and that the fix therefore had no date attached to it. That was accurate when we wrote it. It stopped being accurate the following day. Part 3 addresses it twice. Under Graphics & Rendering Fixes: Fixed an issue where missing or wrong textures could occur on worlds with a lot of custom content due to the texture atlas being full. And under Asset Schemas & Formats, with the detail modders actually need: Custom content that overflows a texture atlas now falls back to the missing texture and logs a warning instead of vanishing without a word. Atlases also pack across several pages, up to 16 for the block atlas and 4 for the others. So the fix we said had no date now has one: 17 September 2026. Be precise about what it is and is not, because this is the kind of entry that gets over-read. The notes do not say the ceiling is removed. They say atlases pack across several pages, up to 16 for the block atlas and 4 for the others. That is a much higher ceiling. It is still a ceiling. The notes do not mention Vulkan or OpenGL. Neither word appears, and no developer is named against the line. The diagnostic half may matter more than the capacity half. Content that overflows used to disappear silently. Now it renders as the missing texture and writes a warning to the log, which turns an unexplainable bug report into a grep. What Players Get in the Hytale Update 7 Part 3 Pre-Release NPCs and entities. "Some creatures must now be defeated in combat before you gain their Memories", which turns Memory collection from an exploration activity into a combat one for part of the roster. Feastmasters "will now animate climbing, swimming, diving, flying, spawning, and sleeping", and the Skeleton Elite got a faster Flowing Slashes attack plus "a new set of sounds". World, items and interactions. "Portal worlds can now remain open without a time limit." "Explosive Barrels are now thrown using the primary input. This is left click by default." The Scrap Glider model was reworked with a new idle animation, and Windwillow Fruit particles were reworked. There is also a rune change that is small in wording and helpful in practice: "Runes have now been renamed to make it clear whether they're Ability Runes or Modifier Runes." That split has been central to the system since it was first shown, as our explainer on ability and modifier runes covers, and it is the same framing a co-founder used when asking for community ideas, in our piece on boss abilities as player runes. The fix list has personality. Two entries are written with a straight face and are not jokes: "Environmental damaging effects have decided pacifism isn't for them and will once again deal damage", and "Inter-species relations have broken down and large predators will now attack spiders on sight". Goblins "have gotten better at running from Void-aligned creatures", continuing the Goblin and Void thread from Part 2. Elsewhere: Ground Slam now works with Battleaxes, the Scrap Glider no longer grants height from repeated jumping, and NPCs "will now successfully find solid ground in worlds where the terrain sits outside of the old fixed height range". Portal Device destinations now "adhere to the world settings selected when the original world was created, such as those related to fall damage and PvP". Commands and Naming: Two Sections New to Update 7 Part 3 is the first part of Update 7 to carry a Commands section at all. It has one entry: The /kit iron and /kit adamantite commands now include food and health potions matching their tier. Neither grants longswords, one-handed axes, clubs, spears, or staves. It is also the first part with a Naming & Categorization section, which standardises three names: "Web Rope" becomes "Spiderweb Rope", "Spider Web - Diagonal" becomes "Spiderweb Rope - Diagonal", and "Large Kenolite Stalactite" becomes "Kenolite Stalactite - Large". The last one is the tell: moving the size qualifier to the end is how you group variants in a sorted list. The Rebuilt Debug Overlay and Quality of Life Changes The debug overlay that appears when F7 is pressed twice has been rebuilt. Panels may be individually moved, resized, or hidden, and custom layouts can be created to switch between them. A matching fix notes that choosing a layout, layout hotkey or panel "will now take effect right away". The "Return to Crossroads" button in Creative Worlds was moved, trigger volume Play Sound settings "now show proper Volume and Pitch labels rather than raw text ids", and a number of typographical errors were fixed. Server owners get a related lever. Adding PreventDebugScreens.INSTANCE to a player entity "blocks the ToggleDebugScreens keybind (F7 by default) and closes any debug screen that is already open". The component "is runtime only and does not persist across a reload", so apply it on join. Stability, Localization and Performance Fixes The stability list is the longest single fix block in Part 3, and most of it is the unglamorous kind that decides whether people stay on your server: sign-in failing on macOS when Hytale was launched from Finder, Spotlight or Apple Games; a crash on Windows when antivirus software interrupted a world being saved; a crash from an incorrect or oversized invite code; a client memory leak when joining a world and another after a world map had been drawn; a two second freeze when leaving a peer-to-peer session; and a random crash on the main menu or inventory screens on machines with integrated Intel graphics. Performance adds "Fixed a freeze that could occur when someone joined a brand new world." Localization contributes one that affects a large slice of the player base: "Hytale will no longer fall back to English when your system language includes a regional variant, such as French (Canada)." Asset Schema Changes That Stop Decoding Trigger volume sound. PlaySound effects "now take VolumeDb in decibels from -100 to 0 and PitchSemitones in semitones from -60 to 12, instead of the old linear Volume and Pitch". The old keys "still load from existing JSON, but they no longer appear as rows in the trigger volume editor". There is a design decision in the range: "Volume is capped at 0 dB, so a trigger can only quiet a sound and never boost it. To make something louder, raise the volume on the sound event itself." Audio timing. This one does break: "Audio timing now speaks one vocabulary, and the old spellings no longer decode." Concretely, StateTransition.DurationMs: 2000 becomes Duration: { "Ms": 2000 }, AudioState.DefaultSyncTo: "NextBar" becomes DefaultSyncTo: { "Point": "NextBar" }, and MusicTransition.FadeOutDuration, FadeOutDelay and FadeInDuration "each take an object instead of a number of seconds". If your pack ships custom music transitions, that is a required edit. Encounters. "Encounter asset files must now declare the top-level Class key. Role files can still leave it out and fall back to Role." Everything else. BreachAtSeconds was removed from the portal VoidEvent config, leaving the Stages list to drive the escalation. World map markers gained an IconSize of Default or Major. Blocks can show their own name and description in game via "Page": { "Id": "BlockLore" } under the block's Use interaction. And one to watch if you animate food: "The blockymodel files for most food items were rebuilt to drive the new eating animations. Custom animations that reference the old node names may break." Renames, Deprecations and Protocol Changes The portal curse surface was renamed wholesale: "AdventureMetadata now carries the ephemeral flag, CursedItems became EphemeralItems, and the /cursethis command is now /ephemeral." The Void Spectre's attack interactions were also renamed to match what they do, with Void_Spectre_Attack becoming Void_Spectre_Charge. On the wire, environments changed shape: Environments now stream one chunk section at a time. SetChunkEnvironments is keyed to section coordinates and carries a single section payload, and SetColumn no longer carries environments at all. Clients and servers have to be on matching protocol versions. Two new server commands help with the heightmap work: /chunk height "dumps a column's heightmap for debugging", and /chunk fixheight now rebuilds the column into a fresh backend. Moderation gets tighter too: "Bans and kicks now close every connection an account has open, including Asset Editor connections that previously remained connected." For Plugin Developers: Hierarchies, Pooled Buffers and Safer Dispatch Entity hierarchies in the ECS store. Plugins can now create parent and child entities, reparent them, and iterate a parent's children. Systems "process root entities by default", and overriding getHierarchyScope() changes that scope. Pooled chunk save buffers. "Chunk saves now borrow their scratch buffers from a bounded direct buffer pool instead of allocating a fresh one per save, which is what stops busy servers from running past the direct memory limit." There is a caveat: "readSegments keeps its signature, but the buffer it returns is pooled, so a caller must not hold on to it after the read finishes." If your plugin stashes that buffer, that is a bug from this build onward. Listener dispatch no longer stops on a throw. "Your other listeners now keep running when one of them throws, and the failure is logged instead of stopping the dispatch." One badly behaved plugin no longer silently disables the ones after it. The fix list rounds it out. An empty OnHitEffects entry on an ItemAbility used to throw a NullPointerException, and validation now rejects it. InstancesPlugin.inheritWorldConfigSettings became inheritDefaultWorldConfigSettings, which is the fix for instances and portal worlds inheriting from the wrong world. Frequently Asked Questions What is Hytale Update 7 Part 3? It is the third section of the living Update 7 pre-release patch notes, headed "Pre-Release (Update 7 Part 3)" and dated September 17, 2026, appended to the same page that carries Part 2 and Part 1. No separate post was published for it. Is Hytale Update 7 Part 3 version 0.7.0-pre.3? The notes do not say so. Part 3 carries no version number at all, and when we checked, the pre-release documentation site still pinned 0.7.0-pre.2 while the stable documentation site pinned Release 0.6.6. Where can I read the Hytale Update 7 Part 3 patch notes? On the same page as Parts 1 and 2, at hytale.com/news/2026/9/pre-release-patch-notes-update-7, at the top. The news index does not link to it separately. Does Hytale Update 7 Part 3 break my world? It changes it permanently. The notes state that cubic worlds now use a new tree heightmap, that BlockSection blobs moved to version 7, and that "a world loaded on this version cannot be opened on an older one". The upgrade happens automatically the first time a world loads, so take a backup before you load anything you care about. Did Hytale fix the texture atlas limit? Part 3 improves it substantially. Overflowing custom content now falls back to the missing texture and logs a warning rather than disappearing silently, and atlases pack across several pages, up to 16 for the block atlas and 4 for the others. The notes do not say the limit is removed, and they do not mention any graphics API by name. What changed for Hytale modders in Update 7 Part 3? The audio timing keys, where "the old spellings no longer decode"; trigger volume PlaySound moving to VolumeDb and PitchSemitones; Encounter asset files having to declare a top-level Class key; CursedItems becoming EphemeralItems with /cursethis becoming /ephemeral; and rebuilt blockymodel files for food items, which may break custom animations referencing the old node names. Is there a Hytale Update 7 Part 4 yet? No. As of 18 September 2026 the page contains exactly three parts. There is also no 0.6.7 hotfix on the stable branch, where 0.6.6 from 14 September is still the newest entry. Do I need to update my Hytale client and server together? Yes. Part 3 changed how environments stream, and the notes state that "Clients and servers have to be on matching protocol versions". The Bottom Line Part 3 is the most substantial of the three Update 7 pre-release sections so far, and the one with the sharpest edge. The texture atlas work is a real answer to a real problem modded servers have been living with, and its diagnostic half, a visible missing texture plus a logged warning, may save more time than the extra capacity does. The rebuilt debug overlay, the pooled chunk save buffers and the long stability list all point at a build being hardened rather than expanded. Set against that is one sentence that deserves more visibility than a bullet buried under "For Plugin Developers" on a page the news index does not link to: a world loaded on this version cannot be opened on an older one. Copy your world, test on the copy, update clients and servers together, and work through the asset schema changes before you restart your content pipeline. Everything else in Part 3 is an improvement you can adopt at your own pace. That one is a door that closes behind you. Running a Hytale server on the pre-release branch? Add it to the HytaleCharts server list so players can find you while the pre-release cycle continues.