Dragonwilds Dedicated Server Troubleshooting

Start with the server log at RSDragonwilds/Saved/Logs/RSDragonwilds.log. Preserve the log and a copy of the save folder before reinstalling, changing ports, or replacing configuration files.

Server does not appear

1. Compare the version at the top of the server log with the version shown by the game client.
2. Search the exact, case-sensitive world name, not only the server name.
3. Confirm Owner ID, Server Name, Default World Name, and Admin Password are configured.
4. Restart managed hosting after a patch so it can update.
5. Read RSDragonwilds/Saved/Logs/RSDragonwilds.log.

The version check matters after every game update or hotfix. A server can start normally but disappear from compatible search results when its build no longer matches the client.

Server appears but cannot be joined

Forward the selected port as UDP to the server's reserved local address and allow it through the host firewall. The default first port is 7777. Carrier-grade NAT, double NAT, or an ISP that blocks inbound connections can prevent home hosting even when the local configuration is correct.

Test in this order:

1. join from another device on the same local network;
2. confirm the server process is listening on the selected UDP port;
3. confirm the host firewall allows the executable and port;
4. confirm the router forwards that UDP port to the server's current local address;
5. check whether a second router, mesh gateway, or ISP modem creates double NAT;
6. ask the ISP whether the connection uses carrier-grade NAT or blocks inbound UDP.

If local joining works but internet joining does not, the world and server configuration are probably valid; concentrate on firewall, router, and ISP reachability.

Crossplay or console joining fails

Keep all clients and the dedicated server on compatible versions, confirm crossplay is enabled through the provider's supported configuration, and restart after changing it. Do not assume that a PC-only local test proves console crossplay is working.

Jagex's announced 1.0.0.5 patch targets several relevant problems: connections failing when more than two players are already present, console save corruption after joining a modded dedicated server, and console owners being unable to edit dedicated worlds. Until the update is confirmed live, avoid joining a modded server from console and read the 1.0 known-issues tracker.

Settings revert

Stop the server before editing DedicatedServer.ini. Jagex lists changes made while the process is running as a known cause of settings being lost.

Edit the file for the operating system the server actually uses. Jagex documents Linux configuration under RSDragonwilds/Saved/Config/Linux/DedicatedServer.ini and Windows configuration under the corresponding WindowsServer directory.

Wrong or new world loads

Stop the server and back up RSDragonwilds/Saved/SaveGames. Confirm the intended .sav is in that directory. If no save exists, the server creates a new default world.

When several .sav files are present, do not identify the correct world by filename alone. Preserve all of them, compare timestamps carefully, and test with copies. Follow the backup and migration guide before emptying the live directory.

Server starts and then stops

Check the log for a missing Owner ID or another mandatory value. The Owner ID must be the Dragonwilds Player ID shown at the bottom of the in-game Settings menu. Also confirm the operating system is 64-bit and that the server has enough available memory beyond what the operating system and monitoring tools consume.

Managed server does not update

Stop and restart the service through its control panel after a game patch. If the displayed server build remains behind the client, use the provider's update or reinstall action only after downloading a current world backup. Contact provider support before deleting the instance.

Sources: official dedicated-server guide, official 1.0.0.5 patch announcement, and official 1.0 launch notes.