RuneScape: Dragonwilds World Saves: What Jagex Fixed and How to Protect Yours
1.0.0.8 stopped new world losses and 1.0.1 brought missing worlds back plus compensation for corrupted characters, so here is what still needs a backup.
World saves really did get corrupted after 1.0, and Jagex changed its story three times in three days. On 16 September it confirmed that console rest mode damages saves and asked players to exit to the main menu first. On 17 September it explained why it would not ship an unverified patch. And on 18 September it shipped 1.0.0.4, which fixed corruption caused by exiting a game session.
That was only the start. Two more patches followed, and they are the ones that decided what happened to worlds already gone:
- 8 October, 1.0.0.8 fixed an issue that caused world saves to disappear under certain conditions, and said in the same post that worlds which had already disappeared would stay invisible until 1.0.1
- 14 October, 1.0.1 is the patch Jagex describes as a range of fixes targeting the disappearing world saves, with missing worlds expected to come back and corrupted characters able to join again with aggregated stats and Tier 4 gear as compensation for lost progress
- 15 October, 1.0.1 Known Issues still lists “an issue where some Corrupted World Saves are disappearing for players” among the fixes in progress, alongside a planned hotfix for two other problems
So the honest state of the bug today. The main class of disappearing worlds was addressed in two patches, and previously lost worlds should return. Jagex also said on 14 October that a very small number of players still hit other save issues, and that data is still being collected.
Three things are still in your hands. Exit to the main menu before sleeping the console. Back up the save folder regularly. Keep your main world off modded dedicated servers.
Jagex changed the story three times in three days
| Date | What Jagex said | What it means for you |
|---|---|---|
| 16 September | Confirmed that rest or sleep mode on consoles compromises world save data and can make worlds irredeemably lost; asked players to exit to the main menu first. Warned that a platform left behind on patch verification may be temporarily de-synced from crossplay | Console players should have changed how they stop playing that day |
| 17 September | Still investigating, with leads; not willing to ship a patch that risks disconnecting you from your world again, and working directly with the console platform teams | Do not expect a same-day fix, and do not pile on duplicate reports |
| 18 September | 1.0.0.4 fixed world saves becoming corrupted when exiting a game session, plus the fishing-rod crash and the settings crash. Worlds missing from the world list were still under investigation and needed extra testing | Normal exits became much safer; missing worlds still needed a later patch |
The same batch of notes carried a side effect that is easy to miss. To let every platform finish verifying that patch, Nintendo Switch 2 and the Jagex Launcher were taken out of crossplay. That is a multiplayer limit, covered on platforms and crossplay.
What 1.0.0.8 and 1.0.1 changed
| Date | Patch | What it did for saves |
|---|---|---|
| 8 October | 1.0.0.8 | Fixed an issue that caused world saves to disappear under certain conditions. Worlds that had already disappeared were explicitly not brought back by this patch - it only stopped new losses |
| 14 October | 1.0.1 | A range of fixes “targeting the disappearing world saves”, plus a catch-up mechanic for corrupted characters: they can join worlds again and return with aggregated stats and Tier 4 gear in place of the progress they lost |
| 15 October | 1.0.1 Known Issues | Confirms an incoming hotfix for two problems and lists the rest under “we’ll get these resolved as soon as possible”, including some Corrupted World Saves disappearing for players |
Two operational details from 1.0.0.8 are easy to miss. Dedicated servers have to be restarted before the hotfix applies. And SteamCMD pulls of the patch were being rate limited, which Jagex said it was working through with Shockbyte. A server that “never got the fix” can be a delivery problem rather than a save problem.
The three things to do now
First, exit to the main menu before sleeping or shutting down. This is Jagex’s own advice and the only concrete step it gave console players. Leaving the game running and putting the console to sleep is exactly the scenario the 16 September post names.
Second, copy your save folder somewhere else on a schedule. The Jagex official wiki gives the PC location:
C:\Users\<your username>\AppData\Local\RSDragonwilds\SavedThat folder holds game settings and character data, and you can copy the whole thing to another directory to create a backup. The character save is a .json file containing appearance, play time, inventory, progression, quest progress, revealed landmarks, skills and experience, journal, map pins and unlocked spells. So it is not just a settings file - copying it preserves your current progress.
Third, keep your main world off modded dedicated servers. The 16 September known-issues update lists players joining modded dedicated servers having their saves corrupted as under investigation. Play your long-term world on an official or unmodded host and treat modded servers as experiments.
If you have already lost a world
1.0.1 is the patch that was meant to reverse this, so the first thing to do is launch the game and look at the world list. Jagex’s wording on 14 October is that disappeared world saves “should hopefully be restored”. That is a hope rather than a guarantee, and it is not a promise that your progress comes back with the world.
If a world is still missing, or a character will not load:
- Do not delete local leftovers. Leave the
Savedfolder, and any empty-looking entries in the world list, exactly where they are. - Do not re-grind irreversible progress in that world before checking it. The 1.0.1 recovery path for a corrupted character is the catch-up package, and it replaces your inventory rather than restoring it.
- If the world is back but the character is corrupted, rejoining now means aggregated stats and Tier 4 gear, not the gear you had.
- Report the world if it is still gone. The 15 October known-issues post still has a slot open for disappearing Corrupted World Saves, and that list is how the remaining cases get found.
Why three days was not enough
The bottleneck is platform patch verification. Jagex spelled it out on 16 September: one bug fix means one patch, but the patch has to clear verification on every platform separately, and any platform left behind loses crossplay. So Jagex bundled several fixes together, trading a shorter “no crossplay” window for less risk of a second round of corruption.
That is why 1.0.0.4 could fix session-exit corruption days before the disappearing-worlds work landed.
What is still on the known-issues list
These come from Jagex’s 1.0 known-issues update and from the 1.0.1 known-issues post on 15 October. The ones that touch saves and multiplayer:
| Issue | What it means for you |
|---|---|
| Some Corrupted World Saves are disappearing for players | Still in the 15 October fix list; keep backups and report it |
| Controller cannot skip the “Corrupted Save” warning on the main menu in some cases | Hotfix planned; some players get past it by reconnecting the pad |
| Ranged Special Attacks crash dedicated servers against some targets | Hotfix planned |
| Air Magic Staff combo’s 4th hit deals no damage on-hit | Acknowledged, no date |
| Joining modded dedicated servers corrupts player saves | Keep your main world off modded hosts |
| PlayStation players crash joining some crossplay worlds via invite | Join through the world browser search instead |
| Input delay on Nintendo Switch 2 | A controls issue, not a save issue |
| Server browser search is case sensitive | Search in lower case or by name prefix |
Sources
- Jagex, “PSA: An Update on Save Data and Rest Mode.”: https://redd.it/1whvd3i (16 September 2026)
- Jagex, “1.0 Known Issues List and Update”: https://redd.it/1whtisk (16 September 2026)
- Jagex, “An Update on World Saves”: https://redd.it/1wj0yo6 (17 September 2026)
- Jagex patch notes, “Eye on Ashenfall | 1.0.0.4 Patch”: https://steamcommunity.com/games/1374490/announcements/detail/1844115010495925 (18 September 2026)
- Jagex patch notes, “Our 1.0.0.8 patch is live!”: https://steamcommunity.com/games/1374490/announcements/detail/1846018067929978 (8 October 2026)
- Jagex patch notes, “Our 1.0.1 update is now live! | Eye on Ashenfall”: https://steamcommunity.com/games/1374490/announcements/detail/1846651706673783 (14 October 2026)
- Jagex, “1.0.1 Known Issues”: https://steamcommunity.com/games/1374490/announcements/detail/1846651706678658 (15 October 2026)
- Jagex official wiki, “Backup” (save folder and how to copy it): https://dragonwilds.runescape.wiki/w/Backup
Related pages
Related Articles
release
RuneScape: Dragonwilds Release Date: Early Access to 1.0
The Early Access start date, the 1.0 launch date, what the Scorned Wilderness update added, and which old guides no longer apply.
release
RuneScape: Dragonwilds Dedicated Server: Setup, Player Limit and Config
What the official dedicated server guide actually requires: hosting options, the RAM formula, the current player cap, UDP port forwarding, mandatory config