Hytale Update 6 Releases August 27 — The Server Owner's Launch-Day Checklist

Update 6 goes stable on Thursday 27 August 2026 — one week from today. If your server is still on the current build when your players' clients update, it will not be slow, or laggy, or partially broken. It will be unjoinable, because the Hytale protocol rejects a client whose hash does not match the server's exactly. There is no grace period in the shipping code, and the server's own auto-updater will not rescue you either, because the setting that would apply an update unattended ships turned off. That last sentence is the reason this article exists. Almost everything written about Update 6 so far has been about what is in it. This is about the twenty minutes of work that decides whether your server is online on the 27th or dark. What Was Actually Announced — And Where The confirmation came from the verified @Hytale account on 17 August 2026 at 18:19 UTC. In full: "Update 6 releases August 27 📢Mod Browser, Hardcore Mode, new Creative Tools, and so much more!Note to Modders/Server Operators: please check the warnings and bug fixes to ensure you are prepared. 🛠️" Read the third line again, because it is unusual. Hypixel Studios does not normally use a release announcement to tell operators to go and read the breaking-change notes. They did this time. Treat that as the signal it is. Now the honest part about sourcing. As of 20 August 2026, that date exists on X and nowhere else we can find. The news archive at hytale.com/news/archive/2026/8 returns "No posts found for this month". The blog has published nothing since 29 July. The front page carries no banner, no countdown and no date, and neither does the download page. If you have been searching hytale.com trying to work out whether the 27th is real, that is why you have come up empty — it is real, it is just not on the website yet. We also want to flag our own stale coverage rather than quietly leave it up. Our earlier piece on when Update 6 goes stable was written when no date had been announced and says exactly that. It has now been superseded by the 27 August confirmation above. What has not been announced is equally worth knowing. The tweet names four things — Mod Browser, Hardcore Mode, new Creative Tools, and "so much more". There is no published stable changelog yet. The most complete public picture of Update 6 remains the pre-release patch notes page, whose newest section is Part 12, dated 13 August 2026. There is no Part 13. If Update 6 ships on the 27th with Part 12 as the final pre-release, that is a fourteen-day gap between last notes and launch, and anything that changes in that window will not be documented until the stable notes land. Why 27 August Breaks Unprepared Servers The mechanism is documented plainly in the Hytale Server Manual, under Protocol Updates: "The Hytale protocol uses a hash to verify client-server compatibility. If hashes don't match exactly, the connection is rejected." And, listed explicitly as a current limitation: "Client and server must be on the exact same protocol version. When we release an update, servers must update immediately or players on the new version cannot connect." Three consequences follow, and they are worth stating separately because operators tend to only think about the first one. There is no partial failure mode. A version mismatch is not degraded service. It is a rejected connection, for every player, from the moment their client updates. You do not control the timing — your players' launcher does. The client updates when it updates. Your window is not "sometime on the 27th"; it is "before the first player's client pulls the new build". An offline server is a delisted server. If you are in the in-game Server Discovery catalogue, a listing disappears once heartbeats stop for more than two minutes, and returns automatically when they resume. A long, messy update window is visible to strangers as absence. We covered that mechanic in the Server Discovery listing guide. Is relief coming? Yes — but not for this update. The same manual section lists, under "Coming Soon", "Protocol tolerance allowing ±2 version difference between client and server. Server operators will have a window to update without losing player connectivity." That is described as future work, not as current behaviour, and nothing in the Update 6 pre-release notes says it has shipped. Plan for the strict rule. The Auto-Update System Nobody Has Read Here is the part that surprises people. Hytale servers have shipped with a built-in updater for a while: the server checks for new versions on a timer, downloads them to updater/staging/, and can apply them. Most operators know this exists in the vague way one knows a fire extinguisher exists. What they do not know is the default. From the manual's config.json reference, the Update block and its documented defaults: Enabled — true — "Enable automatic update checks" CheckIntervalSeconds — 3600 — "Seconds between update checks" NotifyPlayersOnAvailable — true — "Notify players with permission when an update is available" Patchline — null — "Override the update patchline (defaults to the build's patchline, usually release)" RunBackupBeforeUpdate — true — "Run a full server backup before applying an update (requires backup directory to be configured)" BackupConfigBeforeUpdate — true — "Backup config files (config.json, permissions.json, bans.json, whitelist.json) before applying" AutoApplyMode — Disabled — "How to auto-apply staged updates" AutoApplyDelayMinutes — 30 — "Minutes to wait before applying in Scheduled mode" Read the defaults as a sentence and the trap becomes obvious. Checking is on. Downloading is on. Notifying is on. Applying is off. A stock server will happily discover Update 6, pull it into staging, tell your operators about it — and then sit on the old build indefinitely, rejecting every player who updated, while its log quietly says an update is available. The three AutoApplyMode values, verbatim from the manual: Disabled — "Never auto-apply. Requires manual /update apply --confirm" WhenEmpty — "Apply automatically when no players are online" Scheduled — "Apply after AutoApplyDelayMinutes even with players online, warning them periodically" Which one should you pick for 27 August? It depends on whether you will be at a keyboard. WhenEmpty suits a server with genuine quiet hours — a 4 a.m. lull becomes your maintenance window without you setting an alarm. Scheduled suits a server that is never empty, since a busy server under Disabled stays broken until a human notices. And Disabled is right if — and only if — you intend to run the update by hand and be present when it lands, which for a large community with a mod list is defensible. What is not defensible is leaving it on Disabled by accident because you never opened the file. One caveat you should take seriously. The manual revision we are quoting was last updated on 15 June 2026 — before the Update 6 pre-release cycle finished. These are the documented defaults as of that revision, not a statement about Update 6 specifically. Open your own config.json and read the Update block with your own eyes rather than trusting a table in a blog post, including this one. And a second, sharper caveat: config files "are read on server startup and written to when in-game actions occur", and "Manual changes while the server is running are likely to be overwritten". So edit config.json with the server stopped. Editing it live is how operators discover, several hours later, that their carefully chosen AutoApplyMode reverted itself. The Update Commands Worth Knowing Before You Need Them All of these are documented in the manual. Learn them this week, not at 9 p.m. on the 27th: /update check — check for available updates /update download — download the available update to staging /update download --force — download even if already on the latest version, "useful for bootstrapping the update layout" /update apply --confirm — apply the staged update; backs up files, then shuts down with exit code 8 /update cancel — cancel and delete the staged update /update status — show current version and update status /update patchline [name] — show or set the update patchline /update setup — write the wrapper scripts to the parent directory Two more facts from the same section that will save somebody a bad evening. Updates can be disabled entirely via the HYTALE_DISABLE_UPDATES environment variable — worth checking if your host sets it for you and you have never looked. And the updater has a hard structural requirement: a game/ directory containing Assets.zip, start.sh/start.bat and a Server/ folder, with the server started from inside Server/. If that layout is not detected, the update checker disables itself. Silently. Anyone who unzipped a server into a flat folder two updates ago has been running without an updater ever since and does not know it. Exit Code 8, and Why "The Server Does Not Restart Itself" This is the single most misunderstood piece of the whole system, and the manual is blunt about it: "The server does not restart itself. When an update is applied, the server shuts down with exit code 8. The wrapper scripts included with the server detect this exit code and apply the staged files before restarting." In other words, the update is a two-part act. The Java process stages the files and then deliberately dies with a specific status code. Something outside the process has to notice that code and do the second half: "The wrapper script detects exit code 8, loops back to the start, applies the staged files (selectively replacing only server binaries and assets while preserving config, saves, and mods), and starts the server again." So if you are not launching through start.sh or start.bat, exit code 8 is just a shutdown. This is where custom setups get hurt. A hand-rolled systemd unit, a Docker entrypoint that runs java -jar directly, a panel with its own supervisor, a screen session started from a one-line command — every one of those can stage an update perfectly and then leave the server on the old binaries, or restart it in a loop, or stay down. If your host or your own tooling replaced the wrapper, you own the exit-code-8 handling now. Test it before the 27th, not during. The other half of the wrapper's contract cuts the opposite way, and it is a genuinely good design decision: "The scripts only restart on exit code 8 (update). Any other exit code (normal shutdown, crash, etc.) stops the loop." A crash does not become a restart loop. That is correct behaviour, but it means a bad update leaves you down rather than flapping — you will notice, but only if you are looking. The wrapper also does post-update crash detection with a 30-second window, printing rollback instructions pointing at the backup directory if the freshly updated server dies almost immediately. If you would rather not meet that message cold, our crash recovery and config guide is the companion read. A server left on the old protocol after launch day: still standing, still patrolled, nobody able to get in. An official Hytale screenshot of a Zone 2 desert ruin. What Breaks for Plugins and Mods Updating the server binary is the easy half. The harder half is that Update 6 carries a protocol bump and a substantial pile of API removals, and a plugin compiled against the old server will not simply carry over. The blunt statement is in the Part 10 notes of 30 July 2026: "Plugins and custom servers must be rebuilt against the new protocol to connect, because the protocol CRC changed." Part 10 also removed the ClientPlaceBlock packet outright, routing block placement, the eraser and place-mode selection through PlaceBlockInteraction and its new subtypes. Part 12 then removed several more things a real plugin might depend on. The ones most likely to bite a server operator rather than only a developer: The whitelist changed shape. "The HytaleWhitelistProvider has been removed. The whitelist now runs on the hytale.server.join permission, and the whitelist commands grant and revoke it. If you have an existing whitelist.json it will migrate to whitelist.json.migrated." If you run a whitelisted or application-only server, this is a migration you should understand before it happens, not after — our whitelist and access control guide covers the permission-based model. Command permissions changed. "canGeneratePermission has been removed, so a command that overrode it to return false must call requireNoPermission() instead." The HytalePermissions constants also moved from String to PermissionQuery. A core world-access interface is gone. "The BlockAccessor interface is removed. Every member now lives on WorldChunk, which was its only implementor." Anything typed BlockAccessor becomes WorldChunk. The packet API narrowed. Part 12 removed Packet.serialize(ByteBuf), the generated validateStructure(ByteBuf, int) methods, the ByteBuf helpers on PacketIO, and ValidationResult from the server protocol API, with validation now running during the read and throwing ProtocolException on malformed data. Ban handling collapsed into one type. AbstractBan, InfiniteBan and TimedBan become a single codec-stored Ban, with new BanProvider and BanStorageProvider hooks for plugins that want to own storage. That is a summary, not the migration. We wrote the full version separately: the hytale/3 protocol and API breaking-changes migration guide is where the class-by-class detail lives, and it is the right link to send to whoever maintains your plugins. The Part 11 notes are worth a skim too if you skipped that week. Will My Hytale Mods Work on Update 6? Here is where we have to be careful, because the honest answer is "probably not immediately, and nobody official has said so". What we can report is an observation rather than an announcement. Checking CurseForge's Hytale section on 20 August 2026, the game-version filter offers exactly two options — "Early Access" and "Version 0.5" — against a catalogue of roughly 6,300 projects. There is no Update 6 or 0.6 filter yet. Read literally, that means essentially the entire published mod catalogue targets 0.5.x. It is a filter-menu observation, not a statement from CurseForge or Hypixel Studios, and filters usually appear when a version ships rather than before it. But combined with the Part 10 CRC line, the practical expectation is clear: every server-side plugin that touches the protocol needs a rebuild, and mod authors cannot publish an Update 6 build against a version tag that does not exist yet. You will also see the community wiki's Update 6 page quoted on this, stating that the protocol version moved from hytale/2 to hytale/3 and that clients and servers on the old version cannot connect. That matches the official notes, but it is a community wiki and not a primary source, so we would rather you cite Part 10's CRC line and the Part 1 protocol bump directly. The operational upshot: your mod list is your critical path, not the server binary. Updating the server takes minutes. Waiting for six plugin authors to ship 0.6 builds can take days, and a server that updates its binary but keeps a folder full of incompatible mods may simply fail to start — Part 12 notes that the server now stops outright when a core plugin fails to load, set up or start, "rather than running on in a broken state". If you have never audited your mod folder, our mod install and management guide is the place to start. The Launch-Day Countdown Checklist Today — 20 August (one week out) Confirm your folder layout. Does the parent directory hold Assets.zip and start.sh/start.bat, with the server running from Server/? If not, the updater is already disabled and nothing else on this list will work. /update setup writes the wrapper scripts if you are missing them. Run /update status and /update check. Confirm the updater actually responds, and note which patchline you are on with /update patchline. Open config.json with the server stopped and read the Update block. Decide Disabled, WhenEmpty or Scheduled deliberately. List every plugin and mod you run, with its author and its source. This list is your real launch dependency. 21–24 August Verify your backups exist and restore. RunBackupBeforeUpdate defaults to true but the manual notes it "requires backup directory to be configured". A backup setting that points nowhere is not a backup. Test exit code 8 handling on a staging box. If you run systemd, Docker, or a panel, prove that a code-8 exit results in a restart. A five-minute test now is the difference between a ten-minute outage and a three-hour one. Contact your mod authors, or check their repos. Ask one question: will there be an Update 6 build on day one? Their answers determine whether you update on the 27th or run a reduced mod set. Stand up a pre-release test server if you have the capacity, and try your mod list against it. Our pre-release testing guide covers keeping a test server on a separate patchline from production. 25–26 August Tell your players. A pinned Discord message saying "the server will be down for updates on the 27th" converts an outage into maintenance. Silence converts it into "is this server dead?" Freeze changes. No new plugins, no config experiments, no world edits you have not backed up. You want exactly one variable changing on launch day. Take a manual backup you control, stored somewhere that is not the server. Include config.json, permissions.json, bans.json and your world saves. Read Part 12's modder-facing section if you have not, particularly the whitelist migration. If you run a whitelist, that file is going to become whitelist.json.migrated. 27 August — launch day Watch for the update rather than assuming a time. No launch hour has been published. /update check is your source of truth. Update the server before you update your own client, so you can still connect to test. Apply, then watch the first 30 seconds. That is exactly the window the wrapper's post-update crash detection covers. A crash inside it points at the update, and the backup directory is where the rollback lives. Bring mods back incrementally. Start with a clean boot, then add plugins in small batches. A server that stops on a failed core plugin gives you a clear error; a server with twenty mods added at once gives you a mystery. Re-check your listings. Confirm your Discovery heartbeat resumed and that your entry on the server list shows online again. FAQ When does Hytale Update 6 come out? 27 August 2026, a Thursday. The date was announced by the verified @Hytale account on X on 17 August 2026. As of 20 August it has not appeared on hytale.com — the August news archive returns no posts, the blog has published nothing since 29 July, and neither the front page nor the download page carries a date or countdown. No launch time of day has been published either. Will my Hytale server stop working when Update 6 releases? Yes, for anyone on the new client. The Hytale Server Manual states the protocol uses a hash to verify client-server compatibility and that if hashes do not match exactly, the connection is rejected. It further lists as a current limitation that client and server must be on the exact same protocol version, so servers must update immediately or players on the new version cannot connect. Protocol tolerance of ±2 versions is listed as future work, not current behaviour. How do I update my Hytale server? Through the built-in updater, if your install has the required layout. Run /update check, then /update download, then /update apply --confirm. Applying backs up files and shuts the server down with exit code 8; the wrapper script (start.sh or start.bat) detects that code, applies the staged files from updater/staging/ while preserving config, saves and mods, and starts the server again. If you are not launching through the wrapper, you must handle exit code 8 yourself. What does AutoApplyMode do, and what is the default? It controls how staged updates get applied, and the documented default is Disabled — "Never auto-apply. Requires manual /update apply --confirm". The other options are WhenEmpty, which applies automatically when no players are online, and Scheduled, which applies after AutoApplyDelayMinutes even with players online while warning them periodically. Note that the manual revision documenting these defaults dates from 15 June 2026, so check your own config.json rather than assuming. What is Hytale server exit code 8? It is the status code the server exits with when an update is ready to be applied. The manual is explicit that the server does not restart itself: it stages the files, exits with code 8, and the wrapper script detects that code, applies the staged files and restarts. The wrapper only restarts on code 8 — any other exit code, including a crash or a normal shutdown, stops the loop. Custom launchers, Docker entrypoints and systemd units that run the jar directly will not perform the second half unless you implement it. Will my Hytale mods work on Update 6? Server-side plugins that touch the protocol will not work until they are rebuilt. The Part 10 pre-release notes of 30 July 2026 state that plugins and custom servers must be rebuilt against the new protocol to connect because the protocol CRC changed, and Part 12 removed further API surface including BlockAccessor, HytaleWhitelistProvider and several packet-serialisation methods. As an indicator rather than an announcement, CurseForge's Hytale version filter on 20 August 2026 still offers only "Early Access" and "Version 0.5" across roughly 6,300 projects, so treat your mod list as the long pole in your update plan. Why can't I find the Update 6 release date on hytale.com? Because it is not there. The confirmation is a post on the official X account only. The hytale.com news archive for August 2026 reports no posts for the month, and the most recent blog entry is from 29 July 2026. The pre-release patch notes page is still the fullest public description of Update 6, and its newest section is Part 12 from 13 August 2026. Is there a Part 13 of the Update 6 pre-release notes? No. As of 20 August 2026, Part 12 dated 13 August 2026 is the newest section on the pre-release patch notes page. Whether a Part 13 lands before the 27th is unknown; if it does not, expect the stable release notes to be the first documentation of anything that changed in the final fortnight. Should I set AutoApplyMode to WhenEmpty before launch day? It is a reasonable choice for a server with genuine quiet hours, since it applies the update the moment the world is empty without anyone needing to be awake. Scheduled suits a server that is never empty. Disabled is only right if you plan to run the update by hand and will be present when it lands. Whichever you choose, edit config.json with the server stopped — the manual warns that config files are read on startup and that manual changes made while the server is running are likely to be overwritten. What This Means If You Run a Hytale Server Five things, in order of how much trouble ignoring them causes. Open config.json today. Not because we have told you what to set, but because the default is AutoApplyMode: "Disabled" and a default that requires a human is only as reliable as the human. Decide it on purpose. Prove your wrapper handles exit code 8. The server stages an update and then deliberately exits. If nothing is watching for that code, your update finishes as an outage. This is the failure that will catch the most operators on the 27th, because it catches exactly the people who built a nicer launcher than the default one. Treat your mod list as the critical path. The protocol CRC changed, plugins must be rebuilt, and the catalogue on CurseForge still shows 0.5 as the newest targetable version. Updating the binary is the fifteen-minute part. Getting your plugins back is the week-long part, and it starts with asking their authors this week rather than next Thursday. Tell your players before the day. A server that vanishes without warning loses people who assume it closed; one that announces a maintenance window keeps them. Your Discovery listing goes quiet either way — the difference is entirely in what your community was told. And keep the sourcing straight. The 27 August date is from the official X account and nowhere else right now. The protocol and updater behaviour is from a manual last revised on 15 June. The mod-compatibility picture is our reading of a CurseForge filter menu, not a statement from anyone. We would rather hand you that with the seams showing than dress it up as certainty — and if the stable notes on the 27th contradict any of it, the stable notes win.