Hytale Hotfix 0.7.3 Arrived Unannounced With Your Own Sentry Project, a Lower glibc Floor and Eight Joining Fixes

There is a third hotfix. Hytale has appended version 0.7.3, dated Oct 21, 2026, to the living "HOTFIXES: UPDATE 7" page that already carried 0.7.1 on 13 October and 0.7.2 on 14 October. Three hotfixes in nine days for a chapter that shipped on 12 October. It is also the largest of the three, and nobody was told. The page byline still reads "Posted by Hytale Team", "October 12, 2026", and the /news index does not list the 0.7.3 section. We will not guess at why; what is observable is that the version heading is the only field on the page that changed. The release docs at docs.hytale.com now read Release 0.7.3, while pre-release.docs.hytale.com still reads 0.7.0-pre.5, so this is a shipped build rather than a branch. Hytale Hotfix 0.7.3 Patch Notes in Full: 16 Bullets, Seven Sections Seven sub-headings: Stability, Joining & Connecting, World Settings, UI & Quality of Life, Performance, Server and Modder-Facing Fixes. The three bullets that matter most to server owners come first here, not in page order. Hytale 0.7.3 Adds SentryDsn: Server Error Reporting in Your Own Project The first Server Fixes bullet is the most useful line Hytale has published for server owners since launch: Server owners can send error reports to their own Sentry project with the new SentryDsn key in config.json. If the key is not set, nothing changes. A blank value turns error reporting off. Singleplayer worlds ignore the key. And from the Modder-Facing section, the half that makes it worth acting on: If a server sets SentryDsn, errors from third-party plugins also go to that Sentry project. This includes plugin load failures, event listener failures, and errors a plugin logs at SEVERE with a cause. Read those together. SentryDsn in config.json is not just a crash pipe for the server binary: it captures plugin load failures, event listener failures and anything a plugin logs at SEVERE with a cause. On a modded server that is the difference between a player saying "it broke" and you having a stack trace with a timestamp. Nobody who leaves the key alone gets a behaviour change. That is the whole of what the notes say, and the whole of what we will tell you: no Sentry walkthrough, no guess at where your config.json lives. The actionable part is narrow. The key exists, the opt-out is explicit, and a plugin failing quietly can now fail where you will see it. Hytale glibc 2.28: The QUIC Library Floor Drops From 2.38 The second Server Fixes bullet is short and matters to anyone choosing a host: The QUIC networking library in the game and server now runs on Linux systems with glibc 2.28 or newer. Before, it needed glibc 2.38. Context, carefully: glibc 2.28 is an older requirement than 2.38, so the set of Linux systems that qualify gets larger. That is as far as we go. We are not listing which distributions cleared 2.38, because we have not tested any of them on 0.7.3, and we do not know when the 2.38 floor arrived. Checking your own host takes one command: run ldd --version and read the number. If you ruled out a host or an older Linux image over this, that is a reason to re-test rather than assume. Our Chapter 1 server preparation checklist is the place to pick the work back up. Hytale 0.7.3 Joining Server Fixes: Eight Bullets, One Week After the Launch Mess Yesterday we published a piece on players being unable to join servers. The next day Hytale shipped the largest joining section of any hotfix so far. We cannot claim the two are connected, but the overlap is hard to miss. The single Stability Fixes bullet changes what a failed join looks like: Fixed a crash when the game received a bad packet from a server, or ran out of memory while reading from it. You now see the "Failed to connect to server" screen instead. Some share of launch-week crash-to-desktop reports should now surface as the failure screen instead. That is a better outcome, and a reporting change: a player who said "the game closed" will now say "failed to connect" for the same event. Our failed to connect guide covers what that screen tells you. Then the Joining & Connecting Fixes section, all seven bullets verbatim: Joining a server no longer hangs for 20 seconds and then fails when a packet is lost while connecting. Fixed a rare failed join when the game renewed its connection certificate at the same moment you joined a server. Fewer lag spikes and stalls while friends join and load chunks in a world you host, especially on Wi-Fi and home routers. Connections stall less on slow or busy upload connections. Connections over IPv6 reach full-size packets sooner. On Linux, connections over IPv6 now use full-size packets instead of staying at the minimum size. Linux connections also no longer lose packets after the network reports an outdated size limit. Joining a friend's world is more reliable when the host's connection details arrive late. Three observations. The 20 second hang is the most recognisable: one lost packet during connect meant a long wait and then a failure, the exact pattern reported as "the server is down" when the server is fine. The Linux IPv6 bullet is the heaviest technically, since minimum packet size is a throughput problem rather than a connect problem. And the certificate race is called rare, so updating will not clear a failure that hits every attempt. Hytale 0.7.3 Shows Custom Banners for Featured Servers in the Server List One bullet, under UI & Quality of Life Fixes: Featured servers in the server list now show their custom banners. Server images also appear right after the game starts, without a new search or filter change. Significance in one sentence: the in-game server list is now a place where a banner does work, which makes server art a discovery asset inside the client and not only on listing sites. We cover that angle in a separate piece today. Hytale 0.7.3 Performance, World Settings and Modder-Facing Fixes Performance Fixes is a single bullet, specific about hardware: World generation uses fewer CPU threads in singleplayer on PCs with 4 processor threads, and on servers with 4, 6 or 7 processor threads. Exploring new terrain causes less lag on these machines. Note the exact counts: 4, 6 or 7 threads on servers. If your box has 8 or more, this is not your machine. If you run a small VPS it probably is, and the claimed effect is less lag while players explore, not faster generation. World Settings Fixes, one bullet: The Durability Loss % On Death setting now applies to new worlds with every Inventory Penalty On Death option. Before, it only took effect with Partial Drop. The words "new worlds" are doing work there. On an existing world with a non-Partial Drop penalty, the bullet does not promise your durability loss percentage starts applying retroactively. Modder-Facing Fixes, two bullets beyond the Sentry one already quoted: The Node Editor now saves whole-number world generation fields as integers. Before, it saved some of them as decimals, but the server expects integers. The Offset position provider now accepts decimal values for its OffsetX, OffsetY and OffsetZ fields. The first is a type mismatch between authoring tool and server, the kind of bug that produces a config the server rejects for reasons that look nothing like the cause. The second goes the other way: Offset takes decimals now for OffsetX, OffsetY and OffsetZ. What Hytale Server Owners Should Do About 0.7.3 Update. Half the bullets touch joining, connecting or stability, and none lists a workaround. Decide on SentryDsn. The default is safe, but a modded server with unexplained failures now has a way to capture them. Re-check glibc if it blocked you. Compare ldd --version against 2.28 rather than 2.38. Re-test joining from a bad connection. The Wi-Fi, slow upload and IPv6 bullets describe client-side conditions, so a wired test from your desk proves little. Watch the version heading, not the byline. The byline has been wrong since 12 October and the index missed this release entirely. What We Have Not Verified About Hytale 0.7.3 We have not tested 0.7.3. Every bullet above is read from Hytale's hotfix page, not reproduced. We do not know which Linux systems newly qualify. Only that 2.28 is a lower floor than 2.38. We have not configured SentryDsn live. We cannot say what the reports contain or how plugin errors are tagged. We cannot measure the joining fixes. There are no before and after figures; "fewer" and "less" are the actual words. We do not know why this went out quietly, and we are not predicting when another hotfix lands or what is in it. If you track Hytale releases by scraper, webhook or feed, this is the third time in nine days that the version heading was the only field telling the truth. A monitor watching bylines, feed timestamps or the news index saw nothing at all while the biggest of the three hotfixes shipped.