A RuneScape: Dragonwilds dedicated server is configured by a handful of values in one file, DedicatedServer.ini. On your Connect server they all live on the Server Settings tab, and every change takes effect on the next restart.
The settings
| Setting | What it does | Notes |
|---|---|---|
| Player ID (Owner ID) | Makes you the server owner | Copy it from the bottom of the game's Settings menu. See Owner ID |
| World Name | The world the server creates on first start, and the name players search for | Case sensitive. Keep it short and unambiguous |
| Server Name | The label shown against your server in the browser | Up to 16 characters. Players search the World Name, not this |
| Admin Password | Anyone who knows it can open the Server Management tab in the game | Admins can ban online players but cannot unban. Change it to remove every admin |
| World Password | Players must enter it to join | Optional. Overrides any password saved inside the world. Empty = open server |
| Max Players | How many can be in the world at once | 1 to 6. Six is the game's own cap on every plan |
| Update on restart | Check Steam for the current game build on every start | On by default. Turn it off only to hold a version deliberately |
Applying a change
- Edit the value on the Server Settings tab and save.
- Restart the server from the Overview tab.
- Watch the console settle before telling players to search.
The server reads its settings at start. Jagex's guide lists this as a known issue on any dedicated server: values changed while the server is running are lost. The dashboard handles it for you — save, then restart — but a change is not live until that restart.
Update on restart
This is the setting that keeps your server visible. Players update through Steam or their launcher automatically; a server whose build differs from the players' stops appearing in the world browser, with no error. With Update on restart on, every restart checks Steam for the current build first, so a restart after a patch is the whole fix.
Your settings survive the update. The server's INI is copied aside before each Steam update and restored if the update changed it, so a patch never resets your World Name or passwords.
Turn it off only if you want to hold the server on an older build on purpose — for instance, while part of your group waits for a patch to reach their launcher. Remember to turn it back on.
Where the settings are not
- Difficulty and world rules. Not here. Per Jagex's guide, they live in the world save. To run a custom-rules world, create it locally with the settings you want and upload the
.sav— see Upload a world. - Whitelist. There is none. Use the World Password to keep a server private, and bans for anyone who should not be there.
- Crossplay. Jagex's 1.0 release added a crossplay option to dedicated servers. We are verifying how it behaves on our servers and will add it to this table once documented.
Things you cannot change
- Player cap. Six is the game's limit. Max Players goes down from there, never up.
- Ports. Your server's port is assigned at checkout and shown on the Overview tab. It does not change.
- The file itself. The five INI values are managed from this tab. Editing
DedicatedServer.inion the Files tab directly is overwritten by the tab's values at the next start, so make changes here.
Restarts and saving
Restart and Stop from the dashboard are clean shutdowns. The Backups tab is separate from the game's own saving — see Backups & saves — and taking a manual backup before a settings experiment costs nothing.
Related
- Nobody can find the world after a change: Players can't join
- First-run walkthrough: Getting started