The server is running. The log looks healthy. You open Worlds → Public, type the name, and there is nothing there. No error, no "server offline", just an empty result. A running world that nobody can find has a short list of causes. Work down it in order — the build mismatch and the exact-name search come first, and neither one is a bug.
1. The server is on a different build from your game
This is the one to check first, every time, and especially in the days after a patch. Jagex's dedicated-server guide says it plainly: "If you cannot see your Dedicated Server any more, use the logs to ensure that the version it runs matches the one your game does. This is likely to happen any time an update or hotfix is released."
Your game updates itself through Steam, Epic or the Jagex Launcher. The server does not update itself. The moment your client is one build ahead, the server vanishes from your world browser — and it vanishes silently. Steam Community replies describe the mechanism as the server no longer being announced once it stops matching the client version; Jagex does not describe the mechanism, only the effect.
How to check. Open RSDragonwilds/Saved/Logs/RSDragonwilds.log on the server. The version is printed at the top. In the game, the client version is in the top-left corner of the screen. They must be identical.
How to fix. Stop the server, re-run the SteamCMD update (+login anonymous +app_update 4019830), start it, and compare the two numbers again. Host guides report that immediately after a client patch the server build can arrive a little later than the client build — if the numbers still differ after an update, wait a while and update again.
On a Connect server this step is the whole fix: restart. The server checks Steam for the current build on every start, so a restart after a patch puts it back on the players' version. The restart is also why our players can't join guide begins with the version check.
Since 1.0 shipped on 15 September 2026, Jagex has already patched more than once — 1.0.0.4 on 18 September, then 1.0.0.5. Every one of those is a moment when a server that is not restarted drops out of the browser. Earlier patch notes, from 0.12.0.5 through the 0.12.1.x hotfixes, carried the line "Dedicated Servers will need to be restarted to sync updates" for the same reason.
2. You are searching for the wrong name, or the wrong case
There is no browse list. Jagex's guide says to open Worlds → Public and enter "your exact World name, case sensitive". Three ways that goes wrong:
- Searching the Server Name. The Server Name and the Default World Name are two different fields in
DedicatedServer.ini. The search matches the world, not the server.
- Case.
Ashenfall and ashenfall are different searches. Jagex's guide is explicit that the search is case sensitive, and there is no error to tell you which letter is wrong.
- An uploaded world. Host guides report that for a world you copied in, the name to search is the original
.sav file's name, not the Default World Name in the INI. If you uploaded a world and the Default World Name search finds nothing, try the save file's name.
Copy the world name out of the INI (or the save file name) and paste it into the search rather than typing it.
3. The server has not finished starting
The first start creates the default world, and any start that follows a Steam update has to finish the update first. Until the log shows the server is up, the browser will not find it. Read the log tail before you search; on a hosted server, watch the console.
4. You edited the INI while the server was running
Jagex lists this as a known issue: changes made to dedicatedserver.ini while the server is running are lost. If you changed the world name on a live server, the server is still announcing the old one. Stop, edit, start.
And a related trap reported in Steam Community threads from April 2026: a SteamCMD update can replace the INI with a default template, which means your world name reverts to the default and the world you are searching for no longer matches. After any update, open the file and confirm your five lines are still there. Connect servers keep a copy of the INI across updates and restore it if Steam overwrote it, so this one does not apply to a hosted server.
5. You were invited through Steam
Jagex's guide lists a known issue that inviting a player to a dedicated server through Steam invites "doesn't currently connect as intended". If a friend clicked a Steam invite and landed nowhere, that is expected. Have them search the world name in Worlds → Public instead.
6. The world password is wrong
Not a browser problem, but it looks like one from the other side: the search finds the world, the join fails. The World Password in the INI supersedes any password saved in the world itself. Send players the INI value, not the one you set when you created the world locally.
The one-minute checklist
- Version at the top of
RSDragonwilds.log equals the version in the game's top-left corner. If not: update the server (restart, on Connect).
- You are searching the world name, pasted, exact case.
- The server has finished starting.
- The INI still holds your world name after the last update.
- Nobody is using a Steam invite.
Still nothing?
Two further points from Jagex's 1.0 notes are worth knowing while you troubleshoot. The 1.0.0.4 notes say Jagex is investigating reports of worlds going missing from players' world lists — that is about a player's own local list, and Jagex has not said it involves dedicated servers, so do not assume your server is affected. And the 1.0.0.4 notes said Nintendo Switch 2 and Jagex Launcher systems would be unable to crossplay until the patch had been processed on those platforms — Jagex has not posted an all-clear, so if your group spans launchers, a patch can split them for a while through no fault of the server.
If you would rather not carry the update watch yourself, RuneScape: Dragonwilds server hosting at Connect checks Steam on every restart and keeps your INI intact through it, which removes causes 1 and 4 from the list. The setup detail is in the full dedicated server guide.
Frequently Asked Questions
Why did my Dragonwilds server disappear after an update?
Because your game updated and the server did not. Jagex's guide says a mismatch between the server version and the client version is "likely to happen any time an update or hotfix is released". Update the server (or restart it on a host that updates on boot) and compare the version in the log with the one in the game.
Is the world name search case sensitive?
Yes. Jagex's guide says "exact World name, case sensitive".
Do I search the server name or the world name?
The world name — the Default World Name from DedicatedServer.ini, or, host guides report, the original save file's name for a world you uploaded.
Why does a Steam invite to my server not work?
Jagex lists it as a known issue: Steam invites to a dedicated server do not connect as intended. Search the world name instead.
Do I need to restart the server after every game patch?
Yes. Jagex's patch notes have repeatedly said dedicated servers must be restarted to sync updates, and the update installs on the way up. On Connect the restart also pulls the current build.