Hytale Update 8 Will Break the WorldGen V1 Work to Add Proper Modding Support: Slikey Is Moving WGV1 to the Asset System Now

Hytale Update 8 is going to break the WorldGen V1 work that is happening right now, deliberately. Tech Director Slikey said on 26 September 2026 that he is currently moving WorldGen V1 to the asset system, and that for Update 8 the team will probably break all of that in order to properly add modding support to V1 and allow additions of content. It is the only post in the thread that attaches a version number to Hytale WorldGen V1 modding, and we have not seen one attached anywhere else. One caveat before anything else. These are posts on X, not patch notes, not documentation and not a blog post on hytale.com. Nothing on hytale.com mentions Update 8 at the time of writing, there is no release note or developer blog behind any of this, and nobody here has tested a line of it. What Slikey Said About Update 8 and the Hytale Asset System The post is a reply to the modder Hatsuya, who had just shown a WorldGen V1 mod biome test. We have trimmed the leading "@HatsuyaDev" handle prefix from the quote below so it reads cleanly; nothing else about it is altered, including the double full stop: Don't get too attached.. I am currently moving WGV1 to the asset system and I think for Update 8 we will break all of this to properly add modding support to V1 and allow additions of content. Slikey, Tech Director, 26 September 2026, 00:38 UTC. The post he is answering, from Hatsuya on 25 September 2026 at 22:42 UTC, was this: Who needs V2 when you can go back to basics and integrate your biome directly into the game world? 😎 (WorldGen v1 Mod Biome Test)#Hytale #HytaleModding The context is worth holding on to. A modder had got a custom biome working inside WorldGen V1 without waiting for V2, and the Tech Director's first response was that it is worth not getting too attached to it, because the ground underneath it is moving. How This Differs From Our 29 September WorldGen V1 Article We covered this thread on 29 September in Hytale WorldGen V1 stays moddable. That piece is built on the later replies: that V1 mods will be able to add biomes, caves, prefabs and entirely new zones, that the $Versions folder system found in the source code is being dropped, and that V1 is still planned for eventual abandonment. This article is about the root post of that same thread, which the earlier piece does not quote. Two things in it are new on the record: WorldGen V1 is being moved to the asset system right now. "I am currently moving WGV1 to the asset system" is present tense and first person. It is work in progress, not an intention. Update 8 is named as the point where that work gets broken. The later replies describe what V1 modding will eventually be able to do. The root post is the only one in the thread that attaches a version to when the groundwork arrives. Read as a whole, the thread says four separate things: V1 modding is coming, it is being built by routing WorldGen V1 through the asset system, Update 8 is where Slikey expects it, and the current in-progress state is not something to build against. Each of those sentences comes from a different post. None of them is a patch note. Why Hytale WorldGen V1 Mods Still Matter: Chapter 1 Runs on V1 It would be easy to read "don't get too attached" as a sign that V1 is already a dead end. It is not. Chapter 1 arrives on 12 October 2026 and runs on WorldGen V1, which is the premise of our WorldGen V1 versus V2 piece on existing worlds and of the portal answer in WorldGen V2 and old worlds. Co-founder Simon Collins-Laflamme confirmed that incidentally on 30 September, replying to a summary post from the @HytaleAlerts account: @HytaleAlerts We are LOCKED IN! I'm currently doing a legit new world run and suffering through the wgv1 and old crafting lol Simon Collins-Laflamme, 30 September 2026, 23:04 UTC. We are using that for one narrow purpose: it indicates that WorldGen V1 and the old crafting system are still what a new world gets in the run-up to Chapter 1. We are not reading anything else into it, and the capitalisation of "LOCKED IN" is his. What This Does Not Tell Us Being precise about the gaps matters more here than filling them, because the post is short and the temptation to extrapolate is large. Update 8 is not a commitment. Slikey wrote "I think for Update 8", which is an expectation from the person doing the work rather than a scheduled deliverable. It could move. There is no date. No date, month or timeframe for Update 8 appears anywhere in the post, and we are not inventing one. Chapter 1 and version 0.7 land on 12 October 2026, and nothing ties Update 8 to any particular point after that. "Break all of this" is not explained. He does not say what breaks, for whom, or what a mod author would have to change afterwards. The nearest referent in the sentence is the WorldGen V1 work he is doing himself, not any named existing mod. "The asset system" is not defined in the post. We are not going to define it on his behalf. Taken at face value, WorldGen V1 is being expressed through the asset system rather than staying where it currently sits, and that is as far as the text goes. Nothing says V1 worlds are affected. The subject throughout is WorldGen V1 as a system, and the content and mods built on it. No post in this thread says existing V1 save data is involved, in either direction. It does not change the eventual plan for V1. Slikey said elsewhere in the same thread that V1 is still to be abandoned eventually. Modding support in Update 8 and eventual abandonment are both on the record and do not contradict each other. What Server Owners and Modders Should Do With This These are our suggestions rather than studio guidance, and the honest headline is that this is a planning input, not a task list. Nothing here is urgent. Do not start a long WorldGen V1 worldgen mod project on the strength of today's internals. "Don't get too attached" was aimed at precisely that, and it was addressed to someone who had just got a custom biome working. Keep going if the project is small, exploratory or a way to learn the system. Hatsuya's biome test is the kind of work that teaches you how V1 fits together, and Slikey did not tell him to stop. Mark worldgen mods separately in your own notes. If a break lands in Update 8, the parts of a server most likely to need attention are the ones touching world generation, not the economy, permissions or chat plugins sitting beside them. Change nothing for 12 October. Chapter 1 runs on WorldGen V1 and Update 8 is not part of it. The work that matters for launch day is in our Chapter 1 server preparation checklist, and the final preview build situation is covered in no pre-release on 8 October. Budget for a rewrite rather than a patch if you are planning a worldgen mod for after Update 8. That is our inference, not his words. "Break all of this to properly add modding support" reads like a deliberate reshaping of the surface mods attach to, and the cheaper assumption is that code written against the current in-progress state will not carry over. Wait for the first real documentation. Nothing about Update 8 or V1 modding support exists on hytale.com. Whenever it appears, that is the version worth building against, not a reply on X. The Bottom Line on Hytale Update 8 and WorldGen V1 Modding Two facts, both from a single post. WorldGen V1 is being moved to the asset system now, and Update 8 is the point at which the Tech Director expects that work to be broken on purpose so V1 can take proper modding support and new content. For most server owners that changes nothing this month. Chapter 1 arrives on 12 October 2026 on WorldGen V1, and the launch details are in our Chapter 1 release date coverage. For anyone aiming at worldgen modding specifically, the message from the person writing the code is to treat whatever you build against today's V1 as temporary, and to expect the real modding surface to arrive later, in a shape nobody outside the studio has seen. Running a server for Chapter 1? List it on HytaleCharts so players can find it on launch day.