RuneScape: Dragonwilds "mismatched build": meaning and fix
Written by
Last checked
October 25, 2026
You can see a friend's or public world listed in the Worlds screen, but trying to join it throws a "mismatched build" message — even when every player involved reports being fully up to date. Most reported in cross-platform (crossplay) groups, and when a friend's or rented dedicated server has not yet been updated to the same version as the players' game.
Also appears as: dragonwilds mismatched build, dragonwilds mismatched build error, runescape dragonwilds error mismatched build, dragonwilds cant join server mismatched build, dragonwilds mismatched build 1.0.1, dragonwilds server mismatched build after update, dragonwilds server version mismatch
This is different from a dedicated server that silently vanishes from the Public tab — here you can see the world and get an explicit "mismatched build" message when joining.
The clearest documented case is on the game's wiki: a Switch 2 player joining PlayStation-hosted friends said everyone was up to date, yet only they got the mismatched-build message. A wiki moderator pointed them to the official Discord's bug reports instead of citing a fix — nothing is confirmed yet.
The likeliest explanation is console platforms lagging behind PC in approving a Jagex patch — based on Jagex's own acknowledged crossplay rollout gap elsewhere — but that's a plausible mechanism, not a confirmed cause here.
Dedicated servers: the game and the server have to be on the same build. Jagex's 1.0.1.2 notes (October 23, 2026) say "Dedicated Servers will need to be restarted to apply the hotfix", as its 1.0.0.8 notes did. Restarting did not fix it for the one player we found who tried it repeatedly.
No problems reported in the last 15 minutes.
Is RuneScape: Dragonwilds down right now? Live reports →What to try
- 01Reported
Relaunch the game and restart or update any dedicated server
Make sure the game and the server are on the same build. Have everyone fully close and relaunch the game, and update and restart a dedicated or rented server so it picks up the latest version. Jagex's dedicated server guide says "please make sure your server and clients use the latest version of the game available" and "Shockbyte servers just need to restart to update automatically!". Its 1.0.1.2 notes (October 23, 2026) say "Dedicated Servers will need to be restarted to apply the hotfix", the same line as in its 1.0.0.8 notes (October 8). The 1.0.1 notes (October 14) gave no restart instruction. Two Steam Discussions threads (September 18 and 29) also have players saying a server needs restarting after every update. That this clears the "mismatched build" message itself is not confirmed.
- 02Unconfirmed
Restarting the host's server did not fix it for one player
In the r/RSDragonwilds thread "Mismatched build" (40 comments), a replier said restarting the server on the host's website would "auto upload the update". The original poster later wrote "I've restarted several times over and it's still happening". No Jagex reply was visible.
- 03Confirmed
SteamCMD server updates were being rate limited at 1.0.0.8
If you update a self-hosted server with SteamCMD, Jagex's 1.0.0.8 notes say "SteamCMD updates pulling the patch into Dedicated Servers are being rate limited", and that it was working with Shockbyte on "a more permanent fix". The 1.0.1 notes do not say whether this still applies, so an update that has not arrived yet may simply be waiting.
- 04Confirmed
Check whether every platform has processed the latest patch
If this happens in a cross-platform group, check whether every platform involved has actually finished processing the latest patch. Jagex said in its 1.0.0.4 notes that Switch 2 and Jagex Launcher players "will no longer be able to crossplay until the patch has been processed on their respective platforms", and for 1.0.0.5 it expected console verification to "take several days". Whether that produces this exact message isn't stated.
- 05Confirmed
Patch status as of October 25, 2026
From Jagex's Steam announcements. 1.0.0.4 (September 18): Switch 2 and Jagex Launcher crossplay offline until the patch is processed on those platforms. 1.0.0.5 (notes posted September 23, targeting that Friday): "Users no longer fail to connect to Multiplayer servers with more than 2 players present", including Xbox clients; we found no post confirming its go-live day. 1.0.0.6 (September 29): "Epic Games Store players are now back online and can enjoy Crossplay again!" 1.0.0.7: a Jagex Steam post on October 1 says it was "being processed on platforms"; we could not read an official go-live post. 1.0.0.8 (October 8): live on Xbox, PS5, Epic Games Store, Steam, Jagex Launcher and Nintendo Switch 2, with dedicated servers needing a restart. 1.0.1: announced on Steam on October 14, 2026 as "now live"; the post names no platforms and gives no restart or mismatch instruction. 1.0.1.2: announced on Steam on October 23, 2026 as "now live", with "Dedicated Servers will need to be restarted to apply the hotfix"; the post names no platforms.
- 06Confirmed
Compare the server's version in its logs with your game's version
Jagex's dedicated server guide says to "use the logs to ensure that the version it runs matches the one your game does", and that this is "likely to happen any time an update or hotfix is released". The server's version is at the top of its logs; your game's version is in the top left corner of the game. If they differ, update and restart the server (or wait for your platform to get the patch). Console patches go through platform verification that Jagex expected to "take several days" (1.0.0.5 notes), so in a crossplay group a console player can be a patch behind PC for days.
- 07Unconfirmed
Report it as a bug in the official Discord
Report it as a bug in the game's official Discord. The game's own wiki moderators direct this exact error there rather than to a documented fix, which is the clearest sign this hasn't been resolved publicly yet.
Did this fix it for you?
Your answer helps the next player know whether these steps are worth trying first.
Hit this error? Leave a comment
Say where you are, what you see on screen, and whether any fix worked for you.
No links. Anonymous, no account. Keep it about the game.
What people are saying(3)
Notes from players who've hit this one — no time limit, an answer from months ago is still an answer.
Same problem. Happening on 1.000.007 for PlayStation
35d agoSame problem. seems the Epic games version has been given a different version of patch 1.0.0.5 than other platforms.
41d agoMismatched error not solved when both pc and xbox updated and restarted
42d ago
From isthisgamedownMatched on ""
From isthisgamedownMatched on ""
From isthisgamedownMatched on ""
Other RuneScape: Dragonwilds error codes
Recently added
- AION 2 "insufficient gameplay record" market listing block
- ARC Raiders error ARMR0014 on Storms and Night Raids
- Enshrouded server exits 0xC0000135 on Windows Server Core (fix)
- Gears of War: E-Day stuck on "Fetching Data" (fix)
- Gears of War: E-Day lucas-gnasher: reward expired
- Gears of War: E-Day reaver-tyrus: can't queue ranked
- Valheim server "App 896660 state is 0x6" after update (fix)
- Valheim Unity crash error (0xc0000005): what to try