Hytale Update 6 Part 4 Patch Notes: Pre-Release Lands June 18 — A New Color Tool, No-Code Encounters with Trigger Volumes & EncounterManager, and Builder Tools in Survival

Thursday again, and the rhythm holds. Part 1 landed May 28; Part 2 on June 4; Part 3 on June 11; and right on schedule, on Thursday, June 18, 2026, the Hytale Team updated the Pre-Release Patch Notes for Update 6 in place, with a fresh section headed "Pre-Release (Update 6 Part 4): June 18th, 2026." If Part 3 was a polish-and-fixes build, Part 4 has a clear theme: this is the update where Hytale keeps shedding the need for code. Between upgraded Trigger Volumes, the new EncounterManager asset, and Builder Tools that now run in Survival, a map-maker can script a multi-NPC boss fight without writing a line of Java. Same caveat as every week: this is the pre-release testing branch (Launcher → Settings → Pre-Release), not stable, and features may still change before they ship. There is no announced Update 6 stable date — the studio has not committed to one publicly, so anyone quoting you a date is guessing. The cadence is weekly pre-release Thursdays, with the team shipping these notes in place and Simon typically announcing each drop personally on X; on that pattern the next part would be expected around Thursday, June 25, though that is an expectation, not a confirmation. Here is everything in the hytale update 6 part 4 drop, organized by what it actually changes. The Color Tool — Coloring, Gradients, and Shading The screenshot-friendly headline of this hytale pre-release is a brand-new Color Tool, available in Creative Mode under the Specialized Tools section of the Creative Inventory. It ships with three distinct modes, and together they turn block recoloring from a tedious manual job into something closer to digital painting. Coloring replaces the blocks you aim at with another block, and it can preserve shape variants as it goes — so recoloring a sculpted structure does not flatten its detail. Gradient paints smooth color transitions across an area, the kind of soft falloff that is painful to hand-place block by block. Shading is the clever one: it applies lighter or darker tones based on a chosen light source, a surface angle, or a custom palette, letting you fake depth and form across a build the way an artist would shade a drawing. For builders and map-makers, this is a genuine time-saver and a quality lever. Atmospheric sets, terrain blends, and stylized structures that used to demand painstaking manual variation can now be roughed in and refined in a fraction of the time — and they will photograph well, which matters when you are trying to make a server listing stand out. Trigger Volumes Grow Up — Multiple Rule Sets and New Events Trigger Volumes arrived in Update 5 as Hytale's no-code logic primitive, and Part 4 is where they grow up. The single biggest change: a volume can now hold multiple independent rule sets on the same event, grouped by Entry number. That means one volume can run several distinct "if this, then that" chains in parallel rather than forcing you to chain everything into one tangled rule — a real step up in expressiveness for encounter and puzzle design. Two new events expand what a volume can react to. On Block Used fires when a player interacts with a usable block inside the volume — a door, lever, or chest — and On Entity Died fires when an entity in the volume dies. Paired with two new conditions — Block Used (filter by block type or state) and Entity Count (counts the living NPCs in a volume) — you can now build logic that responds to player interaction and to the state of a fight, not just to entry and exit. The new effects are where the no-code encounter idea clicks into place. Spawn NPC spawns one or more NPCs, and Play Animation makes the triggering entity, or every entity in the volume, perform an animation. Spawn a wave of enemies when a player pulls a lever, count down the living NPCs, then fire a cinematic animation and reward when the last one dies — all inside a volume, no script required. A long list of existing conditions and effects also got more flexible. Item Condition gained comparison operators, an empty-inventory toggle, and metadata filtering; Block Type Condition picked up rotation options; Tag Condition added a "Doesn't Have Tag" inversion; Send Message gained a recipient option and can now include volume tag values; Play Sound added a location option that defaults to the volume center; Run Root Interaction got an equip-slot field; Place Block and Replace Block Type both gained rotation options; Teleport added a "Relative to Volume" option; and Modify Tags gained an append operation. Finally, four new commands make volumes easier to manage in the field: /triggervolume tag set, /triggervolume tag remove, /triggervolume tp, and /triggervolume rename. One note for anyone who got bitten last week: a June 17 hotfix fixed Trigger Volume effect presets corrupting the base game asset pack, so the foundation under all of this is now safe to build on. The EncounterManager Asset — No-Code Multi-NPC Boss Fights If Trigger Volumes are the trigger, the new EncounterManager JSON asset type is the brain. It lets modders script multi-NPC encounter logic using reusable NPC instruction lists — so instead of hand-wiring every enemy in a fight, you define instruction sets once and reuse them across the NPCs in an encounter. This is the piece that turns "spawn some enemies" into "run a structured boss fight." Two new hooks make boss tracking work cleanly. ActionTriggerSpawners can now mark a spawned NPC as a boss target for encounter tracking via MarkAsTarget: true — so the system knows which spawned creature is the one that matters. And the new EntityFilterDeath filter lets role sensors react when a tracked entity dies, which is exactly the signal you need to advance phases, trigger the next wave, or end the fight. Put the pieces together and the picture is striking. A Trigger Volume spawns waves and counts living NPCs; an EncounterManager drives the multi-NPC logic with reusable instruction lists; MarkAsTarget flags the boss; and EntityFilterDeath reacts to its death to close the encounter. A scripted, multi-phase boss fight — built largely without writing Java. That is the headline for modders and map-makers in hytale update 6 part 4, and it is a meaningful lowering of the bar for ambitious adventure content. The modding API and server plugin development guide covers where code still fits if you want to go deeper. Builder Tools Outside Creative Mode The third leg of the creator story: Builder Tools can now run outside Creative Mode. To enable a tool in Survival, you set SurvivalAllowed: true in that tool's asset JSON and grant the matching permission — hytale.editor.tool.entity, hytale.editor.tool.ruler, or hytale.editor.tool.laserpointer. Both the flag and the permission are required; one without the other does nothing. For server owners, this is a precise, opt-in capability. Staff and trusted builders can be granted measuring, entity, and laser-pointer tools in a live Survival world without flipping the whole server into Creative — which is exactly the granularity you want for moderation, event hosting, and guided builds on a survival server. More for Modders — Armor Movement, Voice Prefs, and Death Sensors Beyond the encounter stack, Part 4 ships a useful set of additional hytale modding api capabilities. Per-piece armor movement. You can now add a MovementSettings block to an ItemArmor asset to override walk speed, sprint speed, jump height, air control, and more on a per-piece basis. That is the foundation for movement-defining gear — light boots that boost sprint, heavy plate that trades speed for protection — exactly the build-crafting system RPG and adventure servers want. Voice preferences exposed to the server. Voice settings are now surfaced to the server via SyncPlayerPreferences with three new fields: VoiceChat, VoiceInput, and VoiceInputMode. Server-side mods can now read player voice configuration to build proximity-chat features, voice-aware moderation, or role-gated channels. Death-reactive sensors. The new EntityFilterDeath filter mentioned above is not only for boss encounters — it gives any role sensor a clean way to react when a tracked entity dies, which opens the door to quest logic, escort-failure detection, and reactive AI without polling. This all continues the broader Update 6 modding migration that has rolled out across the cycle. If you are catching up, the Update 6 Part 1 patch notes cover the hytale/3 protocol bump and Block Palette Presets, the Part 2 patch notes cover the World-Gen V2 graph additions, and the Part 3 patch notes cover the breaking ECS NPC migration that this build's encounter work builds on. World-gen modders should keep the World-Gen V2 graph nodes guide handy, and if you are tuning the new armor movement stats, the movement and combat-feel guide is the right companion read. Quality of Life and the Fixes That Matter On the polish side, the Server Discovery screen can now be navigated with a controller — a small but welcome accessibility win for the screen players use to find your server. And the "Use Legacy Network Stack" option was removed from settings, retiring an old compatibility toggle now that the new stack has settled in. The bug-fix list in these hytale update 6 patch notes is substantial, with NPCs and stability leading. NPC suppression incorrectly causing unrelated NPCs to spawn is fixed; NPC health fully resetting on reload is fixed; and NPCs losing active effects after save, reload, or duplication is fixed — three fixes that together make custom creatures far more reliable across sessions. On the portal side, summoned portals failing when a destination world was just created but not fully loaded is resolved, portal devices now show an error and refund portal keys when there is no valid spawn location, and dying near a teleporter could still teleport the player — also fixed. A handful of build and world fixes round it out: fluids placed by prefabs always appearing at max depth is corrected, and several Creative place-mode (Extrude and Draw) block issues are resolved. On stability, a crash when multiple players join simultaneously is fixed — which also restored missing player-list entries — alongside a fix for a crash caused by a corrupted local server-list cache, and the client and protocol were hardened against crashes on custom server implementations. There is also a fix for a small VRAM leak from text rendering, and a friendlier wrong-system-clock login error that now tells you how far off your clock is. What Server Owners and Map-Makers Should Do This Week Part 4 has no new block sounds and no protocol bump — the hytale/3 jump was Part 1, back on May 28 — but it hands creators a stack of new tools worth getting your hands on. Here is the checklist: Prototype a no-code encounter. The big opportunity is the Trigger Volume plus EncounterManager combo. Build a small test: spawn a wave with the Spawn NPC effect, mark a boss with MarkAsTarget: true, count the living NPCs with the Entity Count condition, and fire a reward on EntityFilterDeath. Prove the loop on the pre-release branch before you design a full fight around it. Take the Color Tool for a spin. Try all three modes — Coloring, Gradient, and Shading — on a structure you care about. The shading and gradient modes especially can lift a build's screenshots, which is free marketing for your server. Scope Builder Tools for your staff. If you want trusted builders working in a live Survival world, set SurvivalAllowed: true on the tools you want and grant the matching hytale.editor.tool.* permissions. Remember: both the flag and the permission are required. Validate your NPC and portal content. The NPC health, effect-loss, and suppression fixes plus the portal and teleporter fixes touch a lot of custom content. Get your test server onto the pre-release branch and confirm your creatures, portals, and teleporters behave correctly under the new build. Keep your listing current. Pre-release weeks are exactly when curious players go hunting for active, well-run servers to try the new build on — and Server Discovery is now controller-friendly, so more of them will be browsing. Make sure your HytaleCharts server listing is sharp — banner current, heartbeat reporting live player counts, votifier wired up, and your description clear — so the players looking for somewhere to land choose you. Update 6 Part 4 is a creator's build: the three-mode Color Tool makes recoloring feel like painting, upgraded Trigger Volumes and the new EncounterManager asset let you script multi-NPC boss fights with almost no code, Builder Tools come to Survival, and a deep run of NPC, portal, crash, and VRAM fixes steadies the foundation. There is still no Update 6 stable date announced, so treat hytale update 6 part 4 as the live edge to test against. Prototype an encounter, color a build, tidy your hytale server list entry, and you are ready for whatever lands next Thursday.