A dedicated server keeps a Dragonwilds world available without making one player keep the normal game client open. This checklist summarizes Jagex’s official how-to; use that document for the full, current configuration keys rather than copying a third-party template blindly.
Choose where it runs
The official guide supports a 64-bit Windows or Linux host. It lists a memory starting point of 2 GB plus 1 GB per player. That is a March 2026 guidance figure, not a benchmark for every mod, world size or future version. A managed host removes the need to configure your own router, while a home host gives you direct control and responsibility for network access.
Install the separate server tool
Jagex describes a free Steam product named RuneScape: Dragonwilds - Dedicated Servers, with tool App ID 4019830. It can be acquired through Steam or SteamCMD. Install the tool rather than assuming that launching a second copy of the game client creates a persistent dedicated server. The official article provides the current command and names the executable and log options.
Set the required configuration values while the server is stopped. The guide warns that changes made while it is running can be lost. On Linux and Windows, the configuration lives in platform-specific DedicatedServer.ini locations; follow the article for the exact path and keys for your version.
Open the network path
The default dedicated-server port starts at UDP 7777. Another server on the same host moves to 7778, and so on. A home host must allow and forward the applicable UDP port through the firewall, router and ISP path. Do not open unrelated ports simply because a forum post recommends it. If the server is visible but unjoinable, the official guide points to forwarding as a likely issue.
Match versions and crossplay settings
After a hotfix, compare the version at the top of the server logs with the client version shown in game. Update the dedicated-server tool if they differ. The 1.0 release notes add a crossplay option for dedicated servers; decide whether you need it before inviting friends on different platforms.
Finally, do not repeat the March guide’s “up to six players as of 0.11” as an unconditional current limit. It is explicitly version-qualified, and later builds need their own check.
Preflight before inviting players
| Check | Reason |
|---|---|
| Server tool rather than the normal game client | The dedicated tool is the product Jagex documents for a persistent world. |
| World name and settings saved while stopped | The official guide warns that editing configuration while running can lose changes. |
| Client and server versions match | A patch can make a previously visible server unavailable. |
| Correct UDP port allowed and forwarded | Jagex names 7777 as the default first server port; additional instances increment it. |
| Crossplay setting chosen intentionally | The option arrived in the 1.0 release and matters for friends on different platforms. |
For a home host, test from another network rather than assuming that the server appearing on the host machine proves outside access. Keep a copy of your world data before changing binaries or configuration. The exact backup path and commands depend on operating system and version; consult the official how-to instead of copying a path from an unverified forum reply.
If a friend cannot connect, start with the observable symptom. A missing listing after an update suggests a version check; a visible but unjoinable home server warrants checking the configured port and forwarding. Neither symptom proves a single cause. The join-server guide gives a shorter guest-facing triage.