Jagex’s latest Dragonwilds hotfix fixes several multiplayer issues, but save recovery is still in progress and Edit Appearance has been removed for now.
Image: IGDB
Store links: RuneScape: Dragonwilds on Steam
Hotfix 1.0.0.5 puts stability ahead of character edits
Jagex says RuneScape: Dragonwilds hotfix 1.0.0.5 is live as of September 25, 2026, and its most player-visible change is a temporary removal rather than a new feature: the Edit Appearance button has disappeared while the studio investigates world and character save corruption. In Jagex’s official patch notes, the studio says it is testing methods that may restore missing saves, but those recovery options need more investigation and are not part of this hotfix yet.
That creates an awkward moment for a survival RPG that only recently hit its full 1.0 launch. According to the RS: Dragonwilds wiki’s patch tracker, version 1.0 arrived on September 15, 2026, bringing the game out of Early Access and expanding it to consoles with crossplay. A first post-launch hotfix, 1.0.0.4, followed on September 18 with fixes for corrupted world saves when exiting, a Fishing Rod crash, and a settings crash. The new 1.0.0.5 update is broader, but Jagex is still treating save recovery as unfinished work.
The practical tension is simple: RuneScape Dragonwilds crossplay is available across the 1.0 platform lineup, but every player in a group still has to deal with version matching, host settings, console certification timing, and the current save-safety restrictions. If you are trying to get a mixed-platform party into Ashenfall this week, the best answer is not to remake your world or spam invite codes. First, make sure the host has enabled crossplay, confirm everyone is on a compatible build, and avoid assuming that missing or reset saves are fixed by 1.0.0.5.
How to enable crossplay in RuneScape Dragonwilds
Crossplay in Dragonwilds is controlled by the world host, not by each guest individually. Gamepur’s guide says the host enables it when loading a multiplayer world: open RuneScape: Dragonwilds, select the world, choose to host it, turn on the Crossplay option in the world settings, then load in and open the pause menu to find the Invite Code. Friends can enter that code through the world browser to join. Pocket Tactics reports the same basic flow, noting that the host can use Edit Settings to enable Crossplay and then share the code shown in the pause menu.
The detail that catches many groups is timing. Crossplay is not described by those guides as a universal account toggle that stays outside the world flow. It is a host-side world setting, so if your usual host loads a session without crossplay enabled, a friend on another platform can be blocked even if Dragonwilds itself supports that platform combination. Pocket Tactics also notes that the invite code changes whenever the host reloads the world, so an old code may fail even when crossplay is correctly enabled.
Gamepur reports that crossplay is available between PC, PlayStation 5, Xbox Series X|S, and Nintendo Switch 2, and that PC players can play together whether they own the game through Steam, the Epic Games Store, or the Jagex Launcher. Pocket Tactics likewise lists Nintendo Switch 2, PS5, Xbox Series X|S, and PC as supported crossplay platforms. For readers asking how to enable crossplay in RuneScape Dragonwilds, the shortest reliable answer is this: the host must enable Crossplay while loading the multiplayer world, then share the current invite code or let friends find the crossplay-enabled world in the browser.
One related boundary is worth separating from crossplay. Pocket Tactics reports that RuneScape: Dragonwilds does not support cross-progression or cross-save between platforms. Steam Cloud Save works within the Steam version, according to that outlet, but it does not move progression across PS5, Xbox, Switch 2, or PC storefronts. In other words, crossplay lets characters meet across platforms, but it is not a character-transfer system.
Player-hosted worlds still depend on version parity
The official 1.0.0.5 patch notes make clear that platform update timing can affect online play. Jagex said it shared the notes ahead of the console submission process because console verification was expected to take several days. The studio specifically framed that communication around player feedback that updates had been knocking crossplay offline and said it was trying to avoid a weekend of disrupted gameplay for Nintendo Switch 2 players.
That helps explain why some crossplay failures are not solved by re-sending an invite code. If one client or server is ahead of another, a group can run into a mismatch rather than a permission problem. Shockbyte’s Dragonwilds server guide gives the server-side version of that warning: if Platform Policy is set to Crossplay, some platforms may have delayed updates and may be a version or two behind the latest PC build, producing a mismatch error when the client version does not match the server version.
The previous hotfix cycle shows how fragile that timing can be. The RS: Dragonwilds wiki’s 1.0.0.4 tracker says that after that September 18 patch, Nintendo Switch 2 and Jagex Launcher systems could no longer crossplay until the patch was processed on their respective storefronts. That was reported as a limited pause for those named platforms, not a total collapse of crossplay across all storefronts. Still, it is the kind of platform-gap issue mixed groups should check before changing worlds, characters, or server settings.
For a game built around gathering, crafting, boss attempts, and world persistence, those distinctions matter. A failed join can come from a disabled Crossplay setting, a stale invite code, a platform version mismatch, Xbox privacy settings, a server policy setting, or a genuine save issue. Those are different problems with different fixes. Treating all of them as one generic crossplay bug is how players end up deleting healthy worlds they did not need to touch.
Dedicated servers have their own crossplay rules
Dragonwilds also supports dedicated-server play, and that adds another configuration layer. Shockbyte’s support article says its RuneScape: Dragonwilds servers have crossplay enabled by default. Server owners can change that by stopping the server, opening the RuneScape: Dragonwilds settings file from the Settings area, finding the Platform Policy option, choosing a desired platform, then saving and restarting. Shockbyte specifies that choosing Crossplay allows all platforms to connect.
Pocket Tactics reports that standard online co-op supports up to four players, while dedicated servers increase the limit to six players. It also says dedicated servers require a separate PC or hosting service, and that console players need to join a dedicated server rather than host one themselves. Shockbyte lists a practical hosting warning that crossplay servers can be affected by delayed platform updates, which makes dedicated servers especially sensitive to version matching during hotfix weeks.
Jagex’s 1.0.0.5 notes address a serious dedicated-server edge case: the patch targets an issue where joining a modded dedicated server from consoles could corrupt a player save. MMOHuts’ report on the hotfix summarizes the same fix and states that console players joining modded dedicated servers should no longer risk corrupting their player saves after the update. That is a meaningful distinction from ordinary crossplay. It is not simply a matter of whether a PlayStation, Xbox, Switch 2, or PC player can enter the same world. It is also about whether the server is modded, whether the joining player is on console, and whether everyone is on the corrected build.
If you are running a progression-heavy world with rare drops, raid unlocks, or late-game crafting materials, the conservative choice is to confirm the server build and platform policy before inviting console friends back into a modded environment. Jagex says the corruption trigger tied to modded dedicated server joins has been addressed in 1.0.0.5, but the same official post also says broader save recovery work is still ongoing.
The save recovery issue behind the missing Edit Appearance button
The temporary disappearance of Edit Appearance is the clearest sign that Jagex is prioritizing containment before restoration. In the official 1.0.0.5 notes, Jagex says save corruption affects both world and character saves and that it is testing methods that will hopefully restore missing saves. The studio then explains the immediate mitigation: it is removing the most common cause, so the Edit Appearance button will vanish until the issue is resolved.
That is a blunt tradeoff. Character appearance editing is part of how many RPG players settle into a long-term avatar, especially in a shared-world survival game where a character is tied to hours of gathering routes, combat choices, and base-building progress. But if that button is connected to a common save-corruption trigger, disabling it is the kind of unglamorous systems decision that protects more players while recovery tools are being tested.
Jagex also warns that some restored saves may have had their world settings reset to default. The official notes say Custom or Creative worlds may have reverted to Normal worlds and could appear in Normal save lists. MMOHuts reports the same warning. That means a world that looks misplaced is not automatically gone, and a world that appears under Normal may not represent the settings you originally chose. Before deleting anything, players should check all relevant save lists and look for worlds that may have shifted categories.
The important limitation is that 1.0.0.5 does not claim to recover every missing save. Jagex says it needs longer to investigate solutions and potential recovery options. So the current RuneScape Dragonwilds save recovery status is unresolved: the studio has removed a common trigger, warned players where some restored worlds may appear, and is still testing recovery methods. Players affected by missing saves should not read this hotfix as a completed rollback or full restoration patch.
Multiplayer fixes in 1.0.0.5 narrow the troubleshooting list
The Jagex Dragonwilds update does include several concrete multiplayer fixes that should make crossplay troubleshooting less chaotic. Jagex says users should no longer fail to connect to multiplayer servers with more than two players present. The same note specifically says this resolves Xbox clients being unable to connect if two users were already in the world. The Click’s Xbox-focused report emphasizes that this was separate from normal privacy, invite-code, or crossplay setup problems because Dragonwilds co-op supports groups above that failed two-player state.
For Xbox players, the practical first step is to fully close the game and check for update 1.0.0.5 rather than relying on Quick Resume, as The Click advises. After that, the host should confirm that crossplay is enabled if the group is mixed-platform. Jagex also says 1.0.0.5 adds a notification for Xbox players when Privacy and Safety Settings conflict with going online, which should help separate account restrictions from the now-fixed two-player connection bug.
The patch also resolves a PS5 crash that could occur when creating a crossplay world with a password in certain instances, according to Jagex’s notes. That fix matters for cautious hosts who use passwords to control access to a world browser listing. It sits alongside other online-play improvements, including a tooltip clarifying that the server search bar is case sensitive and a fix for dedicated server owners being unable to edit dedicated server worlds on consoles.
Outside crossplay, 1.0.0.5 touches progression and raid stability. Jagex says AI should now respawn as intended on the second Scorned Wilderness Raid attempt, dying in that raid should no longer skip a respawn point, and the Abyssal Whip recipe should now unlock for users with existing character saves. The patch also makes Primordial Hearts, Imbued Granite Maul Heads, and Chinchompa Skulls destroyable or storable, lets Luminite ore be crafted into Divine Rocks, enables Summon Shelter in the Scorned Wilderness hub, and adds DLSS and FSR upscaling in the Video Settings for Windows and Xbox Game Pass versions. These are secondary to the save issue, but they reduce friction for players trying to continue progression instead of waiting outside the game.
A cautious path for playing crossplay right now
If your group is starting fresh, RuneScape Dragonwilds crossplay is straightforward when every platform is current: have the host enable Crossplay while loading the multiplayer world, enter the world, share the current invite code, and make sure friends use the browser or code flow rather than an expired invite. If you use a dedicated server, confirm that Platform Policy is set to Crossplay and that the server and clients are on compatible versions.
If your group already has a world with meaningful progress, act more carefully. Do not delete or recreate a world simply because someone cannot join, especially while Jagex is still working on save recovery. Check whether the problem is platform certification lag, an old invite code, a disabled host setting, Xbox privacy restrictions, a case-sensitive server search, or a dedicated server policy mismatch. If a world is missing, reset, or appears under an unexpected category, treat that as a save issue rather than a normal multiplayer failure.
For appearance changes, the current guidance is effectively to wait. Jagex removed Edit Appearance because it was tied to a common save-corruption cause, and the studio has not announced when that button will return. The official notes say the team is targeting a later 1.0.1 update for a crash that can happen when disconnecting from internet or Wi-Fi and selecting Play Online, along with unintended keybind remapping. Jagex also says a broader Dragonwilds roadmap is planned for RuneFest the following weekend.
Dragonwilds’ 1.0 launch expanded Ashenfall into a cross-platform survival RPG, but the first post-launch weeks have made one thing clear: world persistence is the system everything else depends on. Crossplay can bring the party together, raids can test the build, and dedicated servers can stretch the group size, but save integrity decides whether any of that progress feels safe. Hotfix 1.0.0.5 is a step toward stability, not the end of the save recovery story.