Hytale Update 7 Part 4 Patch Notes: The Second Wave of Chapter 1, Six New Runestones, Crossbow Nerfs, and a Chunk API Purge That Will Break Plugins

Hytale added a fourth section to its Update 7 pre-release patch notes on 24 September 2026, and nothing announced it. The heading "Pre-Release (Update 7 Part 4)", dated September 24, 2026, was appended to the same living document that has carried Part 1 since 3 September. The byline on that page still reads "Posted by Hytale Team / September 3, 2026", and the card for it on the news index still shows September 3, which means the index and the RSS feed both miss this drop completely. If you rely on either one, you did not hear about Part 4 today. We checked the page directly, along with the documentation sites. The pre-release docs version switcher at pre-release.docs.hytale.com now reads 0.7.0-pre.4, up from 0.7.0-pre.3. The stable docs at docs.hytale.com still read 0.6.8. On the stable branch there is no new hotfix: the hotfixes page still tops out at 0.6.6 from 14 September, and no "HOTFIXES: UPDATE 7" page exists yet. Everything below is pre-release only. The Second Wave of Chapter 1 Content, and the Forgotten Temple Teaser Part 4 leads with the thing everyone will talk about. The notes open the section by saying the team is adding its second wave of content for the upcoming Chapter 1, that the content is still being actively developed, and that things will continue to change between now and Chapter 1's release. Then comes the line that is doing the real work: For this pre-release, you can begin engaging in Chapter 1 content immediately by visiting the Forgotten Temple. Alternatively, you can wait a few days and see what happens. And immediately after 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! Two things follow from that. The first is that the patch notes are, by the team's own admission, an incomplete description of this build. Reading them start to finish will not tell you what is in the second wave. The second is that "wait a few days and see what happens" is a timed event, not a figure of speech. Something at or around the Forgotten Temple is scheduled to change on its own while pre-release servers are running. There is a corroborating detail buried in the Items & Interactions list, and it is easy to miss: "Whatever's happening at the Forgotten Temple has made it too difficult to sleep there right now, so the bed can no longer be interacted with." A removed bed interaction is a strange thing to write a joke about unless the location is being actively staged for something. Part 4 also opens with a credit line, as Part 3 did: "A huge thank you to NoctuaAstrum and tssan1ty for the fixes, features, and polish they've brought to this update. Your community contributions make Hytale better for everyone!" If you are running a pre-release test server, this is the week to keep it up. Our guide to testing Hytale pre-release builds covers how to get onto the branch and stay on it. French Has Been Added to Hytale's Available Languages The Localization section of Part 4 contains exactly one line: "French has now been added to the list of available languages!" That is worth flagging for server owners specifically, because it widens the set of players who can read your in-game text without a workaround. It also pairs with a localization fix from Part 3 that stopped Hytale falling back to English when a system language carried a regional variant such as French (Canada). The language list and the regional handling landed a week apart, which is a reasonable signal that localization is getting active attention in this cycle rather than being parked until release. Hytale Runestones: Renamed, Re-Rarity-ed, and Six New Additions Part 3 renamed runes so it was clear whether you were holding an Ability Rune or a Modifier Rune. Part 4 reverses part of that and solves it a different way: "Runestones have now been renamed to only include the ability name." The type no longer lives in the item name. "Runestone tooltips now show whether a runestone is an Ability Runestone or a Modifier Runestone." The type moved into the tooltip instead. "Ability Runestones are now Rare quality, and Modifier Runestones are now Uncommon quality." That is a rarity split you can now filter and sort by, and it tells you plainly which half of the system the game considers scarcer. If the Ability and Modifier split is new to you, our explainer on the Chapter 1 rune system covers how the two halves are meant to combine. The Six New Runestones in Update 7 Part 4 Part 4 adds six runestones. Two of them are Ability Runestones. Four of them augment an Ability Runestone, and three of those four are explicitly labelled Modifier Runestones in the notes, with Expansion listed simply as "the Expansion Runestone". RunestoneType as written in the notesWhat it does Chain HookAbility RunestoneGrants the ability to throw out a hook that damages your enemies and reels them toward you. Charged ShotAbility RunestoneGrants the ability to channel a bolt of frost that, when released, deals damage and slows the enemy depending on how long it was charged. ExpansionRunestoneAugments an Ability Runestone, causing its area of effect to be increased by 100%. Extended DurationModifier RunestoneAugments an Ability Runestone, causing its duration to be increased by 2%. ForkModifier RunestoneAugments an Ability Runestone, causing projectiles fired to be split into additional projectiles. These additional projectiles cannot fork again. RicochetModifier RunestoneAugments an Ability Runestone, causing projectiles fired to bounce off of enemies. Read the two numbers next to each other and the balance intent is obvious. Expansion gives an area of effect increase of 100%. Extended Duration gives a duration increase of 2%. Those are the figures in the notes and we are not going to tidy them up for you, but a 2% duration modifier at Uncommon quality is either a deliberately tiny stacking effect or a number that will move before Chapter 1 ships. Worth watching in the next part. Ground Slam and Wind Strike Rebalance Two existing abilities were reworked with exact figures, and they move in opposite directions. Ground Slam gets a large buff with a cost attached. Impact damage goes from 10 to 15. The damage of its earthen spikes goes from 20 to 35. The spikes now launch enemies higher, the ability roots the player for roughly half the previous duration, and the weapon restrictions have been relaxed. In exchange, the cooldown has been increased from 14 to 18 seconds. Wind Strike goes the other way. Its damage drops from 14 to 8, its weapon restrictions are relaxed, and its cooldown drops from 15 to 10 seconds. Less damage per cast, but a third off the cooldown and usable on more weapons. Enrage's animation has also been updated, and in the Naming & Categorization section the Runebinder's Effigy is now referred to as the Runebinder's Lattice. Combat Rebalance: Food, Potions, Movement Speed and Crossbow Damage Eating and Drinking Under Fire The single most practical combat change in Part 4: "Taking damage will no longer interrupt consuming food or potions." Healing mid-fight stops being a gamble on whether anything hits you during the animation. The counterweights are all in the numbers around it. Movement speed while consuming food or potions is now reduced by 25%, previously 60%. You move much better while eating. Food now takes 2.5 seconds to consume, previously 2 to 3 seconds depending on the type. One flat number in place of a range. Bread, Popcorn and Cheese now restore 10% Health, previously 15%. Consuming raw fruit, vegetables or crops now grants a minor Health regeneration buff for 1 minute. Raw meat, fish and eggs do not grant this buff. Buffs granted from consuming cooked food now last 6 minutes. This covers Health regeneration, maximum Health and the maximum Stamina buffs that various cooked food can grant. For anyone balancing a PvP server, that is a coherent package: interrupting an enemy's heal is off the table, so the counterplay moves to closing the gap while they are at 75% movement speed, and the per-item burst from the cheap foods is down. Attacking Now Costs Movement Speed Every melee and ranged weapon class now slows you during the attack. The previous values are given as ranges because they varied by attack. Crossbow: movement speed reduced by 50% during the attack, previously 0%. Sword, mace or battleaxe: reduced by 25% during the attack, previously 0 to 40% depending on the attack. Daggers: reduced by 15% during the attack, previously 0 to 50% depending on the attack. Alongside that, sword, dagger, mace and battleaxe attacks are now roughly 15% faster, sword hits cause less vertical knockback, swords and battleaxes have received new casting animations, and swords play an enchanting animation when casting Poison Imbue or Wind Strike. Faster swings, but you commit to them in place. The Crossbow Damage Nerfs These are the largest single numerical cuts in the Update 7 pre-release cycle so far, and they are worth quoting exactly. Weapon and attackBeforeAfter Iron Crossbow, combo shot2712.5 Ancient Steel Crossbow, standard shot1610.5 Ancient Steel Crossbow, combo shot4213.125 Ancient Steel Crossbow, Signature Attack12382 The Ancient Steel combo shot losing roughly two thirds of its damage, combined with a 50% movement penalty while firing, changes what a crossbow is for. It is no longer the safe high-damage pick. One more ranged change is easy to overlook and genuinely useful: "Arrows now set off Goblin Boom Barrels." NPCs and Entities: Flinching, the Revenant Guardian, and Braver Goblins Flinching is the headline. Non-Elite enemies you encounter in areas related to Chapter 1 will now flinch when hurt, interrupting their attacks. Crucially, it is capped: "If an enemy is made to flinch too many times in a short duration, they will temporarily become immune to further flinching." That is an explicit anti-stunlock rule, and the Modder-Facing section gives the exact numbers behind it, which we cover further down. The Skeleton Elite has been renamed the Revenant Guardian, and the rename is listed twice, once in the NPC section and once under Naming & Categorization. It "has retrieved its own armor and weapons", its sprinting and running animations have been updated, and the armor worn by various Skeletons has been visually updated. Goblins got a full behavioural pass. Their animations have been updated so they now walk, run and look around while prowling, they can now sprint and run backwards, and the Goblin Feastmaster animations have been updated. In the fix list, "Goblins have gotten braver and will no longer run from almost every creature they encounter", and Goblin Turrets "will no longer fixate on threats they haven't seen or heard". Goblin Scrapper, Miner and Guardian melee hits now cause less vertical knockback. Void-aligned creatures will no longer appear within the Echo of Orbis at night, and have been rebalanced, given new looks or attacks. World and Blocks: Foliage, Shears, and World Events You Can Switch Off The foliage change will affect every survival server on the branch. Foliage such as bushes, vines, leaves or seaweed can no longer be broken with weapons. On top of that, breaking player-placed foliage now drops the same things it would in the wild, such as sticks and berries, rather than the plant itself. The notes add the workaround and where to get the tool: "Use shears if you want the plant back. As a reminder, shears can be crafted at the Farmer's Workbench." Shears may also now be used to gather fallen leaf piles. Anyone who builds with decorative plants should expect a round of confused questions from players who chop a bush they placed and get sticks back. World events are now optional. A "World Events" option has been added to the World Settings screen for Creative Worlds so they can be toggled on and off, and Creative Worlds now have world events switched off by default. The Commands section adds one line for it: "World events may be toggled on and off with the command /worldevent." The server-side detail sits in the Server & Permissions section. The command form is /worldevent enable, which takes true or false and toggles when you leave the argument off. Underneath, the WorldEvents plugin stores an EnableWorldEvents flag in a new WorldEventsWorldConfig, and new Creative worlds get it set to false. If you run creative or build servers, that default flips for you automatically on new worlds. Elsewhere in the world list, Hedera's Lair will no longer end in a void breach, Ruined Giant longswords and shields are now accessible in the Creative Inventory, the glider gained falling animations played when Stamina runs out earlier than planned, and coconuts have shrunk in size, "baffling botanists". Audio: 39 New Exploration Tracks The audio section is unusually large for a pre-release part. Part 4 adds 5 new exploration tracks to Zone 2, 10 new exploration tracks to Zone 3, and 24 new exploration tracks to Zone 4, which is 39 new exploration tracks in one drop. Caves and sewers in Zone 4 now have their own music, and a matching fix ensures caves in Zone 4 play the intended Zone 4 cave music rather than overworld tracks. Smaller additions: the Hookshot and the Scrap Glider both got sounds, and Ancient Platform Traps now play a sound as they break. Music transitions will no longer run longer than intended when a fade has a delay in front of it, and sounds attached to creatures or projectiles now play smoothly if you move alongside them. For Hytale Server Owners and Plugin Developers: The Chunk API Purge This is the section that matters most if you ship code. Part 4 carries the longest "For Plugin Developers" block of the Update 7 pre-release cycle, and most of it is one coordinated move: the old column-oriented chunk API is being closed off, and everything is being routed through chunk section references instead. To be explicit before anything else: this is pre-release 0.7.0-pre.4, not the live stable 0.6.8 build. Nothing here has shipped to stable. It is a preview of what your plugin will have to compile against, which is exactly why it is worth reading now rather than on release day. For the wider migration story that started earlier in this cycle, see our Update 7 server and plugin breaking changes guide and our note on the 0.6.8 docs version that arrived without patch notes. Nine Legacy Column Accessors Are Now @RestrictedApi Nine legacy column accessors on WorldChunk and BlockChunk are now marked @RestrictedApi, so a plugin that still calls getBlockChunk, getFiller, getRotationIndex, getHeightmapColumn, getFluidLevel, getSupportValue, setState or setEnvironmentRange no longer compiles if errorprone is used. The replacement is the BlockSection component of the section ref from ChunkStore.getChunkSectionReferenceAtBlock. Note the failure mode carefully. These are not runtime deprecation warnings. With Error Prone in your build, the code stops compiling. If your CI does not use Error Prone, you will not see the breakage until a later part removes the methods outright, which is precisely the pattern the rest of this section follows. A second restriction block covers the reads: WorldChunk.getBlock, BlockChunk.getBlock, World.getBlock and World.getBlockType are now @RestrictedApi too, and the notes say to "Read BlockSection.get on the BlockSection component of the section ref instead". WorldChunk.getBlockComponentHolder is now allowlisted for BuilderTools and BlockSelection only, "since block entity reads go through the section's BlockComponentSection". Methods That Are Simply Gone Removals, not restrictions. These will not compile at all. Removed or restrictedStated replacement WorldChunk.setBlock overloads taking a String, a BlockType, or a BlockType and a rotation, plus BlockChunk.setEnvironmentRemoved as unused WorldChunk.breakBlock, IChunkAccessorSync.breakBlock, BlockChunk.getEnvironment(Vector3i)Resolve the section ref with ChunkStore.getChunkSectionReferenceAtBlock, then use BlockOperations.setBlock or the EnvironmentSection component IChunkAccessorSync.setBlockInteractionState and both WorldChunk.setBlockInteractionState overloadsThe BlockSection component of the section ref from ChunkStore.getChunkSectionReferenceAtBlock The last WorldChunk.setBlock overloads taking a block id or a block key, plus IChunkAccessorSync.setBlock(String, SetBlockSettings)BlockOperations on the section ref from ChunkStore.getChunkSectionReferenceAtBlock BlockChunk.getEnvironment(Vector3d) removed, the (x, y, z) overload restricted to BuilderToolsThe EnvironmentSection component of the section ref IWorldChunksAsync.getChunkAsync(int, int) removed, getChunkAsync(long) and getNonTickingChunkAsync(long) now @RestrictedApi for IWorldChunksChunkStore.getChunkReferenceAsync IChunkAccessorSync.getChunk, getNonTickingChunk, getChunkIfInMemory, loadChunkIfInMemory, getChunkIfLoaded, getChunkIfNonTicking, World.getBlockBulkRelative and every way to build a LocalCachedChunkAccessor, all @RestrictedApiChunkStore.getChunkReference, then read the components on that ref There are two recurring rewards written into these entries, and they are the reason to migrate rather than resist. Both the interaction state write and the block write "skips the blocking chunk load and the old 0 to 320 height cap". Environment reads through EnvironmentSection now answer "at any Y rather than only the old 0 to 320 band". If your plugin has ever worked around the 320 ceiling or blocked a thread waiting on a chunk load, the new path fixes both. One tidy-up goes with it: ChunkAccessor.getFluidId moved up into IChunkAccessorSync, next to the other block reads, and ChunkAccessor is now an empty extension of it. Chunk Storage Providers Gain a readOnly Flag 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. That last sentence is the one to implement correctly. If your storage backend has no read-only mode, the correct behaviour is to fail the request, not to quietly open a writable handle. Getting that wrong turns a validation pass into an accidental write. World.validate Is Replaced by ChunkStorageValidator Instance validation no longer builds a whole world to read its stored chunks, so World.validate and WorldValidationUtil are gone in favor of ChunkStorageValidator. ValidateBlockEvent moved from PrefabBufferValidator to BlockValidator and now fires for chunk validation too, concurrently and off the world thread, so a handler must not keep state between events. Read the last clause as a hard requirement. ValidateBlockEvent handlers now run concurrently and off the world thread. A handler that accumulates into a field, a counter or a shared collection between events was correct before and is a race condition now. Audit every ValidateBlockEvent listener you own before you build against this. The New 256 MiB Per-Asset Cap From the Protocol & Networking section: 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. Two separate rules in one line, and both can take your server offline for players without any error on your side. First, the declared size in AssetInitialize has to be truthful: a client that receives more bytes than the server declared disconnects. Second, no single asset may exceed 256 MiB. If you ship a large custom asset pack, check your largest individual asset now, and check whatever generates your AssetInitialize figures, because a stale or estimated size will start dropping connections. Other Server-Side Additions Worth Knowing Block specific interactions per world. A new BlockedRootInteractionTags list in GameplayConfig.WorldConfig takes root interaction tags, and anything matching is blocked on the server and hidden from the HUD. That is a clean way to disable a mechanic on a single world without touching assets. Persistent portal instances. Portal instances accessed via TeleportInstanceInteraction can now stay around between sessions when their asset asks for it. Worlds spawned from the portal device summon page still set setDeleteOnRemove and setDeleteOnUniverseStart themselves, so those remain temporary and get swept on the next start. Marker debugging commands. /spawning markers debuginvalidmarkers now highlights invalid marker placements and revalidates markers that are moved or rotated, and /spawning markers autoremoveinvalidmarkers switches automatic removal of failing markers on or off. Asset Editor property gallery. The Asset Editor plugin ships a sample EditorPropertyGallery asset showing every property control in one file. It stays unregistered until you create mods/Hytale_AssetEditor/config.json with EnablePropertyGallery set to true and restart the server. Audio binding validation signature change. AudioStateResolver.validateBindings now takes a SubscriberTempo parameter, and the notes say MAY_HAVE matches the old behavior. That is your drop-in value if you just need it to compile. Entity scale and hitboxes. Hitboxes now follow EntityScaleComponent. BoundingBox keeps the entity scale across recomputes and applies it to the detail boxes, and a new EntityScaleBoundingBoxSystem keeps the box in step with the component. World draining is now async. DrainPlayerFromWorldEvent is an IAsyncEvent, so the drain waits for listeners and you can call setWorld once the target world is ready. That fixes loading a destination world while players are being drained out of a world that is shutting down. Modder-Facing Changes Behind the Flinch System The flinching players will notice is configurable. Running Component_Instruction_Hit_Interrupt on a role gives it a 0.5 second flinch, a 0.7 second attack delay, and temporary protection after three reactions occurring within four seconds. Models using a different flinch move can override FlinchAnimation on that component, which otherwise plays Hurt in the Action slot. There are two integration requirements that will bite custom NPCs. Attack instructions and roots need to check for the absence of Hit_Interrupt_Stunned so a queued attack start gets blocked, and offensive roots have to keep their Attack tag for the cancel to find them. A custom attack can also mark where its counterattack ends: Hit_Interrupt_Begin_Protected_Attack goes after the start gate and Hit_Interrupt_Finish_Protected_Attack after the final swing and recovery, "otherwise protection just times out after eight seconds". Other modder-facing items in the same block: a new IgnoreDisableNPCIncomingDamage flag lets a single NPC stay damageable in worlds with NPC damage switched off, with Test_Dummy_Stationary enabled by default; TargetRequireLoS on Component_Instruction_Combat_Target_Swap defaults to true and the default TargetSwitchTimer range moved from [5, 5] to [4, 6] so switches no longer happen in lockstep; Component_Step_Generic_Detection gained an Observe flag with ObserveAngleRange, ObservePauseRange and ObserveRelativeTurnSpeed; and a new HiddenUIComponents key on a role takes a list of EntityUIComponent ids such as ["Healthbar"] to hide the healthbar or its damage numbers. Spawn markers got a substantial pass too. SpawnPositionSearch takes Line to follow the marker orientation or Range for a bounded two-dimensional sweep, MaxHorizontalSpawnOffset sets how far it looks up to 16 blocks, ValidatePosition rejects a marker buried too far inside solid blocks, ValidateBelowPosition rejects one sitting over an empty column looking up to 192 blocks down, RequireFitAtMarkerHeight pins a range search to the marker's Y, and SpawnPositionSearchDebug reports failures with Summary or Map diagnostics. Limits are now bounded as well: MaxDropHeight tops out at 32 blocks and BlockOverlapHeightCompensation at 4, with non-finite or out-of-range asset values rejected as the asset decodes. On blocks and prefabs, UseDefaultDropWhenPlaced is gone from 45 foliage assets, which is the asset-side cause of the player-facing foliage drop change above. Plant_Leaves_Autumn_Floor, Plant_Leaves_Jungle_Floor and Plant_Leaves_Poisoned_Floor each gained a Shears entry in Gathering.Tools, and a new StayOpenWhenEmpty flag on ItemContainerBlock keeps an emptied generated loot container in its open block state. Fixes Worth Calling Out The player-facing fix list is long. A handful stand out for anyone running a world. When a world shuts down and the prior world is unloaded, that world will now be loaded correctly, rather than sending players to a fallback world. Traveling between worlds will no longer cause terrain colors or lighting to bleed between them. Trigger blocks will now fire every time a creature moves over them, instead of just once. Non-opaque blocks placed above crops will no longer prevent the crops from growing in cubic worlds, with the asset-side fix being that WaterGrowthModifierAsset now decides rain exposure from the heightmap. Teleports and respawns will no longer be delayed while the server is generating terrain elsewhere, and opening the world map will no longer cause the world to temporarily stall. Breaking blocks using a tool in the utility slot now correctly reduces that tool's durability, and tools using the per-block durability loss mode now lose durability for each block. Larger creatures will now spawn more reliably with spawn markers, and entities that have been scaled in size will have their hitbox scale with them again. Mantling now works when you are stood atop a half-slab or a horizontal beam. Two crashes are fixed: one that could occur when a chunk unloaded while its animated blocks were updating, and one that could occur when an item, block or ability was used and the client did not recognise the interaction. The block spawner and prefab spawner commands no longer stall the world thread waiting on a chunk, they work at any height rather than only inside the old column range, and targeting a prefab spawner in an unloaded chunk no longer errors out. There is one localization fix written with a straight face that is not a joke about nothing: "After an awkward dinner party, we've concluded there is a difference between fishbones and salt, and we've updated ingredient names accordingly." Placeholder tags were also removed from a number of items and descriptions. Frequently Asked Questions What is Hytale Update 7 Part 4? It is the fourth section of the living Update 7 pre-release patch notes, headed "Pre-Release (Update 7 Part 4)" and dated September 24, 2026, appended to the same page that carries Parts 1 to 3. No separate post was published for it, and the news index card still shows September 3. Is Hytale Update 7 Part 4 version 0.7.0-pre.4? The patch notes themselves do not carry a version number. However, the pre-release documentation site's version switcher moved from 0.7.0-pre.3 to 0.7.0-pre.4 alongside this drop, while the stable documentation site still reads 0.6.8. Where can I read the Hytale Update 7 Part 4 patch notes? On the same page as Parts 1 to 3, at hytale.com/news/2026/9/pre-release-patch-notes-update-7. The news index does not list it separately, so bookmark the page rather than relying on the index or the feed. What is the Forgotten Temple in the Hytale Chapter 1 second wave? It is the entry point the notes give for the second wave of Chapter 1 content: "you can begin engaging in Chapter 1 content immediately by visiting the Forgotten Temple. Alternatively, you can wait a few days and see what happens." The notes also say a lot of what you will encounter in this wave deliberately is not mentioned in them, and the bed at the Forgotten Temple can no longer be interacted with. How many new runestones are in Hytale Update 7 Part 4? Six: Chain Hook and Charged Shot as Ability Runestones, and Expansion, Extended Duration, Fork and Ricochet as runestones that augment an Ability Runestone. Runestones were also renamed to include only the ability name, with the Ability or Modifier type now shown in the tooltip, and Ability Runestones are now Rare quality while Modifier Runestones are Uncommon. Were crossbows nerfed in Hytale Update 7 Part 4? Heavily. Iron Crossbow combo shot damage went from 27 to 12.5. Ancient Steel Crossbow standard shot went from 16 to 10.5, its combo shot from 42 to 13.125, and its Signature Attack from 123 to 82. Attacking with a crossbow also now reduces movement speed during the attack by 50%, up from 0%. What breaks for Hytale plugin developers in Update 7 Part 4? The legacy chunk column API. Nine legacy column accessors on WorldChunk and BlockChunk are now @RestrictedApi, the block reads on WorldChunk, BlockChunk and World are restricted, and the setBlock, breakBlock, setBlockInteractionState and getEnvironment overloads are removed. The stated replacements are ChunkStore.getChunkSectionReferenceAtBlock plus BlockOperations and the BlockSection, EnvironmentSection and BlockComponentSection components. Chunk storage providers also gain a readOnly flag, and World.validate and WorldValidationUtil are replaced by ChunkStorageValidator. Is there a new Hytale hotfix on the stable branch? No. The hotfixes page still tops out at 0.6.6 from 14 September, no "HOTFIXES: UPDATE 7" page exists, and the stable documentation still reads 0.6.8. The Bottom Line Part 4 is the first part of Update 7 that openly refuses to tell you what is in it. The second wave of Chapter 1 content is deliberately under-documented, the Forgotten Temple is the way in, and "wait a few days and see what happens" is a scheduled event rather than a turn of phrase. For players, the rest of the part is a large, legible combat rebalance: eat under fire, move slower while you swing, and stop treating the crossbow as free damage. For anyone running a server or shipping a plugin, the "For Plugin Developers" block is the part to act on. The chunk column API is closing, the replacements are named in every entry, and the two things you get back, no blocking chunk load and no 0 to 320 height cap, are worth the migration on their own. Check your largest single asset against the new 256 MiB cap, make sure whatever declares your asset sizes is honest, and audit every ValidateBlockEvent handler for state that will not survive running concurrently off the world thread. None of it is live yet on 0.6.8. All of it is coming. Previous parts, if you are catching up: Part 3, Part 2 and Part 1. Running a Hytale server on the pre-release branch? List it on HytaleCharts so players can find you while the Update 7 cycle continues.