Hytale 0.6.4: Better Automatic Port Forwarding, Fewer Broken Rejoins, and a Hotfix You Will Not See on the News Page

Four days after the Update 7 Part 1 pre-release pulled attention onto Chapter 1, Hytale quietly shipped a stable hotfix. 0.6.4 landed on Monday 7 September 2026 at the top of the living HOTFIXES: UPDATE 6 page, and docs.hytale.com now pins it. If you host worlds for friends, three of its lines are the reason to update today. Why You Probably Missed It The hotfixes page is a living document: Hytale appends each build to the top of the same post rather than publishing a new one. That post still carries its original byline, "Posted by Hytale Team August 27, 2026", so on the news index nothing happened on 7 September. Only the page body shows 0.6.4. That is why you have seen no announcement, and the same reason 0.6.3 slipped past a lot of people on 31 August. The reliable signals are the version on docs.hytale.com and the top heading inside the hotfixes page. Bookmark the page, not the index. Joining and Connecting Fixes Router discovery no longer gives up early. "Improved automatic port forwarding. Router discovery no longer gives up early when other devices on your network are slow to answer, so fewer players should see the 'automatic port forwarding is unavailable' message." Two PCs on one network stop fighting. "Fixed a case where two PCs on the same network could remove each other's port forward when either opened or joined a world." Hosts hold the connection open. "Hosts now keep their connection to the network alive while a world is open. This should help with cases where friends could not rejoin after a disconnect until the host restarted the game." Each maps to a complaint people have been posting. The first is a timeout problem, not a capability problem: on a busy home network, other hardware answering slowly could make Hytale conclude there was no forwardable router, so try again before going near your router's admin page. The second explains the most confusing reports: two machines in one house, each stepping on the other's port forward, so friends can join when one of you hosts but not when the other does. The third is the "restart the game and it works" bug, whose workaround was effective enough to hide the cause. None of this is a Double NAT fix, and it is not billed as one: if your ISP hands you a carrier-grade NAT address, no local forwarding creates a route. Our Double NAT explainer keeps the hedges intact, and the Update 6 Part 13 hotfix has the routing work these build on. World and Block Fixes, With a Caveat That Matters "Entities with block models saved in Update 5 worlds now keep the correct position and scale when the world is upgraded to Update 6. Note: This does NOT repair entities that were already upgraded with the wrong position and scale." Read that note carefully, because it changes what you should do. The fix applies at upgrade time: a world you have not upgraded yet will now upgrade correctly, but a world you already upgraded stays broken. If you still have Update 5 worlds sitting unopened, this is the build to upgrade them on. If one came through wrong and you kept an untouched backup, restoring and upgrading again on 0.6.4 is the only supported route. Otherwise it is a manual fix. Creative Tools, Audio and Stability Three builder tool fixes land: rotating a multi-axis block selection "now rotates entities with block models correctly", builder tool keys "no longer stay bound after you leave a world", and dragging an icon-less item onto the entity tool no longer crashes. That last one matters on a modded build server, where an unresolved icon is a normal consequence of a half-loaded mod. Ambient world loops now stop "the moment you leave a world", and three server-side stability fixes land: a crash "when the server sends a fluid update before it has sent every block type", plus server errors on an explosion that damages no blocks and on a respawn confirmation arriving after the player has left. Three modder-facing fixes round it out, led by Anchor PropDistribution "dropping random parts of props in an 8x8 grid pattern" on multi-threaded world generation. All three subjects appear in the Update 7 Part 1 notes too, the ItemGrid and ClientTool entries in near-identical wording and the Anchor one described instead as a shared "global context instance", which is consistent with the same fix written up twice: work lands in pre-release, then gets back-ported to stable. Where 0.6.4 Sits The stable line now runs 0.6.1 and 0.6.2 (both 27 August), 0.6.3 (31 August) and 0.6.4, with networking the theme throughout; our Update 6 hotfix tracker has the sequence. The pre-release branch has moved to 0.7.0-pre.1. Two trains, one launcher toggle: if you run a public server, stay on stable. Update, 14 September 2026: the point above about the news index has since proved itself again. 0.6.5 landed on 10 September, appended to the same page under the same August 27 byline, with no post anywhere to announce it. It is a stability and polish build rather than a networking one: a client memory leak when joining worlds or switching instances, a server memory leak where unloaded worlds stayed resident after their world maps were generated, and a crash when leaving a world with a machinima scene loaded. Server owners get one line that is worth acting on, because it closes a ban-evasion gap: "Server bans now apply to asset editor connections. Kicking or banning a player also closes their active editor connections." The social recovery and trigger volume fixes listed here as shipping in Part 1 also reached stable in it. 0.6.5 is the current stable build, so take that rather than 0.6.4. On the other track, the pre-release pin has moved again, to 0.7.0-pre.2: see our Update 7 Part 2 write-up. Frequently Asked Questions What is in Hytale hotfix 0.6.4? Improved automatic port forwarding, a fix for two PCs on one network removing each other's port forward, hosts keeping their connection alive while a world is open, correct position and scale for block model entities when Update 5 worlds are upgraded, and ten builder tool, audio, stability and modder-facing fixes. It shipped on 7 September 2026. Does 0.6.4 fix "automatic port forwarding is unavailable"? It should reduce it. The cause addressed here is router discovery giving up early when other devices on your network are slow to answer, so a router that does support forwarding could be missed. Hytale's wording is that "fewer players should see" it, not that it is gone. Does 0.6.4 fix Double NAT? No. These are local port forwarding and host session fixes. Double NAT and carrier-grade NAT sit upstream of your router and no local forward solves them. The work Hytale has pointed at for that is aimed at the Update 7 pre-releases and has not been announced as shipped. Will 0.6.4 repair my already upgraded world? No. Hytale states it explicitly: the fix does not repair entities already upgraded with the wrong position and scale. It applies only when a world is upgraded from Update 5 on this build. If you kept an untouched pre-upgrade backup, restoring and upgrading again on 0.6.4 is the supported route. Why does 0.6.4 not appear on the Hytale news page? Because Hytale appends hotfixes to one long-lived post rather than creating a new one, and that post keeps its original date. The byline still reads August 27, 2026 even though the newest build on it shipped on 7 September. Check docs.hytale.com or the hotfixes page directly. The Bottom Line 0.6.4 is a small release doing unglamorous work on the part of Hytale that frustrates people most: getting friends into your world and keeping them there. Its joining and connecting fixes are still the reason it matters, and they carry forward into every build after it, so if you are anywhere below 0.6.4 these are the fixes you are missing. Update to the current stable build, which is 0.6.5 as of 14 September 2026. And if you would rather play on a world somebody else keeps online, browse the Hytale server list.