Dragonwilds platform fall after Commander Zilyana teleports you? Jagex says hotfix 1.0.1.3 targets that specific problem in RuneScape: Dragonwilds. The useful checks are your platform’s rollout, your installed build and, for hosted worlds, whether the dedicated server has restarted.
The October 23 developer announcement identifies the affected encounter as the Regicide Quest/Scorned Wilderness Raid. A separate October 24 announcement confirms Xbox availability. These are targeted patch notes, rather than evidence that every fall, crash or connection error has the same cause.
Dragonwilds platform fall: check the rollout first
Jagex named PlayStation, Steam, Epic Games Store and Jagex Launcher in the initial release announcement. It gave the update identifier as CL254097, Juicy-Yellowjacket. Xbox arrived in the follow-up announcement.
PC Game Pass was still awaiting approval in the initial post. The later Xbox message does not separately name PC Game Pass, so it does not establish that platform’s rollout. Check the latest official notice and the update actually offered by your own launcher before treating another platform’s announcement as confirmation.
This distinction matters when comparing results with friends. A fix available to a Steam player may not yet be installed on a console or another PC storefront. The platform name and build are more useful than simply saying everyone has updated.
Check the client and the dedicated server
- Record the platform and installed version. Compare the update offered by your launcher with Jagex’s 1.0.1.3 announcement. Keep the build identifier with any notes about the fault.
- Complete the available client update. Close the running game before checking your launcher for it, then reopen the updated game.
- Check the world host. Jagex explicitly says dedicated servers need to restart to apply this hotfix. If someone else manages the server, establish its update and restart status before repeating the encounter.
- Verify the same encounter. Check the platform reached after Zilyana’s teleport in the named quest or raid. Record whether the platform fall persists there; a different location is a separate symptom.
For a dedicated world, confirm the server process restarted, rather than only the connecting player’s game. A client relaunch is a different event and does not establish that the hosted server applied the hotfix.
Keep the existing world and character intact while checking versions. The announced remedy is the update, with a dedicated-server restart where applicable. These notes do not describe a world conversion or a save-recovery procedure.
Why crossplay may still be unavailable
The initial announcement also says crossplay is unavailable while platforms are on different patches, and returns once the relevant platform updates. A missing crossplay connection during this rollout therefore needs a version comparison before broader network troubleshooting.
Jagex separately said Nintendo Switch 2 would be off crossplay for the weekend while Nintendo verified the patch. That statement does not confirm a completed Switch 2 release. Recheck the developer’s current notice before organizing a mixed-platform session.
If the Dragonwilds platform fall continues
Keep a short record of the client build, platform, host type, server restart status and the exact teleport stage. This makes it possible to distinguish a remaining instance of the named bug from an unrelated fall or a mismatched server.
Save corruption is a different issue from this encounter fix. Our earlier Dragonwilds save-corruption coverage describes an older patch and should be read in that dated context.
Next step: compare your platform and server with the official Dragonwilds platform fall hotfix scope, then check the Xbox follow-up if that is your platform. Rollout statements checked October 24, 2026.
