RuneScape: Dragonwilds has already shipped its first serious post-launch repair job, and this is one update console players should not treat like background noise.
Jagex released hotfix 1.0.0.4 after reports of world saves becoming corrupted when players exited a session. That specific corruption path is now listed as fixed. Two crash bugs were also addressed. The important catch is that another save-related problem remains under investigation: some players have reported worlds disappearing from their world list or appearing invisible.
That makes this less of a normal patch-note story and more of a practical question for anyone who has spent hours building in Ashenfall: is it safe to play again, and what should you avoid until Jagex closes the remaining issue?
Quick Take
The good news is meaningful. Patch 1.0.0.4 fixes the bug that could corrupt a world save when leaving a game session. Jagex also fixed a crash caused by casting a Fishing Rod at a player-made structure and another crash triggered by parts of the settings menu.
The unresolved issue matters just as much. Jagex says some worlds are still going missing or becoming invisible in the world list. The studio is working with console platform teams to understand the problem and says recovering those worlds may require a future patch and additional verification.
If your world currently loads correctly, the sensible move is simple: install the latest update, exit cleanly to the main menu before suspending or shutting down your console, and keep an eye on Jagex’s official updates before assuming the entire save problem is over.
What Patch 1.0.0.4 Actually Fixes
According to Jagex’s patch notes, the update addresses three concrete issues:
- World saves should no longer become corrupted when exiting a game session.
- Casting a Fishing Rod at a player-made structure should no longer crash the game.
- Changing certain settings should no longer trigger a crash.
That first item is the headline. Survival games ask players to invest time in bases, gear, gathering routes and shared worlds. A save bug is not a cosmetic annoyance. It attacks the thing the entire progression loop is built around.
The Problem That Is Not Fixed Yet
Jagex says it is still investigating reports of worlds going missing or becoming invisible in the world list. The team says it is in active conversation with the console platform holders and wants to help affected players recover those worlds and have them reappear in a future patch.
That distinction matters. Patch 1.0.0.4 fixes one known corruption route. It does not mean every save-related symptom reported since the 1.0 console launch is solved.
Jagex has also been unusually cautious about deployment. In an update to players, the studio said it did not want to rush a patch that might disconnect players from their worlds and create another opportunity for save corruption. That is frustrating if you are waiting on a fix, but it is the right kind of caution when the data at risk is a player’s world rather than a texture glitch.
Crossplay Can Temporarily Be Messy During the Rollout
There is another wrinkle for mixed-platform groups. Jagex warned that the patch rollout can temporarily leave different platforms on different versions. When that happens, crossplay may stop working until the relevant platform has processed the update.
That is especially important for groups split between PC, PlayStation, Xbox and Nintendo Switch 2. If one player suddenly cannot join the shared world after a patch, version mismatch may be the reason rather than the world itself being broken.
What Console Players Should Do Right Now
Before the hotfix, Jagex specifically warned console players not to put their system into rest or sleep mode without first returning to the main menu. The studio linked that behaviour to reports of compromised save data and said protecting worlds was its top priority.
Even with the new hotfix installed, we would keep the cautious routine for now:
- Update the game before starting a session.
- Return to the main menu before putting the console into rest or sleep mode.
- Do not repeatedly force-close the game while it is saving.
- If your world disappears from the list, avoid creating a replacement with the same expectations until Jagex provides recovery guidance.
- If you play with friends across platforms, check that everyone is on the same game version before troubleshooting the server itself.
Why This Matters More After the 1.0 Launch
Dragonwilds left Early Access on September 15 and expanded to PS5, Xbox Series X|S and Nintendo Switch 2 alongside PC. Jagex described the launch as the next stage of the game’s journey after 17 months of development with the community.
That broader audience changes the stakes. Early Access players are often prepared for rough edges. A console player downloading a 1.0 release through Game Pass or PlayStation Plus is much less likely to tolerate the possibility of a long-running world disappearing.
The response therefore matters almost as much as the bug itself. Jagex moved quickly enough to ship a hotfix, publicly separated the fixed corruption issue from the still-unresolved missing-world issue, and avoided pretending the problem was completely solved. That is the transparency players need when progress is at risk.
Should You Start Dragonwilds This Weekend?
If you have been waiting to try Dragonwilds, the game itself has plenty going for it: cooperative survival, RuneScape’s world and skill DNA, building, exploration and a full 1.0 content package across PC and consoles.
But if losing a save would ruin the experience for you, there is nothing wrong with waiting for one more all-clear from Jagex. The main corruption bug has been patched, yet the missing-world investigation is still open. Players who are already deep into a world should be especially conservative with sleep mode, shutdowns and cross-platform version mismatches.
ZerotoBeast Take: this is a much better situation than it was at launch, but it is not a clean bill of health yet. Patch 1.0.0.4 solves the nastiest confirmed corruption path. Now Jagex needs to close the loop on worlds that have vanished from player lists and, where possible, get affected players back into them.
Pingback: RuneScape: Dragonwilds Roadmap: 7 Big Reveals at RuneFest