Hytale Update 8 Pre-Release: Server Networking, World Saves and Breaking Mod Changes

Release status: October 29 preview, not a stable release

The official Update 8 patch-note page was first published October 22 and received a Part 2 section dated October 29. Hytale directs testers to Launcher, Settings, Pre-Release, and asks for bug reports labeled pre-release. It does not provide a confirmed stable rollout date in those notes.

That distinction matters for communities running persistent worlds. Do not move a production server onto a testing branch merely because an optimization or security fix is listed in a preview. Confirm your host's available build, the client version players use, and the mod versions supported by their authors.

World saves, memory and disk activity are changing

The October 29 notes say worlds write substantially less data when saving, clean shutdowns leave less residual save data, and restarts no longer replay the entire save log. They also address a server out-of-memory condition when exploring new terrain. These are targeted improvements, not a published guarantee of a specific RAM reduction or higher player capacity.

RocksDB's write-ahead-log cap falls from 512 MB to 128 MB, and the log and SST levels use zstd compression. The developer says existing worlds can still open without a migration for this storage change. The 128 MB figure describes the WAL cap, not a new total world-size or server-memory limit.

Before comparing performance, measure the same world, player count, and exploration activity on each build. Preserve a full copy of saves and configuration even when an individual storage-format change is described as compatible.

Dedicated-server networking and join reliability

Update 8 Part 1 notes say dedicated servers now start using the quiche-based transport rather than the previous Netty default, with a fallback on platforms without the native library. Part 2 addresses connection attempts that hang, Windows-hosted disconnects under network pressure, clock-related failures, and rare authentication-certificate timing problems.

The update also fixes inbound packet watchers and filters registered through PacketAdapters not firing on the QUICHE transport. That is especially important for custom networking or moderation plugins: verify that filtering actually works, rather than assuming a successful server startup proves compatibility.

Record the transport shown in startup logs and test real client joins, reconnects, latency, and plugin packet handling. If your host uses a managed launch configuration, consult its instructions before changing transport flags.

Some worldgen packs and plugins require changes

The Part 1 notes explicitly say legacy worldgen v1 JSON assets no longer load: packs still using the older v1 format or modifiers must be rebuilt with typed assets. Several plugin API methods and fields were removed or replaced, so an older compiled plugin may fail until its developer updates it.

Part 2 adds further server API changes, including a new abstract getUsersInGroup method for custom PermissionProvider implementations. Asset-load-order failures now stop startup with a named MOD_ERROR rather than continuing without loaded packs. Check both your worldgen assets and server plugins before switching builds.

Global event state moves from universe/events.json to universe/resources/GlobalWorldEvents.json, with migration on boot. The notes warn that older servers do not read the new file. If you need to roll back, restore a pre-upgrade copy of the world rather than relying on the migrated files to behave identically on an older build.

A specific certificate-trust hardening change

Part 2 rejects TLS chains using eight eMudhra intermediate CA keys described by the Hytale team as compromised in October 2026. Its CertificateTrustPolicy is installed before plugins and HTTP clients start, covering standard Java JSSE connections; custom SSL contexts and native TLS stacks are outside that stated coverage.

This is an outbound certificate-validation safeguard, not proof that Hytale dedicated servers were breached, nor a substitute for operating-system updates, credential security, or reviewing plugins. Server owners who integrate external HTTPS services should test their plugin connections and examine certificate errors rather than disabling certificate checks.

What Hytale server owners should do now

Keep a tested production backup of world saves, permissions, configuration, asset packs and installed plugins. Clone the environment to a staging server if you want to try Update 8, and make sure testers use a matching pre-release client.

Check whether any installed mod uses legacy worldgen v1 assets, removed API methods, custom permission providers or packet filters. Test startup, player permissions, joining and reconnecting, world event progress, saves, clean restarts and recovery from a backup. Compare memory, CPU and disk activity using repeatable scenarios.

Wait for the official stable release announcement and compatible hosting images before scheduling a public maintenance window. Treat the current notes as subject to change during testing, and communicate that status to players.

A couple more questions

Keep reading