Hytale Pre-Release Worlds and Mods Missing After Switching Back to Release? Here Is Exactly Where They Went

It goes like this. You have been running the Update 6 pre-release since June. You built a base, you collected a modpack, you tuned your settings exactly how you like them. Update 6 went stable this morning, so you open the launcher, turn the pre-release toggle off, load the Release build — and the world list is empty. No mods. Settings back to defaults. Three months of play, apparently gone. Nothing has been deleted. Take your hands off the keyboard before you reinstall anything. The Short Answer Your pre-release worlds, mods and settings are still on your disk. They are in a different folder, and the Release build does not look in it. Since a launcher change that shipped with Update 5 in May 2026, each patchline keeps its own data directory. The Release patchline reads %HYTALE%/UserData/. The pre-release patchline reads %HYTALE%/data/pre-release/. Switching patchlines does not move anything — it points the game at a different folder. Everything you did on pre-release is sitting in the pre-release directory exactly as you left it, and everything the Release build shows you is whatever was in UserData/ the last time you played on Release. That is the whole problem and the whole answer. The rest of this article is the detail: what the change actually says, the one sentence in it that almost every write-up skips, how to bring your pre-release progress across to Release safely, and what the same principle means if you run a dedicated server. Why This Is Happening Today Specifically On Monday August 17, 2026, at 18:19 UTC, the verified @Hytale account posted: "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. 🛠️" One note on timing, because we would rather date our claims than leave them floating: Update 6 went stable on Thursday August 27, 2026. Hytale published two posts that morning — HOTFIXES: UPDATE 6 at 09:55 GMT and the full Update 6 Patch Notes at 10:00 GMT. This article is not a write-up of what shipped: we cover the release itself in our Update 6 stable patch notes breakdown, and the run-up in our Update 6 release date explainer. What follows is about one specific consequence of the switch that the patch notes do not mention at all. What matters for this article is the behaviour on your machine, and that is already true today. The pre-release patchline has had its own data directory since May. The moment a large group of people stop using that patchline — which is what a stable launch causes — that directory becomes invisible to them, all at once. What Actually Changed: The Update 5 Launcher Split This is documented in exactly one place. The Update 5 patch notes, posted May 26, 2026, carry a section headed "QUICK NOTE ON LAUNCHER & DATA STORAGE CHANGES". Quoted exactly: "Game data storage has been updated. Previously all Hytale game data (e.g. worlds, mods, settings, and logs) was stored in %HYTALE%/UserData. A launcher update will change this behaviour to the following: * The Release patchline will continue using %HYTALE%/UserData/ * Non-release patchlines will now use their own directories under %HYTALE%/data/ * For example, Pre-release files will now be found within %HYTALE%/data/pre-release/" Read the scope of the first sentence carefully: "worlds, mods, settings, and logs". This is not just save games. Your installed mods, your keybinds and video settings, and your logs all follow the same rule. That is why the symptom looks so total — it is not that your worlds are missing while everything else survived. It is that the game is reading an entirely different data root. Note also that the rule is general, not a one-off for Update 6. "Non-release patchlines will now use their own directories under %HYTALE%/data/" means every future pre-release cycle behaves this way. Update 7's pre-release will do the same thing to you next time unless you know it is coming. We covered this change when it shipped, as one item among many in our Update 5 Part 8 write-up — but we framed it there as a convenience for people who want to run both branches side by side, which is how the patch notes present it. That framing is correct and it is also exactly why nobody remembers it three months later. Nobody searches for "run both branches side by side". They search for "hytale worlds gone". The Sentence Almost Everyone Misses: Duplicate, Not Move The same section contains a second passage, and it is the key to the whole thing: "Existing non-release patchlines will automatically duplicate existing worlds, mods, and game settings to the new location. Once migrated, patchlines will no longer share data." Duplicate. Not move. When the split landed and you were on pre-release, your existing data was copied into the new pre-release directory. The originals stayed where they were, in UserData/. And then: "Once migrated, patchlines will no longer share data." From that moment on the two directories diverged. Every session you played on pre-release wrote to the pre-release copy only. Nothing you did there touched UserData/ at all. Which gives you three quite different situations, and it is worth working out which one you are in before you touch a single file. If you only ever played on Release Nothing has happened to you. Your data has been in UserData/ the whole time and still is. You can stop reading and go and enjoy the update. If you opted into pre-release and kept playing there This is the big group, and the good news is genuinely good: you have two intact copies of your world as it existed when you switched, plus everything you have done since, and neither has been destroyed. Your old Release worlds are sitting untouched in UserData/ — frozen at the moment you opted in, because nothing has written to them since. Your current, up-to-date worlds are in data/pre-release/. The world list you are staring at right now, the one that looks wrong, is the UserData/ copy. It is not empty because your saves were wiped. It is showing you a snapshot from months ago — or nothing at all, if you never played the Release build before opting in. If you started fresh on pre-release If you only ever built on the pre-release patchline, there is no Release copy of that work, because there was never anything in UserData/ to duplicate. Your world exists in exactly one place: %HYTALE%/data/pre-release/. Treat that folder accordingly, and copy it somewhere safe before you start moving things around. Where Your Hytale Files Actually Are Two roots, and it is worth being precise about what the patch notes do and do not tell you. Release patchline: %HYTALE%/UserData/ — documented, quoted above. Pre-release patchline: %HYTALE%/data/pre-release/ — documented, quoted above. Other non-release patchlines: their own directories under %HYTALE%/data/ — documented as a general rule, with pre-release given as the worked example. What the patch notes do not spell out is what %HYTALE% resolves to on your machine. They use the placeholder throughout and never expand it, so we are not going to assert an exact path as though it were documented. What we can say is that the usual Windows install location puts the Hytale data root under %AppData%\Roaming\Hytale\, which is the path our own older modding guides have long used for UserData/Mods/. Treat that as the usual location rather than a guarantee, and confirm it for your own install — the launcher knows where it put things, and opening the folder from the launcher or the game rather than typing a path from a blog post is always the safer move. Inside the two roots, the sensible expectation — and we are labelling this as inference, because the notes do not enumerate the layout — is that the pre-release directory mirrors the structure of UserData/, since it was created by duplicating it. The reliable way to confirm that is to open both folders side by side and compare. It takes ten seconds and it beats guessing. Everything you built on pre-release is still on disk. The Release build is simply reading a different shelf. A general official Hytale screenshot, not a screenshot of the launcher change. How to Bring Pre-Release Worlds and Mods Back to Release The mechanism is unglamorous: you copy files from one directory to the other. There is no in-game import button documented anywhere, and we are not going to invent one. Back up first — this is not boilerplate Before you move anything, copy the entire %HYTALE%/data/pre-release/ directory somewhere outside both roots — another drive, a zip on your desktop, wherever. If you started fresh on pre-release, that folder is the only copy of your work in existence, and the failure mode of a careless drag-and-drop is not "the game shows an error", it is "the folder is now in the wrong place and something has overwritten it". Do the same for UserData/ if there is anything in it you care about, because the whole point of this exercise is that you are about to write into it. Server operators already know this reflex; if you want the longer version of the argument, our guide to rollbacks and backups makes the case at length. The steps Close the game and the launcher completely. Copying save data out from under a running process is how you turn one problem into two. Take the backups described above. Both directories, somewhere neither patchline will touch. Open both roots side by side — %HYTALE%/UserData/ and %HYTALE%/data/pre-release/ — and compare the layouts before you move a thing. Copy the worlds you want across from the pre-release directory into the matching location under UserData/. Copy, do not move, until you have confirmed the result loads. Deal with name collisions deliberately. If the same world name exists in both, you have the old Release snapshot on one side and your current pre-release save on the other, and only you know which is which. Rename rather than overwrite. Do mods separately and deliberately. Do not bulk-copy a mods folder from a pre-release build into a stable one and hope. Take them one at a time, checking each is built for the stable release. Our guide to installing and managing Hytale mods covers the sane way to do this. Start the Release build and check before you delete anything from the pre-release directory. Ideally, do not delete it at all — disk is cheap and that folder is your rollback. What might not come across cleanly Be realistic about the fact that you are moving data between two builds of a game, not between two folders on equal footing. Mods are the obvious risk. A mod compiled against the pre-release API is not automatically valid on the stable build. The Update 6 pre-release run removed and renamed public API repeatedly, and the network protocol version was bumped from hytale/2 to hytale/3 right at the start of the run, in the Modders Warning Section of Pre-Release Part 1 — clients and servers on the previous protocol version cannot connect. If you maintain anything that touches that surface, our hytale/3 protocol breaking-changes guide is the relevant read. For everyone else, the practical rule is simply: add mods back one at a time, not all at once. World data has its own considerations. Worlds carry generation data, and moving a world between builds is a category of operation that has bitten Hytale players before — we wrote up the whole question of what happens to existing worlds across a generator change in our WorldGen V1 vs V2 explainer, and the same instinct applies here: back up, then test, then trust. Settings are the least risky and the least valuable. If your keybinds do not come across, re-entering them takes two minutes. Do not risk a save file for a settings file. Dedicated Server Operators: Same Principle, Different Directory The split quoted above is a launcher behaviour. It governs the data root the game client uses when you switch patchlines. It does not reach out and relocate a dedicated server installation that you unpacked into a directory of your own choosing. But the principle that bites you is the same one, and it bites harder, because a server has more state to lose. If you have been testing Update 6 by running a second server install against the pre-release client, then you have two server directories with two sets of world and player data, and today is the day you decide which one is authoritative. Nothing merges them for you. Our Hytale server setup guide documents universe/ as the directory holding world and player save data on a dedicated server, alongside your mods and config. We are deliberately not going to enumerate a full directory tree here, because layouts vary with how you deployed and we have not verified yours. Check your own install, identify where world data, mods and configuration actually live for it, and back up all three before you touch anything today. The rest of launch-day operations — updating in the right order, checking that plugins load, watching the first joins — is a separate job with its own sequence, and we have written it out in full in our Update 6 launch-day checklist. One thing worth flagging from the pre-release run: Part 13 Hotfix 1, dated August 22, changed how player-hosted joins negotiate connections, using ICE with STUN and TURN. That is a client-side joining change and it has nothing to do with your data directories, but it is the most recent pre-release build and worth knowing about before people start reporting connection oddities that are not yours. For the record, and because we get asked every week: as of today there is no Part 14 and no Hotfix 2. The newest section on the pre-release patch notes page remains Part 13 Hotfix 1 from August 22. "Pre-Release Worlds Are Usually Wiped" — Correcting a Widely-Cited Claim If you searched for this problem before you found us, there is a good chance you read that your pre-release progress was never going to survive in the first place. One well-ranked guide, in its FAQ under the question "Does my progress in Pre-Release carry over to the live game?", states: "Pre-release worlds and character data are for testing purposes only. These are usually wiped or reset when the official update goes live." That page is dated March 29, 2026. The launcher change is dated May 26, 2026. The advice predates the change that invalidated it by two months, which is a completely ordinary thing to happen to a guide and not a reason to be smug about it — our own coverage of the same change, published the same week, buried it as a side note. But it is wrong now, and it is wrong in a way that causes real damage, because a player who believes their pre-release worlds were wiped will not go looking for the folder they are sitting in. Worse, they may well delete it while "cleaning up" after a version switch. Here is the precise correction, and note how carefully it is bounded. The official notes establish that patchlines no longer share data and that pre-release files live in their own directory. So the right statement is: your pre-release worlds are not deleted when the stable build arrives — they are in a directory the Release build does not read. What the notes do not say is anything about how long that directory persists, or that pre-release data is guaranteed never to be cleared under any circumstance. We are not making that claim and neither should anyone else. "Not wiped by switching patchlines" is a factual statement about the documented behaviour. "Safe forever" is not, and if you want your pre-release world to be permanent, the way to make it permanent is a backup you control, not an assumption about someone else's launcher. FAQ Where are Hytale pre-release worlds saved? Under %HYTALE%/data/pre-release/. The Update 5 patch notes of May 26, 2026 state that "Non-release patchlines will now use their own directories under %HYTALE%/data/" and give the worked example: "Pre-release files will now be found within %HYTALE%/data/pre-release/". The Release patchline continues to use %HYTALE%/UserData/. The notes do not expand what %HYTALE% resolves to on your system, so confirm the root through your launcher rather than trusting a path from a guide. My Hytale worlds disappeared after Update 6 — are they gone? Almost certainly not. If you had been playing on the pre-release patchline and you switched back to Release, the Release build is reading %HYTALE%/UserData/ while your recent progress lives in %HYTALE%/data/pre-release/. Nothing was deleted by switching. Look in the pre-release directory before you reinstall anything, and take a copy of it as soon as you find it. Does Hytale pre-release progress carry over to the stable release? Not automatically, and not because it was destroyed. The patch notes are explicit that "Once migrated, patchlines will no longer share data" — so work done on pre-release stays in the pre-release directory and does not appear on Release. Bringing it across means copying the files yourself, with a backup taken first. Why does Hytale have a UserData folder and a data/pre-release folder? Because a launcher update shipped with Update 5 gave each patchline its own data root, so that a stable client and a pre-release client can coexist on one machine without their worlds, mods and settings colliding. Before that change, everything shared %HYTALE%/UserData. The upside is that you can run both branches; the downside is the symptom this whole article is about. Were my Release worlds overwritten while I was on pre-release? No. The patch notes say existing non-release patchlines "will automatically duplicate existing worlds, mods, and game settings to the new location" — duplicate, not move. Your Release copies stayed in UserData/ and stopped changing the moment the split took effect, which is why they look like a snapshot from months ago rather than your current save. How do I move my pre-release world to the Release build? Close the game and launcher, back up both data roots, then copy the world folder from %HYTALE%/data/pre-release/ into the matching location under %HYTALE%/UserData/. Copy rather than move, rename instead of overwriting when a name already exists in both, add mods back one at a time rather than bulk-copying a pre-release mods folder into a stable build, and confirm the world loads before you delete anything. Do I lose my mods when I switch off the Hytale pre-release patchline? You do not lose them, but the Release build will not see them, because mods are covered by the same split — the patch notes list "worlds, mods, settings, and logs" as the data that moved. Reinstall or copy the mods you want on the stable build, checking each one is built for it. A mod compiled against the pre-release API is not automatically valid on stable. Will this happen again with the Update 7 pre-release? Yes, on the documented behaviour. The rule is written generally — non-release patchlines get their own directories under %HYTALE%/data/ — so the next pre-release cycle will produce the same split, and the same surprise, unless you go in expecting it. The habit worth forming now is simple: whenever you switch patchline, assume you are switching data root as well. Can I still run an older version of Hytale? The same Update 5 patch notes carry a section headed "LAUNCHER NOW SUPPORTS OLDER VERSIONS", stating: "We also now support older versions of the game via our launcher for an extended period of time". That is useful context here, because it means going back to a build to retrieve or verify something is a supported path rather than a hack. The notes do not define how long "an extended period of time" is, so do not treat it as indefinite. What to Do Today Four things, in order. Find the folder before you conclude anything. Open %HYTALE%/data/pre-release/. In almost every case the panic ends there, because everything is visibly present and correct. Back it up immediately, before you start tidying. Especially if you built on pre-release from scratch, because then that folder is the only copy that exists. The single most damaging thing you can do today is delete a directory you have decided is redundant. Move worlds first, mods second, settings last. Worlds are irreplaceable, mods are re-installable, settings take two minutes to redo. Spend your care accordingly. If you run a server, work out which install is authoritative before anyone joins. Two parallel installs with two sets of world data is a fine way to test and a terrible way to launch. Pick one, back it up, and run the rest of the day off the launch-day checklist. Beyond today, the useful takeaway is the general one. Patchlines are separate data roots, permanently and by design, and that is a good design — it is what lets you test an update without risking the world you actually play in. It only feels like data loss because the change was documented once, in a quick note, in a patch post from May, and then never mentioned again. Now you know where to look, and you will know next time too. Once you are running the stable build and your worlds are where you want them, that is the moment to think about who else gets to see them. If you host for a community, listing your server on HytaleCharts puts it in front of players who are looking for exactly what you have built — and launch week, when everyone is on the same version at the same time for the first time in months, is the best window you will get all year. If you are still deciding what your server should be, Hardcore Mode arrived in Part 11 and the Mod Browser landed in Part 12, and between them they have changed what a fresh Hytale server can offer on day one.