Hytale Docs Now Pin Release 0.6.8, But the Patch Notes Still Stop at 0.6.6: What Server Owners Can and Cannot Know

Hytale rebuilt both of its documentation sites on Saturday 19 September 2026, and both version pins moved. The patch notes did not move with them. The stable documentation site now pins a build two version numbers ahead of the newest published hotfix notes, and the pre-release site now pins a version number that our own reporting said, three days ago, had not appeared anywhere. This is a short factual story that is very easy to get wrong, so we are going to be pedantic about it. Everything below was re-fetched on the morning of Sunday 21 September 2026. Where we quote, we quote character for character. Where we do not know something, we say so and stop. The Short Version The Hytale docs version pin on the stable branch moved from 0.6.6 to 0.6.8. The switcher on docs.hytale.com now reads <span class="docs-version-label">Release</span><span class="docs-version-number">0.6.8</span>. On 18 September it read 0.6.6. The Hytale pre-release docs pin moved from 0.7.0-pre.2 to 0.7.0-pre.3. The switcher on pre-release.docs.hytale.com now reads <span class="docs-version-label">Pre-release</span><span class="docs-version-number">0.7.0-pre.3</span>. Both javadoc sets were generated on Saturday 19 September 2026, minutes apart, according to their own build stamps. No Hytale patch notes exist for 0.6.7 or 0.6.8. The Update 6 hotfixes page still ends at 0.6.6 from 14 September, and neither string appears anywhere on it. There is no Update 7 hotfixes page. hytale.com has not served a modified page since Friday 18 September 09:28 UTC, so nothing on the site could have quietly gained a 0.6.7 or 0.6.8 section after the docs were rebuilt. The Server API javadoc your plugins are documented against has changed with no changelog. That is the part that has practical consequences. What the Hytale Docs Version Switcher Says Now Both documentation sites carry a version switcher in the header. On the stable site, docs.hytale.com, the markup reads verbatim: <span class="docs-version-label">Release</span><span class="docs-version-number">0.6.8</span> The Server API javadoc served from the same site, at docs.hytale.com/api/, carries the title "Hytale Server API 0.6.8" and this build stamp: Generated by javadoc (25) on Sat Sep 19 03:26:27 UTC 2026 That page also carries <meta name="dc.created" content="2026-09-19">, which is a second, independent statement of the same build date. On pre-release.docs.hytale.com, the switcher reads verbatim: <span class="docs-version-label">Pre-release</span><span class="docs-version-number">0.7.0-pre.3</span> Its javadoc is titled "Hytale Server API 0.7.0-pre.3" and stamped: Generated by javadoc (25) on Sat Sep 19 03:30:25 UTC 2026 Four minutes apart. Both branches were rebuilt in the same pass on Saturday morning. Three days earlier, on 18 September, the stable site pinned Release 0.6.6 and the pre-release site pinned 0.7.0-pre.2. The Hytale Patch Notes Did Not Move The published hotfix notes live on one page, hytale.com/news/2026/8/hotfixes-update-6, titled "HOTFIXES: UPDATE 6". Its byline still reads "Posted by Hytale Team August 27, 2026". The version headings on it, newest first, are: 0.6.6, dated Sep 14, 2026, which we covered in our 0.6.6 joining and connecting write up 0.6.5, dated Sep 10, 2026 0.6.4, dated Sep 7, 2026, covered in our 0.6.4 port forwarding write up 0.6.3, dated Aug 31, 2026, covered in our 0.6.3 NPC shadows write up 0.6.2, dated Aug 27, 2026 0.6.1, dated Aug 27, 2026 We searched that page for the strings 0.6.7 and 0.6.8. Both return zero matches. There is no section for either version, no passing mention of either version, nothing. The obvious next question is whether the hotfix notes simply moved to a new page for Update 7. They did not. The address that would follow the existing pattern, hytale.com/news/2026/9/hotfixes-update-7, returns a 404. No Update 7 hotfixes page exists. The Update 7 pre-release notes page is a separate document and it has not grown either. That page contains exactly three headings: "Pre-Release (Update 7 Part 3)", "Part 2" and "Part 1". There is no Part 4. The byline still reads "Posted by Hytale Team". The dates carried on the page are August 27, 2026, September 3, 2026, September 10, 2026 and September 17, 2026. How We Know Nothing Was Quietly Appended This is the part that turns an observation into a story, and it is worth explaining because the Update 7 notes have twice grown a new section with no announcement. We covered that pattern when it happened, in our Update 7 Part 2 breakdown and again in our Update 7 Part 3 breakdown. A silent append is exactly the kind of thing that could have carried 0.6.7 and 0.6.8 notes past us. It did not, and here is the proof. hytale.com is a static build, and it serves one site-wide last-modified header on every page rather than a per-page one. Today that header reads: Fri, 18 Sep 2026 09:28:21 GMT We verified that the header is identical on the Update 7 pre-release notes page and on the Update 6 hotfixes page. Because it is a single site-wide stamp from a static build, no living page on hytale.com has gained a section since Friday 18 September at 09:28 UTC. The documentation sites were rebuilt the next morning, Saturday 19 September, at 03:26 and 03:30 UTC. So the sequence is: notes frozen since Friday morning, docs rebuilt Saturday morning with a stable pin two numbers higher. The asymmetry is not an inference. It is two timestamps. What We Can Say and What We Cannot We are going to be blunt about the limits here, because this story has an obvious exciting reading and the obvious exciting reading is not supported. What we can say. The stable documentation pin moved from 0.6.6 to 0.6.8, which is a jump of two version numbers. Neither 0.6.7 nor 0.6.8 has any published patch notes. The javadoc titled "Hytale Server API 0.6.8" exists, is live, and was generated on 19 September 2026. What we cannot say. We cannot tell you that a 0.6.7 build shipped to players. The string 0.6.7 does not appear on the notes page, it does not appear in either documentation site, and it does not appear in either javadoc. We have no evidence of a 0.6.7 anything. A version pin skipping a number is not proof that the skipped number existed as a release. We also cannot tell you what is in 0.6.7 or 0.6.8. There are no notes. We are not going to guess, and you should be suspicious of anyone who does. If a fix list for either version turns up, we will cover it the same day. One more boundary, since it comes up every time a version number moves: we are making no claim in either direction about what anyone at Hytale has or has not posted publicly. That was not something we were able to check today, and an unchecked thing is not a finding. Hytale Server API 0.6.8 Against 0.7.0-pre.3: A Package Census Since both javadoc sets are live and both publish machine readable package lists, we counted them. This is a comparison of the two builds as they stand today, 21 September 2026. It is not a diff of what changed this week. There is no archived copy of last week's javadoc to compare against, so nobody can honestly tell you when any of these packages first appeared. Release 0.6.8 lists 1056 packages. Pre-release 0.7.0-pre.3 lists 1078 packages. 25 packages appear only in the pre-release build. 3 packages appear only in the release build. The three that exist only on the stable branch, all prefixed com.hypixel.hytale., are builtin.adventure.objectives.blockstates, builtin.adventure.objectives.events and builtin.instances.hud. The 25 that exist only on the pre-release branch, same prefix, are: builtin.abilities, plus .command, .element, .entity, .interaction, .trigger and .window builtin.adventure.goblinlab builtin.adventure.wilderness.debug builtin.augmentblocks.ui builtin.beam, plus .asset, .command and .interaction builtin.gameflags.integration builtin.npcknockbackdebug builtin.rewards, plus .asset server.core.asset.type.musictransition, plus .config server.core.asset.type.stinger, plus .config server.core.modules.interaction.event server.core.modules.projectile.event server.core.universe.world.chunk.heightmap Read that as a map of how far apart the two branches currently sit, nothing more. A plugin written against a pre-release only package will not compile against the stable Server API today. If you are weighing up which branch to develop on, our guide to testing Hytale pre-release builds covers the trade-off, and our piece on pre-release worlds, mods and missing patchline folders covers where files end up when you switch. Why This Matters for Hytale Server Owners The Server API javadoc is not a marketing page. It is the reference that server owners and plugin developers build against, and it is the thing people check when a method signature stops behaving. The documented API surface on the stable branch has moved to 0.6.8 with no changelog explaining what moved, which means a class page you read last week may not describe the jar you are running this week, and you have no published list telling you which pages to re-read. That is an annoyance for a solo plugin author. It is a genuine operational problem for anyone running a listed server with paying players on it, especially if a managed host updates builds on its own schedule. Our self-hosted versus managed hosting guide goes through who controls the update button in each model, and that is the question to answer first. The checklist for this week Find out which build your server is actually running. Not which build you installed, which build is running right now. If you are on a managed host, ask them directly and get the version number in writing. Pin your server jar version. If your host offers a version lock or a manual update toggle, turn it on. An automatic update onto an unreleased build with no notes is not a risk worth carrying. Do not assume the docs you read last week describe the jar you are running. Re-check any API surface your plugins depend on before you ship a change, because there is no changelog to tell you what to re-check. Back up before you update anything. Stop the server, copy the world directory, store the copy somewhere the live server cannot reach. Keep the Part 3 world format change in mind. The Update 7 pre-release notes state that a world loaded on that build cannot be opened on an older one. If a host auto-updates you onto a pre-release build, that decision is not reversible. Our Part 3 breakdown has the full text. Re-read the breaking changes list if you maintain plugins. Our Update 7 server and plugin breaking changes guide is still the best single migration reference, and our texture atlas limit piece covers the modded content ceiling that Part 3 addressed. A Caveat From Our 18 September Article, Now Retired When we covered Part 3, we were careful to say that the part carried no version number. The exact sentence we published was: Part 3 carries no version number. It is not labelled 0.7.0-pre.3 anywhere, and when we checked, pre-release.docs.hytale.com still pinned 0.7.0-pre.2 while docs.hytale.com still pinned Release 0.6.6. Half of that is now out of date, and we would rather flag it ourselves than leave it sitting there. The pre-release documentation site now pins 0.7.0-pre.3, so the pin half of the caveat is retired. The other half still stands. The patch notes page itself still does not label Part 3 with any version number, and Hytale has not published anything connecting the two. The pin moving to 0.7.0-pre.3 three days after Part 3 appeared is consistent with Part 3 being that version, and it is not a statement that it is. We are recording the pin move, not upgrading it into an announcement. Is a Hytale Update 7 Part 4 Due? Nothing has been announced, and we want to be clear that what follows is our observation of a pattern rather than anything Hytale has said. The three published parts landed on Thursdays. Part 1 is dated 3 September, Part 2 is dated 10 September, and Part 3 is dated 17 September. On that cadence alone, a Part 4 would fall due around Thursday 24 September. That is arithmetic on three data points, not a schedule. We are also not going to read the docs pin move as a signal that Update 7 is close, because a documentation build date tells you when a site was generated and nothing else. No release date has been announced and we are not predicting one. Frequently Asked Questions What is Hytale 0.6.8? It is the version currently pinned by the stable Hytale documentation site and by the Server API javadoc served from it, which is titled "Hytale Server API 0.6.8". Beyond the version number itself, we do not know what it contains, because no patch notes have been published for it. Where are the Hytale 0.6.8 patch notes? There are none. The Update 6 hotfixes page ends at 0.6.6 from 14 September 2026, and the strings 0.6.7 and 0.6.8 do not appear on it. There is no Update 7 hotfixes page either, so there is nowhere else on hytale.com for them to be. Was there a Hytale 0.6.7? We do not know. The stable documentation pin went from 0.6.6 to 0.6.8, so a number was skipped, but the string 0.6.7 does not appear on the notes page, in either documentation site or in either javadoc. We have no evidence that a 0.6.7 build shipped, and we are not going to assert one did. When did the Hytale docs version change? Both javadoc sets carry their own build stamps: "Generated by javadoc (25) on Sat Sep 19 03:26:27 UTC 2026" on the release side and "Generated by javadoc (25) on Sat Sep 19 03:30:25 UTC 2026" on the pre-release side. The release javadoc also carries a dc.created value of 2026-09-19. On 18 September the pins still read 0.6.6 and 0.7.0-pre.2. Is Hytale Update 7 Part 3 version 0.7.0-pre.3? The patch notes still do not say so. What changed is that the pre-release documentation site now pins 0.7.0-pre.3, where on 18 September it pinned 0.7.0-pre.2. That is consistent with Part 3 being that version. It is not confirmation, and Hytale has published nothing linking them. Does the Hytale docs version change mean Update 7 is close? It does not tell you that. A documentation build stamp records when a site was generated. No release date has been announced for Update 7, and we are not going to predict one from a version pin. What should Hytale server owners do about this? Confirm which build your server is running right now, pin your server jar version if your host lets you, re-check any Server API surface your plugins depend on rather than trusting docs you read last week, and take a world backup before any update. If you are on a managed host, make sure it cannot auto-update you onto a pre-release build, because the Update 7 pre-release world format change is one way. How many packages are in the Hytale Server API right now? As of 21 September 2026, the Release 0.6.8 javadoc lists 1056 packages and the 0.7.0-pre.3 javadoc lists 1078. Twenty five packages appear only in the pre-release build and three appear only in the release build. That is a snapshot of the gap between the branches today, not a record of what changed this week. The Bottom Line Two documentation sites were rebuilt on Saturday 19 September 2026 and both moved their version pins. The stable pin skipped a number to land on 0.6.8. The pre-release pin landed on 0.7.0-pre.3, retiring half of a caveat we printed on 18 September. Meanwhile hytale.com has not served a modified page since the Friday morning before, so no notes were appended anywhere to explain either move. We are not going to fill that gap with guesses. What we can hand you instead is a boring, useful instruction: find out what your server is running, stop it from changing without your say-so, and treat the API documentation as something that can move under you without warning until notes for 0.6.7 and 0.6.8 exist. When they do, we will have them up the same day. Running a Hytale server through this stretch? Add it to the HytaleCharts server list so players can find you while the version numbers keep moving.