The server is online, but the world is not in anyone's search results or the join fails. For RuneScape: Dragonwilds this is nearly always one of the causes below. Work down the list in order.
1. The server is on a different build from the game
Players update through Steam or their launcher automatically. The server updates when it restarts. In between, the two are on different versions, and Jagex's guide is explicit about the result: a server whose version does not match the client stops appearing in the world browser. There is no error message — the world is simply not found.
Fix: restart the server from the Overview tab. On every start it checks Steam for the current build, so the restart is the update. Then search again.
Check: the server's version is printed near the top of the console when it starts (and in RSDragonwilds/Saved/Logs/RSDragonwilds.log on the Files tab). The player's version is in the game's top-left corner. They must be identical.
Straight after a game patch, host guides report the server build on Steam can arrive a little after the client build. If a restart still shows the old version, wait and restart again.
2. The name is wrong, or the capitals are
Jagex's guide says players search Worlds → Public for the exact World name, case sensitive. So:
- Search the World Name from the Server Settings tab, not the Server Name.
- Match every capital letter.
- If you uploaded your own
.sav, the name to search may be the save file's name rather than the World Name field. Try both.
Fix: copy the World Name from the Server Settings tab and send it to players to paste.
3. The server has not finished starting
Between Start and the console settling, the server is updating from Steam and loading the world. Searches during that window find nothing.
Fix: watch the console; tell players to search once it has gone quiet.
4. A setting was changed without a restart
The server reads its settings once, at start. A new World Name saved on the Server Settings tab is not live until the next restart — the server is still announcing the old name.
Fix: restart, then search for the new name.
5. Wrong world password
If the search finds the world but the join is refused, the network side is fine and the password is wrong. The World Password on the Server Settings tab overrides any password saved inside the world, so a password set when the world was created locally no longer applies.
Fix: send the World Password from the Server Settings tab. If you just changed it, restart first.
6. They used a Steam invite
Jagex lists this as a known issue: inviting a player to a dedicated server through Steam invites does not connect as intended.
Fix: the invited player searches the World Name in Worlds → Public instead.
7. The server is full
Jagex's guide caps a dedicated server at six players, and Max Players on the Server Settings tab may be set lower. If a player is refused at what looks like a full table, the setting is the thing to check.
Fix: check Max Players and raise it if it is below six; nothing raises the limit above the game's six.
8. One player, everyone else fine
If exactly one person cannot join while the rest are in, it is their side: their game version (section 1 again — check their top-left corner), their connection, or a launcher-specific issue. Jagex's 1.0.0.4 notes, for example, said Nintendo Switch 2 and Jagex Launcher systems could not crossplay until that patch had been processed on those platforms — a patch can reach launchers at different times.
Jagex's 1.0 release added a crossplay option to dedicated servers. We are verifying how it behaves on our servers and will update this guide with the per-platform detail once we have it.
Still stuck?
Open a ticket from your dashboard with: the exact text the player searched, the player's game version from the top-left corner, the server version from the console, and whether anyone at all can join. Those four answers usually let us solve it in one reply.