Hytale Update 6 Part 11 Pre-Release Patch Notes (August 6, 2026)

Hytale Update 6 Part 11 arrived on August 6, 2026, and it does something no previous part has: it rebuilds a feature that shipped two weeks earlier. Hardcore mode went live in Part 9 as a single on/off setting locked at world creation. Part 11 replaces that switch with five named settings, a lives counter, a server config key, a new network packet and a permissions reshuffle. Everything here comes from the official rolling pre-release patch notes page, which runs from Part 1 through Part 10 on July 30 to this one. Part 11 got no standalone news post. There are no August 2026 posts on the Hytale news index at all: it exists only as a section on the rolling page, so it is easy to miss. What Is New in Hytale Update 6 Part 11? Five things carry it: five hardcore settings, the Defaults.HardcoreMode config key, a Java runtime bump, four compile-breaking API changes, and discoverable map markers. Then cosmetics, twenty bug fixes and rendering polish. The Five Hytale Hardcore Mode Settings, Quoted in Full The notes state it plainly: "There are now five different hardcore mode settings you may select from when generating a new world:" "Off: Hardcore isn't enabled." "Permadeath: Each player has a single life. Death is permanent." "Three Strikes: Each player has three lives. After strike three, you're out." "Nine Lives: Everyone in the world has a shared pool of nine lives. Once the ninth death occurs, the run ends for all." "Soulbound: Everyone's fate is interconnected. If any player dies, the run's over." Two lines complete it. On tuning: "When worlds are being created in Three Strikes or Nine Lives mode, the number of lives initially available can be increased or decreased from the default. No, it cannot be set to zero." On feedback: "When a hardcore mode is enabled, the number of lives remaining will appear above your health." The distinction the names hide: per-player versus whole-world Read as a list, those five look like a difficulty ladder. They are not. Permadeath and Three Strikes are per-player: your deaths are yours, and if you die out the world carries on without you, exactly as Part 9 hardcore behaved. Nine Lives and Soulbound are shared. Nine Lives gives everyone in the world one pool, and on the ninth death "the run ends for all". Soulbound has no pool at all. In both, one person's death can end everyone's run, including for players who were offline when it happened. That is a different kind of multiplayer, not a harder one: a co-op game with a single shared fail state, closer to a raid wipe than a death penalty. Anyone who can join a public server can end its season, so whitelisting and trust become mechanical concerns rather than policy ones. Our hardcore mode guide predates this change, but its fundamentals still apply. What a shared wipeout does to everyone is undocumented: Part 9 described only the individual case, with avatars that "drop all of their worldly possessions and be switched into Spectator Mode." We will not assert that applies to a whole server at once. A dark cave is exactly the sort of place a Permadeath run ends, and in Soulbound it would end for everyone else too. This is a general official Hytale screenshot from the media gallery, not a Part 11 screenshot. Hardcore Is Now a Server Config Choice "Hardcore is now a server config choice. Defaults.HardcoreMode can be set to None, PerPlayer, or Global. Existing hardcore worlds will be migrated to the PerPlayer setting." If you already run a Part 9 hardcore world, you do not have to do anything: the migration to PerPlayer is automatic and preserves the behaviour you had, since Part 9 hardcore was per-player by definition. Being honest rather than tidy about the rest: the notes do not document how the five in-game settings map onto those three config values. None, PerPlayer and Global line up suggestively with Off, the per-player pair and the shared pair, but suggestive is not documented, and nothing says whether Global distinguishes Nine Lives from Soulbound. Set it, make a test world, see what the creation screen offers. We would rather flag an open question than invent a mapping table. PlayerLives, /player lives, and a permissions change to audit "Added a PlayerLives component that any game mode or plugin can read and write to. The /player lives commands sit in the WorldEditor permission group." "The /player respawn command now lives in the Builder permission group. Reviving other players now has its own player.respawn.other node in the WorldEditor permission group." /player respawn moved groups, and reviving somebody else is now its own node in a different group. If your staff roles were built around the old arrangement, the people who can bring a dead player back are not the set you configured. On a Soulbound or Nine Lives world a revive is effectively a rollback of the season's fail state, so audit that before you open the doors. PlayerLives is the developer half, and it turns hardcore into a substrate: life tokens as rewards, a life bought back with an item, lives-based tournaments, all component reads and writes rather than a game-mode fork. The wire protocol gained a packet "The wire protocol gains an UpdateLivesRemaining packet and a nullable LivesRemaining field on the player list entry, carrying each player's remaining hardcore lives." Proxies, bots, panels and overlays that parse the player list need a new packet type and a nullable field. Nullable is the important word: null is not zero lives, it is a player with no hardcore state. Hytale Now Ships Temurin JRE 26.0.2+10, and Shenandoah Users Should Update The Stability Fixes section opens with a preamble rather than a bullet, and it is the most actionable line in the drop: "We have updated the version of Java used to run the game in the Hytale Launcher (Temurin JRE 26.0.2+10). Note: If you are running a dedicated server and use Shenandoah GC we recommend you update to using Temurin JRE 26.0.2+10." That matters more than two sentences suggest, because almost every Hytale server setup guide in circulation still tells you to install Java 25, several of our own older articles included. We are updating ours. Two precision points, because this is the sort of note that gets over-reported. First, the bump is stated for the Hytale Launcher; the notes give no minimum required JRE for dedicated servers, and neither do we. Second, the Shenandoah line is a recommendation for one configuration, a dedicated server and Shenandoah GC. It is not a requirement, it is not stated for other collectors, and no JVM flags are published with it. Stability Fixes: Five, and Two You Will Feel Fixed a crash that could occur when interacting with incomplete menus. Fixed a crash that could occur when trying to load a creature or object of an invalid size. Fixed a rare issue that could suddenly disconnect players from a server on linux. Fixed an issue that could prevent players from rejoining a server until the server restarted. Fixed a periodic freeze that could occur on busier servers when saves occurred. The rejoin fix covers the failure where the process is alive, the panel says online, and a disconnected player cannot get back in until somebody restarts. Part 10 handled the world thread dying outright; this is the quieter variant where nothing crashes and nobody can play, and our crash recovery guide covers the policy around it. The periodic freeze on busier servers when saves occurred is the other: a rhythmic hitch every few minutes may not have been your plugins. Breaking Changes for Hytale Plugin Developers Four changes here will not compile against your existing source. 1. A removed method. "Removed the deprecated BlockModule.ensureBlockEntity. Block entity spawning now goes through BlockEntity.ensureBlockEntity, with BlockEntity.declaresComponent for checking whether a block type's entity template declares a component." Deprecated, so a mechanical swap. 2. World event lookups went async. "World event location lookups are now async. EventLocation#find becomes find(store) returning a CompletableFuture<Vector3iList> in place of the old find(dt, store, locations). Spawner#getHeight is replaced by Spawner#findSurface, which hunts for the nearest qualifying surface rather than only reading the outdoor heightmap." A synchronous call becoming a CompletableFuture restructures whatever called it. 3. The one that catches everybody. "ISpawnable now has a requiresSpawnDropHeightCheck(SpawningContext) method with no default, so any plugin that implements ISpawnable or extends BuilderBaseWithType or BuilderMotionControllerBase has to implement it." Note with no default: nothing to inherit, so every class in that hierarchy stops compiling until you add it, whether or not your plugin touches hardcore. 4. Respawns are cancellable. "Respawns can now be canceled. A new RespawnEvent fires from DeathComponent.respawn and a plugin can register an EntityEventSystem for it to observe or refuse a player's respawn. DeathComponent.respawn now returns a nullable future, where null means a listener canceled and the entity stays dead, so any caller chaining that future has to check for it." Code chaining off that future without a null check throws the first time anything cancels a respawn. Non-breaking additions include MaterialQuantity.toItemStacks, a CleanupOnRemove encounter flag, Clearance and SearchRadius on LocationCondition assets, and FirstSpawnItems in the gameplay config Spawn block. World generation gains a Trig density node, where "Type": "Trig" "takes a Function of Sin, Cos, Tan, Asin, Acos, or Atan and an InputScale that multiplies the input before the function runs." Our plugin development, Maven and CI/CD guide covers pinning a pre-release version safely. Discoverable Map Markers: For Quest and Adventure Servers Scattered across four sections is one feature. "A new Discoverable flag on BlockMapMarker and BlockMapMarkerData keeps a marker off the map until a gameplay system reveals it, tracked per player and per world." Per player is the key phrase; discovery state is individual. Driving it: a "RevealMapMarkersInView interaction for items and blocks that uncovers hidden discoverable map markers inside a player's view cone", a treasure map with no code required, plus "a number of /worldmap markers commands to place and test discoverable markers in-game". For developers, DiscoverableMapMarkers is the entry point, "where isRevealed, reveal, and hide are safe from any thread while collectMarkersInView reads the chunk store and must run on the world thread." Calling the collector from an async task is the bug you will write if you skim. Everything Else in the August 6 Notes Cosmetics got a pass: haircuts recoloured, ear accessories aligned per ear type, three items gaining colour options and fifteen reworked. There is a new Full Leafy Soil block, carrying the best line of the drop: "It's like the Leafy Soil block, but fuller." Settings gained "a search button to the Settings menu that searches across all tabs", and the Trigger Volume tool gained "a rotation option when a trigger volume pastes a prefab, so you can turn the pasted build by 90, 180, or 270 degrees". On rendering: "Improved how transparent surfaces look, particularly when looking through multiple different transparent things at the same time like glass and water." Our reading, not the notes: that looks like the return of the transparent-effect work Part 9 reverted. The notes do not say so, and we are not claiming it as fact. The full player-facing bug fix list: Fixed an issue which allowed some players to perform interactions through projectiles or entities they didn't launch. Climbable blocks that exist very far away from the center of the world may now be climbed upon once more. Spectators will no longer count toward the number of players needed for some events to occur. The Stone Brick - Ornate block inventory icon is now more accurate. Mud, Hive, and Tar blocks will now correctly render when placed adjacent to one another. Deep Grass blocks will now render the correct color when placed adjacent to other blocks they can transition to. Fixed z-fighting occurring with Feran Double Doors, Redwood fences, the Farmer's Workbench, Blacksmith's Anvil, and the Crude Hoe, in addition, the Redwood fences got a slight upgrade so its variants look more consistent when placed all together. Fixed Wind Temple window frames gaps in model. Mithril cuirass texture that was bleeding is fixed. Added a full block variant for Soil Leaves. The Mithril Cuirass will now render with less texture bleeding. Farming tools should now all work correctly in cubic worlds. Projectiles that are stuck in blocks, or laying on the ground, will now fall to the ground if the block they're stuck in, or laying on, is removed. Avatars will no longer be able to negotiate insane deals by only giving a single item to trading NPCs when the merchant had requested multiple copies. Flying and swimming creatures will now appear more often in places you'd expect to see them. Resolved a dimension error involving the Clay Raw Brick half-block texture. Grass, leaves, and other foliage will now look brighter. Shadows will no longer leak halfway through blocks and so should generally look better. Reduced the memory usage of some mip-enabled textures. News tiles will now be displayed in your system language (if available) if you use the language setting "Use System Language". The spectator fix is a quiet good one for owners: staff in spectator no longer inflate the player count that gates event spawning. Server consoles also regain chunk-coordinate commands and proper translated error messages. Version 0.6.0-pre.11 and the Release Window Part 10 stated no build string, so we cited community numbering. Part 11's version is officially observable in two places. The pre-release Maven metadata lists 0.6.0-pre.11 as both latest and release, last updated 2026-08-06 at 14:33:39 UTC, and pre-release.docs.hytale.com renders "Pre-release 0.6.0-pre.11 (current)" in its sidebar. Pleasingly, that version switcher is itself one of Part 11's own Documentation Changes. On stable, the release channel is still 0.5.7, last updated July 19, 2026. No stable Update 6, no announced date, and we are not going to predict one. The only timing signal on record is the July 16 post "First Look: Chapter 1 and More", which listed "Spectator and Hardcore: 2-3 weeks (Update 6)". That window is roughly August 6 to 13, so today sits inside it and Hardcore did just get finished off. An alignment and nothing more: an estimate offered at the time, not a commitment, never restated, and a feature being complete on pre-release is not a stable build being ready. We track it in our Update 6 release date roundup. FAQ What's new in Hytale Update 6 Part 11? Part 11, dated August 6, 2026, rebuilds hardcore into five settings with a lives counter, adds the Defaults.HardcoreMode config key and a PlayerLives component, moves /player respawn into the Builder permission group, adds an UpdateLivesRemaining packet, ships five stability fixes and a Java bump, adds discoverable map markers and clears twenty bugs. What are the five hardcore modes in Hytale? Off, Permadeath, Three Strikes, Nine Lives and Soulbound. Permadeath gives each player one life and Three Strikes gives each player three, both per player. Nine Lives gives the whole world a shared pool of nine, and Soulbound ends the run if any single player dies. What is Soulbound mode in Hytale? The notes define it as "Everyone's fate is interconnected. If any player dies, the run's over." It is the strictest of the five: no pool, no per-player allowance, one death anywhere ends the run for everybody. Can I change hardcore mode after creating a world? Part 11 describes the settings as something "you may select from when generating a new world", and Part 9 was explicit: "Hardcore Mode can only be activated when creating a new world. Once a world has been created, this setting cannot be adjusted." Part 11 does not say that has been lifted, and it does not document Defaults.HardcoreMode as a way to convert an existing world. Starting lives in Three Strikes and Nine Lives are adjustable at creation, but not to zero. Is Hytale Update 6 out yet? Not as a stable release. As of August 7, 2026 the stable channel is still 0.5.7 and Update 6 exists only on the pre-release patchline, currently 0.6.0-pre.11. No stable release date has been announced. How do I join the Hytale pre-release to try Part 11? Pre-release is opt-in through the launcher, under Settings. Use a copy of your world rather than your main save, because pre-release builds change weekly and can regress. Our guide to testing Hytale pre-release builds covers opting in, backups and rolling back. What Part 11 Means If You Run a Server Three jobs. Update your JRE if you run Shenandoah GC. Audit your permission groups, because /player respawn moved and player.respawn.other is new. And choose per-player or shared before you start a hardcore season, because Nine Lives and Soulbound turn every player you admit into someone who can end it for everyone. If you build one, list it on HytaleCharts so the players hunting exactly that run can find you.