How to Fix a RuneScape: Dragonwilds Server That Will Not Start

Dragonwilds servers fail for a small number of reasons, and one of them accounts for most of them.

1. The owner ID is missing

The server will not start without a valid OwnerId. It is your RuneScape: Dragonwilds player ID, shown at the bottom of the in-game Settings menu.

1. Stop the server.
2. Open RSDragonwilds/Saved/Config/LinuxServer/DedicatedServer.ini in Files.
3. Set OwnerId to your player ID.
4. Start the server and watch the console.

2. You edited the config while the server was running

Dragonwilds discards changes made to the config while the server is up. The order is always stop, edit, start. If a setting keeps reverting, this is why.

3. The config has a broken line

Read the panel console from the top of the last start. A malformed line, or a missing [/Script/Dominion.DedicatedServerSettings] section header, means settings below it are ignored. Restore your downloaded copy of the file if you have one.

4. The world name changed

DefaultWorldName names the world created at first startup. If the server appears to have started a fresh world, check that this value and the save on disk still match. Browse the save folder in Files and compare modified dates to find the real one.

5. After a game update

Dragonwilds is a young title and its dedicated server changes between updates. Restart the server so it pulls the new build, then read the console from the top for settings it no longer recognises.

Players cannot join a running server

• Confirm the world password, which is case sensitive.
• Confirm the port matches the one on the server overview.
• Confirm the client and server are on the same game version.

Back up before you experiment

1. Stop the server so the world is fully written.
2. In Files, download DedicatedServer.ini and the save folder.

What to send support

Open a ticket with the first hundred lines of console output from a fresh start and your config pasted as text with the passwords removed.