Hytale Shipped Four Unreleased Biomes for Something Called Adventure 1.0, and They Are Hidden in the First Modder Patch Notes It Has Ever Published Separately

Here is the line, in full, from an official Hytale post published on 12 October 2026. It sits in the world generation section of a post most people will never open, under a heading of its own. Drifting Plains Added the Drifting Plains region with four biomes: Plains Hills, Plains Gorges, Plains Trork and Plains Oak. These are reachable only through the instances command and will make up part of Adventure 1.0. Read that twice. Four named biomes have shipped in the build you downloaded yesterday. You cannot reach them through normal play, only through a console command. And they belong to something called Adventure 1.0, a name that has never appeared in a Hytale announcement, a patch note, a developer post or anywhere in our own archive of more than 200 articles. That is the story. The rest of this article is where it came from, what Adventure 1.0 is not, and what else in the same post matters if you run a server. Hytale Split Its Modder Patch Notes Out for the First Time On 12 October 2026 Hytale published two posts about a minute apart. The one everybody read was the Chapter I launch post, which we cover in our piece on the Chapter 1 patch notes. The other is this: Modder-Facing Patch Notes (UPDATE 7), at hytale.com/news/2026/10/modder-facing-patch-notes-update-7, bylined "Posted by Hytale Team October 12, 2026", in the Modding Updates category. The RSS feed at hytale.com/rss.xml dates it Mon, 12 Oct 2026 11:08:54 GMT, one minute ahead of the Chapter I post at 11:09:54 GMT. This is the first standalone modder-facing patch notes post Hytale has published. We did not take that on trust. We pulled hytale.com/sitemap-0.xml, which lists 293 URLs covering the whole site, and filtered every slug containing "modd", "patch-notes" or "hotfix". modder-facing-patch-notes-update-7 is the only entry of its kind. For Update 5 and Update 6 the modding changes lived inside update-5-patch-notes and update-6-patch-notes. There is no modder-facing-patch-notes-update-5 or -update-6. If you maintain a mod or a plugin, that matters practically: the place to watch has changed, and the Modding Updates category is now a separate feed of its own. What Adventure 1.0 Is Not A new milestone name invites guessing, so here is the boundary drawn as tightly as the evidence allows. "Adventure 1.0" appears exactly once in the post, in the sentence quoted at the top. The post does not define it, date it, or mention it again. We searched our own archive for the phrase and found zero occurrences. We also checked "Adventure Mode", which does appear in our coverage, and that is a different thing entirely: Adventure Mode is an existing play mode, not a release milestone. Do not conflate them. It is also not either of the two roadmap items we have already covered: Not Update 8. We covered Slikey explaining that Update 8 is not Chapter 2, and his warning that Update 8 will break worldgen v1 and the asset system. Neither mentions Adventure 1.0. Not Chapter 2. We covered the crafting rework and companions slated for Chapter 2. Again, no mention. What the name suggests, and we are labelling this as inference rather than reporting, is a version number attached to a mode rather than to the game. Hytale's early access is structured in chapters, and Simon has said it will run six or seven chapters before 1.0. A "1.0" attached to the word Adventure reads like a finished state for one mode. We do not know that, nobody has said it, and we are not going to build a roadmap out of one line. The Four Biomes, and Why They Are Reachable at All The four names are Plains Hills, Plains Gorges, Plains Trork and Plains Oak. Three of those are self-describing. The fourth is not: Trorks are an existing Hytale creature faction, so Plains Trork implies a populated region rather than terrain alone. They are gated behind "the instances command", which is a development and debugging route rather than a feature. That phrasing is doing real work. The studio did not say these biomes are coming, or teased, or planned. It said they are in the build and reachable by command. Shipped but hidden is a normal way to stage content, and it is also the reason the line exists at all: the audience for this post is mod authors who will find the biomes in the asset tree and need to know what they are and whether to build on them. The answer to that last question is in the same section, two lines earlier, and it is a warning: The Prefabs/Orbis folder holds work in progress for V2 world generation. It is less stable than the rest of the prefabs folder, so expect changes. So: do not build a mod that depends on these. The surrounding context is the V2 world generation migration we have been tracking, including the tree prefabs being copied so they can be edited safely: "Copied most trees from the legacy Prefabs/Trees folder into Prefabs/Orbis/Trees. You can now use and update these trees in V2 biome prototypes without affecting V1 world generation." If you are new to that split, our guide to worldgen v1 versus v2 on existing worlds and the world gen v2 graph system guide cover the ground. Our reporting on Slikey confirming v1 stays moddable is the context for why this folder separation exists. Server Operator Changes Nobody Announced This is the part that earns the post a read if you run a Hytale server. None of the following appeared in a launch announcement, a social post or the Chapter I changelog. All of it is quoted verbatim. A new /wilderness debug command Server operators can now check which chunks the wilderness system counts as wilderness and which count as home. The new /wilderness debug [enabled] [player] command tints those chunks green and red on one player's world map and draws matching cubes in the world. Wilderness tracking stays off by default in WildernessConfig, and the command warns when a world has it turned off. Note the default: tracking is off unless you turned it on. If you have been wondering why wilderness behaviour seemed inert on your server, that is the first thing to check. World events are now toggleable per world World events can now be switched on and off per world with /worldevent enable, which takes true or false and toggles when you leave the argument off. The WorldEvents plugin stores an EnableWorldEvents flag in a new WorldEventsWorldConfig, and new Creative worlds get it set to false. Creative worlds defaulting to off is the detail to carry forward. We documented the command itself in the world events server config guide, and this adds the per-world flag and the Creative default to it. Two more command changes The /eventtitle command takes --style in place of --major, and the secondary line now defaults to empty rather than to "Event". Added a /beam command for development work, with entity, position, spawn and clear. If you have automation or a plugin passing --major to /eventtitle, it needs updating. Portal worlds gained an opt-in leave button Portal worlds can now offer a Leave Portal button on the map. It is off by default and needs the new leave button flag set on the PortalType asset. This pairs with the command rename in the Chapter I notes, where /portal replaces /fragment and /leave becomes /portal leave. BuilderTools and the Asset Editor BuilderTools gained two limits on how much world a single edit loads up front, PrefetchColumnLimit (default 1024) and PrefetchSectionLimit (default 10240). An edit over either limit reads what is already in memory and reports the rest as skipped. A large selection that used to churn through chunk loading will now report part of the edit as skipped instead. That is a behaviour change, not just a safety valve, and it is the sort of thing that looks like a bug the first time it happens to you. What We Had Already Covered In the interest of not selling you consolidated material as a scoop, several of the most quoted items in this post were already in the five Update 7 pre-release parts we covered between 3 September and 1 October, and we have written them up before: The server refusing to boot from the launcher install folder, with exit code 11 and the --allow-install-dir escape hatch. Covered in our Update 7 server plugin breaking changes piece. The MaxViewRadius clamp, now "clamped in memory with a warning" for values outside 1 to 32, with the command rejecting anything above 32 "instead of 512". Background in the maxViewRadius guide. BlockedRootInteractionTags in GameplayConfig.WorldConfig, which we covered when it appeared in the pre-release notes. The ContextPrecision setting on the Runtime node, part of worldgen V2 managing context size dynamically. One genuinely useful item we had not written up: "Bans and kicks now close every connection an account has open, including Asset Editor connections that previously remained connected." If you run a server with the Asset Editor enabled, a banned account previously kept that connection. Worth knowing, and it pairs with the whitelist and access control guide. What We Have Not Verified We have not loaded the Drifting Plains biomes. We have not run the instances command, seen the terrain, or confirmed the four biomes are complete rather than stubs. Everything above is read from the post. We do not know what Adventure 1.0 is. One sentence in one post is the entire public record. We have not seen a date, a scope or a second mention. We do not know the exact instances command syntax. The post says "the instances command" without giving its form, and we have not found it documented on either docs site. We have not read every line of the post to you. It runs to roughly 100 sub-headings, including about 30 "For Plugin Developers" sections on block reads and writes, chunk lookups, cubic worlds, the ECS, the ability system and Noesis UI. If you write plugins, read it directly at hytale.com/news/2026/10/modder-facing-patch-notes-update-7. If you are running a server through this update, the sequence we laid out in the Chapter 1 server preparation checklist still applies, and you can list your server on HytaleCharts through the server discovery guide.