Hytale Hotfix 0.7.1 Is Live and It Fixes the Two Things That Stopped People Joining Servers: The 30-Second Windows Host Timeout and the "Already Logged In" Reconnect

We need to update the record before anything else. In yesterday's piece on the Chapter 1 patch notes we wrote, verbatim: "There is also no launch-day hotfix. /news/2026/10/hotfixes-update-7 returns 404" and "If you are waiting for a 0.7.1, nothing has been posted yet." Both sentences were true when we checked them. Both are now superseded. Hytale has published a new page titled "HOTFIXES: UPDATE 7", and it carries hotfix 0.7.1, dated Oct 13, 2026. That URL returns HTTP 200 today, as does the longer canonical form. So there is a Chapter 1 hotfix, it is the first one, and it fixes the two problems most likely to have stopped people getting into a server at all. Hytale Hotfix 0.7.1: Where To Find It The page lives at two working addresses: hytale.com/news/2026/10/2026-10-13-hotfixes-update-7/, the canonical URL, where the slug encodes the date hytale.com/news/2026/10/hotfixes-update-7, the short form we reported as a 404 yesterday Its headings, in order, are HOTFIXES: UPDATE 7, UPDATE 7: HOTFIXES, the version 0.7.1 followed by Oct 13, 2026, and then seven sections: Joining & Connecting Fixes, Stability Fixes, Mod Browser Fixes, Forgotten Temple Fixes, NPC Fixes, Creative Tool Fixes and Modder-Facing Fixes. Twelve fixes in total. 0.7.1 is the only version on the page. There is no 0.7.2. This is a separate page from the Update 6 hotfixes, which sit at /news/2026/8/2026-08-27-hotfixes-update-6/ and top out at 0.6.6. The sitemap at hytale.com/sitemap-0.xml now lists 295 URLs and includes both new Update 7 hotfix addresses. Yesterday the only hotfix slugs in it were january-2026, update-5 and update-6, which is why we reported the absence. Hytale Join World Timeout on Windows Hosts, Fixed If you host for friends off a Windows machine, this is the one. The first bullet in the Joining & Connecting section reads: Joining a world hosted on Windows should no longer time out after 30 seconds just as you enter the world. This affected both LAN joins and joins over the internet. Read the shape of that carefully. The connection was not refused. It got you to the point of entering the world and then dropped you at a fixed 30-second mark, which is the profile of a fault people reliably misdiagnose as port forwarding or a bad router. The note that it hit LAN joins too rules out the network edge entirely: a LAN join does not traverse your router's NAT table. If you have spent the last two days walking players through port rules, the fix may be an update rather than anything in your configuration. Our double NAT guide still covers the genuine router-side cases and our failed-to-connect piece the broader diagnostic order, but check your version number first now. Hytale "Already Logged In" on Reconnect, Fixed The second server-side fix is the one that produced the most confusing error message in the game: If your IP address changes during a session, for example when you switch from Wi-Fi to Ethernet, you can now reconnect right away. The server no longer refuses the reconnect as "already logged in". This is a session cleanup problem: the server held the old session open and matched on something that did not survive an IP change, so your own reconnect collided with your own ghost. Laptops roaming between access points, connections that re-dial and machines that gain a wired interface on docking would all have hit it. The workaround was waiting for the stale session to lapse. As of 0.7.1 the reconnect goes through immediately. Taken together, these two are the reason this hotfix deserves attention from server operators rather than just players. Joining and connecting was also the headline section of the last hotfix before this one, 0.6.6 on 14 September, which suggests the connection layer has been the studio's recurring trouble spot across both the Update 7 pre-release cycle and now the stable chapter. And one more joining fix The remaining bullet in that section is smaller but irritating enough to be worth printing: Switching avatar presets no longer drops you into offline mode until you restart the game. Changing your avatar preset silently knocked you offline, and nothing short of a restart brought you back. If a player told you they could not see any servers after fiddling with their character, that was this. Hytale Forgotten Temple Teleporter Repair Costs Now Match This is the only genuine gameplay and balance change in 0.7.1, and it is a straightforward standardisation: Both teleporters in the Forgotten Temple now cost 25 Scraps and a Dubious Assembly to repair. Before, the two teleporters had different repair costs. Two teleporters, one price: 25 Scraps plus a Dubious Assembly each. If you have been costing out a Chapter 1 route for your community, the figures you worked out before 13 October for one of the two are now wrong. The Forgotten Temple is the entry point to Chapter 1 content, so this sits on the critical path for new players. We covered that entry sequence in our launch day coverage. The same section adds feedback that should have been there from the start: Teleporters in the Forgotten Temple now play a teleport sound when you use them. Hytale Mod Browser Install Button Now Explains Itself One fix, and it is a user-experience correction rather than a bug in the strict sense: Mods whose creators do not allow in-game downloads now show a disabled Install button with an explanation, instead of failing with a connection error. You can still download these mods directly from CurseForge. The behaviour was always intended. The messaging was wrong in the most misleading way available: a creator's distribution setting was reported to the player as a network failure, so anyone who tried would reasonably have blamed their connection or Hytale's servers. The mod is still obtainable, just from CurseForge rather than the in-game browser. Nothing changes about what you can run on a server, only whether players understand why an install button will not work. The One Stability Fix, and Exactly What It Covers The Stability Fixes section contains a single bullet: Fixed a disconnect when you go through a portal while a projectile you fired or threw, such as an arrow or a kunai, is still in flight. We want to be precise, because this is the kind of line that gets stretched. It fixes one reproducible disconnect: a projectile of yours is mid-air, you take a portal, you drop. Easy to hit by accident if you are fighting your way to a portal, but it is not a general networking fix and 0.7.1 does not claim to be one. Nothing else on the page addresses disconnects. NPC and Creative Tool Fixes One each. From NPC Fixes: Spawn markers no longer fail to spawn large NPCs that have enough room to stand. Note the qualifier "that have enough room to stand". The check was rejecting valid locations, not creating new ones. If a map you host was conspicuously short of large NPCs, this is a plausible cause, and it pairs with the modder-facing change below. From Creative Tool Fixes: On Windows and Linux, the Node Editor now opens from the Creative Tools menu instead of closing right away. The Node Editor was unusable on two of the three desktop platforms. It opened and immediately closed. Builders and map makers on Windows and Linux get the tool back. Modder-Facing: The New MaxVerticalSpawnOffset Field Three bullets, and they belong together. Spawn markers gain an optional field: Spawn markers have a new optional MaxVerticalSpawnOffset field. It sets how far up and down the marker searches for a spawn spot, up to 32 blocks. If you leave it out, it uses MaxDropHeight, so existing markers keep their current range. Two constraints follow: MaxVerticalSpawnOffset cannot be lower than MaxDropHeight, and MaxDropHeight still limits the final drop for ground movement. A spawn marker with an invalid search range now logs a warning and is disabled. The useful part is the backwards-compatibility guarantee: omit the field and the marker falls back to MaxDropHeight and behaves exactly as it does today. What changes is that search range and drop limit are now separate dials. MaxVerticalSpawnOffset governs how far the marker looks, up to 32 blocks, while MaxDropHeight still caps the actual drop for ground movement. Previously one number did both jobs, so widening a search meant accepting a longer fall. The third bullet helps debugging. An invalid search range used to be something you discovered by noticing nothing spawned; now the marker disables itself and writes a warning. Spawn markers and MaxDropHeight were introduced in Update 7 Part 4 on 24 September, which is the reference to read alongside this if you are implementing it. Hytale's willingness to publish modder-facing notes at all is recent, and we traced its development in our piece on the Adventure 1.0 modder patch notes. Watch the URL, Not the Byline or the Feed Here is the reader takeaway that applies beyond this hotfix. The 0.7.1 content is dated 13 October on the page itself, under the version heading. Everything else on that page says 12 October. The byline reads "Posted by Hytale Team" and "October 12, 2026", in the Game Updates category. It has not been updated for the 0.7.1 content. The RSS pubDate is Mon, 12 Oct 2026 11:09:53 GMT, and it did not move either. The URL slug, 2026-10-13-hotfixes-update-7, is the only part of the publication that reflects when the hotfix actually landed. If you monitor Hytale by watching bylines or feed dates, you will miss hotfixes. The hotfix pages are living documents: Update 6's page accumulated six versions from 0.6.1 to 0.6.6 under a single 27 August byline. Expect this page to do the same, with anything after 0.7.1 appended under an October 12 byline and an unchanged feed timestamp. The slug is the signal, and the sitemap is the other one, which is how we spotted this at all. The Game Is on 0.7.1, the Docs Are Still on 0.7.0 The documentation site has not followed. The switcher on docs.hytale.com still reads Release 0.7.0 (current), and pre-release.docs.hytale.com reads Pre-release 0.7.0-pre.5 (current). There is no 0.7.1 docs version. That is not a story, because the docs did not move. It is worth a sentence as a practical warning: the version you are running and the version the documentation describes are no longer the same number, so do not use the docs switcher as a release tracker. It is the inverse of the gap we wrote about in September, when the docs showed 0.6.8 with no patch notes to explain it. What We Have Not Verified Being straight about the limits of this report: We have not played 0.7.1 or tested any of these fixes. Every fix above is read from Hytale's own hotfix page. We have not reproduced the Windows join timeout, confirmed the reconnect behaviour, or priced the temple teleporters in game. There is no next-hotfix date. The page lists 0.7.1 and nothing else. There is no 0.7.2, no schedule and no stated plan for one. We cannot rule out further silent edits. The byline and RSS pubDate did not move for this update, so we have no reliable way to detect the next change to the page other than re-reading it. If content is appended again, the same discrepancy will hide it. We are not claiming 0.7.1 resolves the wider disconnect reports. One disconnect is fixed, the portal-with-projectile-in-flight case. Anything else people have been experiencing since launch is not addressed on this page and we are not going to imply otherwise. No known issues list exists. The page does not carry one, and we have not constructed one. If you run a server: update, and tell anyone who could not get in to update as well, particularly if you host on Windows. If you maintain spawn markers, read the three modder-facing bullets before your next content pass. And if you are picking a server to play Chapter 1 on, the list on HytaleCharts is sorted by votes, not by anything we were paid to show you.