RuneScape Dragonwilds Server Not Showing Up? How to Fix It

A RuneScape: Dragonwilds server not showing up in the world search is usually a naming problem: the Public tab searches the exact world name, not the server name, and it is case sensitive. The next most common causes are a server on an older build than the game, a server that has not finished starting, and crossplay settings. This guide goes through each one, fastest checks first.

Quick fix

1. Open the Worlds screen and go to the Public tab.
2. Search the world name exactly as it is set on the server, character for character. AshenfallCrew and ashenfallcrew are different searches.
3. If you are not sure of the name, check the server log for the world that actually loaded.
4. If someone is already in the world, ask them for the invite code from the pause menu and enter it in the world browser instead.

Cause 1: Searching the wrong name

Dragonwilds servers have two names: ServerName and DefaultWorldName in DedicatedServer.ini. The Public tab search matches the world name. Searching the server name finds nothing unless the two happen to be the same.

Keep world names short, around 16 characters, and avoid names that are easy to mistype. Write the exact spelling down and share it with your group.

Cause 2: The server loaded a different world

DefaultWorldName is used when the server creates a world. If there is already a save in the server's RSDragonwilds/Saved/SaveGames folder, the server loads that save under its own name, and changing DefaultWorldName later does not rename it. If you uploaded a world, players need to search for the uploaded world's name, which is its .sav file name without the extension.

Check the server log to see which world loaded and search for that.

Cause 3: Version mismatch after a patch

Players cannot see a server running an older build than their game. This is the most common reason a server that worked yesterday vanishes today, since Jagex often ships hotfixes, especially in the weeks after the 1.0 release.

• Self hosted: stop the server and run the SteamCMD update for app 4019830 again, then start it.
• Hosted: restart the server from the panel to update it.

Compare the version at the top of the server log with the version shown in your game.

steamcmd +force_install_dir /home/dragonwilds/server +login anonymous +app_update 4019830 validate +quit

Cause 4: The server never finished starting

The server needs four values in DedicatedServer.ini to start properly: OwnerId (your Player ID from the bottom of the in game Settings menu), ServerName, DefaultWorldName and AdminPassword. If any is missing, the server may stop or sit there without ever listing the world.

Read the console from the top. A healthy start ends with the session being created and advertised. After an update, give it a few minutes before searching.

Also remember Jagex's known issue: changes to DedicatedServer.ini made while the server runs are lost. Stop, edit, start.

Cause 5: Crossplay and console settings

Since 1.0, PlatformPolicy in DedicatedServer.ini decides which platforms can join. With PlatformPolicy=Crossplay, players on every platform can see the world. If it is set to a single platform such as PC, console players will never find it.

Console players may also need to allow crossplay and online play with other platforms in their console's privacy or parental settings. Some players have reported a "crossplay disabled" banner that was fixed by correcting the clock on their device. More in Dragonwilds dedicated server crossplay.

Cause 6: Port 7777 is blocked (self hosted)

The server uses UDP 7777 by default. If you host at home and friends outside your network cannot see or join the world:

1. Allow UDP 7777 through the firewall on the server machine. On Ubuntu: sudo ufw allow 7777/udp.
2. Forward UDP 7777 on your router to the server's local IP.
3. If you changed the port with -Port=, forward that port instead.

Our port forwarding guide covers routers step by step, and what to do when your provider uses CGNAT. A hosted server has no ports to forward.

The world shows up but friends cannot join

• World password: players need the world password, not the admin password.
• Server full: dedicated worlds hold 6 players.
• Banned: an admin or the owner may have banned them. Only the owner can unban.
• Steam invite: Steam invites to dedicated servers have not connected reliably. Use the name search or invite code.
• Network: restart the router, turn off VPNs and allow the game through the firewall.

Dragonwilds server not showing up on a hosted server

On GamezServers the port is already open, so cause 6 does not apply. Check these:

1. The server is Online on your dashboard. With Sleep when empty on, it stops after 90 minutes with nobody playing, and anyone with access can start it again in one click.
2. Search the exact world name. If you uploaded a world, search that world's name.
3. After a game patch, restart the server so it updates.
4. Check PlatformPolicy in RSDragonwilds/Saved/Config/LinuxServer/DedicatedServer.ini in the Files tab if console friends cannot see it.

FAQ

Why can I not find my Dragonwilds dedicated server?

You are most likely searching the server name or the wrong capitals. The Public tab matches the exact world name.

How long does a Dragonwilds server take to appear?

Usually a short while after it finishes starting. After an update, allow a few minutes.

Can I join a Dragonwilds server by IP?

No. Players join by world name search or invite code.

Why did my server disappear after an update?

It is on an older build than the game. Update it and restart.

Skip the setup

Most of these problems come from running and updating the server yourself. A hosted Dragonwilds server is online in about a minute with no ports to open, crossplay for console friends and one click backups. See RuneScape: Dragonwilds server hosting, or how to host a Dragonwilds server.