RuneScape: Dragonwilds Dedicated Server Hosting Guide

RuneScape: Dragonwilds is Jagex's attempt to take one of the most recognizable names in MMO history and repurpose it into a co-op survival-crafting game \x2014 you gather resources, build a base, fight familiar RuneScape monsters, and progress through skills that longtime RuneScape players will recognize, but the moment-to-moment gameplay loop is closer to Valheim or Enshrouded than to the tick-based MMO combat the RuneScape name is known for. For groups who want a persistent Gielinor homestead that survives between play sessions, a RuneScape: Dragonwilds dedicated server is the difference between a game that only exists when one specific friend is online and a genuine shared world you can drop into whenever you like. This guide covers what is publicly known about Dragonwilds' server architecture, realistic hardware planning based on comparable Unreal Engine survival-crafting titles, a full setup walkthrough, and the operational issues that catch new hosts off guard.

What Is Known About Dragonwilds Dedicated Servers

Dragonwilds launched into early access built on Unreal Engine, following the now-familiar pattern for co-op survival-crafting titles: a client build most players buy and run locally, plus either peer-hosted multiplayer, a standalone dedicated server tool, or both. Jagex has a long institutional history running persistent MMO worlds for the original RuneScape and Old School RuneScape, which is a meaningfully different discipline from shipping a self-hostable dedicated server binary for a survival-crafting spin-off, so treat the two as separate engineering efforts rather than assuming Dragonwilds inherits RuneScape's server infrastructure directly. What is reasonable to expect based on the genre and the game's early access status:

• A SteamCMD-distributed dedicated server download, consistent with how the overwhelming majority of modern Unreal Engine survival-crafting titles ship self-hosted server support \x2014 confirm the exact App ID from the game's Steam page or Jagex's official channels before scripting automation, since early access titles occasionally split the dedicated server tool out under its own App ID sometime after the client's initial launch.
• World/save data tied to a persistent save file that grows as your base, farms, and explored map expand, the same pattern seen in Valheim, Enshrouded, and Sons of the Forest.
• Skill progression and inventory data likely stored per-character within the world save, meaning a corrupted or rolled-back world save can cost players real progression time, not just base structures \x2014 this raises the stakes on backup discipline compared to a pure base-building game with no character progression system.
• Frequent early access patches that may adjust balance, add skills or biomes, and occasionally require a save-compatibility break, which is standard for the genre at this stage of development.

If you already ran a Valheim or Enshrouded dedicated server for your group, most of that operational knowledge \x2014 backup cadence, port forwarding, process supervision \x2014 transfers directly to Dragonwilds even though the exact binary and config file names differ.

How Dragonwilds Differs From a Pure Base-Building Survival Game

Because Dragonwilds layers RuneScape-style skilling progression on top of the usual survival-crafting loop, server-side load is driven by three factors instead of the usual two: player count, world/base complexity, and the number of tracked skill and inventory systems per character. A four-player group that has fully explored the map and leveled multiple skills to their cap can realistically load the server more heavily than an eight-player group still in the early game, which is worth keeping in mind when you compare your own server's performance against a friend's group of a different size.

Combat and Monster AI Load

Dragonwilds retains recognizable RuneScape monsters and combat encounters, translated into real-time action combat rather than the original's tick-based system. Real-time monster AI and hit detection are more CPU-intensive per-encounter than tick-based combat, so expect server CPU load to spike during active combat encounters and boss fights more than during quiet building/gathering time, similar to what Sons of the Forest and Enshrouded hosts observe during their own combat-heavy moments.

Expected Dragonwilds Server Requirements & Pricing

Because Jagex had not published a finalized, exhaustive dedicated server specification sheet at the time of writing, the table below is modeled on comparable Unreal Engine survival-crafting titles with skill/inventory progression layered in, framed as a planning baseline to validate against your own testing:

The jump to the "large / long-running world" tier reflects the same pattern seen across the genre: a world that has been alive for months, with multiple maxed-out skills and a sprawling base, needs meaningfully more RAM and storage than the same player count on a fresh world. If your group plays for more than a few weeks, plan to re-evaluate your tier rather than assuming your launch-week benchmark holds indefinitely.

Step-by-Step Dragonwilds Dedicated Server Setup

1. Provision flexible Linux infrastructure

Start with a Linux dedicated server or VPS running Ubuntu 22.04 or 24.04. Because this is an early access title, favor infrastructure with full root/SSH access over a rigid pre-built game panel slot so you can adapt as Jagex updates the dedicated server tooling.

2. Install SteamCMD

sudo useradd -m dragonwilds
sudo su - dragonwilds
mkdir ~/steamcmd && cd ~/steamcmd
wget -q https://steamcdn-a.akamaihd.net/client/installer/steamcmd_linux.tar.gz
tar -xvzf steamcmd_linux.tar.gz

3. Download the dedicated server files

./steamcmd.sh +force_install_dir ~/dragonwilds-server \
  +login anonymous \
  +app_update APPID validate \
  +quit

Replace APPID with the current confirmed Dragonwilds dedicated server App ID from the game's official Steam page \x2014 do not hardcode a guessed number into long-term automation, since early access dedicated server tools sometimes move to a new App ID as they mature out of a beta branch.

4. Configure the server settings file

On first run, the dedicated server generates a settings file (naming and format subject to change during early access). Review and set at minimum:

• Server name and max players \x2014 match max players to the hardware tier you selected.
• Password \x2014 set one for any server with a public IP, since publicly reachable early access servers can attract uninvited connection attempts.
• World name/seed \x2014 set once at world creation; changing it starts a new world and discards existing progression.
• PvP and difficulty toggles \x2014 decide with your group before the world is created, since some settings only apply cleanly to a fresh world.

5. Open the required ports

Until Jagex publishes a final confirmed port, reserve a working UDP range typical of Unreal Engine co-op titles and narrow it once the official default is confirmed:

sudo ufw allow 7770:7790/udp
sudo ufw enable

6. Launch and verify

cd ~/dragonwilds-server
./DragonwildsServer.sh -log

Watch console output for a successful listen confirmation, then have one player connect via the in-game "Join by IP" or server browser option before inviting the rest of your group.

7. Automate uptime and backups

Wrap the server in a systemd unit so it restarts automatically after a crash or host reboot, and schedule automated, versioned backups of the world save directory. Because Dragonwilds ties skill progression to the world/character save, losing a save is a bigger loss for players here than in a pure base-building game with no leveling system \x2014 treat backup cadence accordingly, at least daily and ideally before and after any server update.

Common Dragonwilds Server Issues & Troubleshooting

Players cannot connect after a game update

Confirm the dedicated server binary version matches the client version exactly \x2014 mismatched client/server versions are the most common cause of silent connection failures in actively patched early access titles. Update the server via SteamCMD immediately after any client patch is announced.

Combat feels laggy with a full group

Because combat encounters are more CPU-intensive than quiet gathering time, sustained combat lag with a full player count is usually a CPU sizing issue rather than a network problem. Moving to a higher CPU tier resolves this faster than adding RAM.

World save grows large after weeks of play

This is expected as your base, explored map, and skill data expand. Budget storage headroom in advance rather than waiting for a "disk full" error, and consider archiving old backup generations to cheaper storage once you have several weeks of history.

Server crashes after a specific boss encounter

Early access boss fights are common sources of server-side crashes since they often introduce new AI and scripted behavior that has had less production testing than core survival mechanics. Report crash logs to Jagex's official channels and keep a recent backup before attempting the same encounter again.

Skill progression seems to reset or roll back

This points to a save-corruption or rollback event, not a bug in the skill system itself. Restore from your most recent clean backup and avoid killing the server process directly (always use a proper shutdown command) to reduce the odds of this happening again.

Buyer's Checklist Before Renting a Dragonwilds Server

• Confirm the provider supports custom SteamCMD installs rather than only a fixed pre-built game panel template, since early access tooling changes quickly.
• Check that automated, versioned backups are available and easy to configure, given that character/skill progression lives inside the world save.
• Verify NVMe storage with headroom for a save file that will keep growing as your group plays.
• Ask whether you can resize CPU/RAM without a full migration as Jagex publishes more concrete official requirements.
• Prefer monthly billing over long-term contracts while the game is still in early access.
• Confirm the host allows you to open custom UDP ports without a slow support-ticket process.

Frequently Asked Questions

Does RuneScape: Dragonwilds support dedicated servers?

Check the game's official Steam page and Jagex's community channels for the current status of dedicated server tooling, since early access titles frequently ship or refine this kind of support after initial release.

Is Dragonwilds connected to the main RuneScape or Old School RuneScape servers?

No \x2014 Dragonwilds is a separate co-op survival-crafting game that reuses RuneScape's IP, lore, and some monster designs, but it runs on its own distinct server infrastructure rather than sharing a world with the MMO.

How much RAM does a Dragonwilds dedicated server need?

Based on comparable Unreal Engine survival-crafting titles, 8-12 GB is a reasonable starting point for a small group, scaling to 16-20 GB for larger, long-running worlds with maxed-out skills and sprawling bases.

Can I run mods on a Dragonwilds server?

Modding support for early access titles typically develops over time; check the game's official channels for the current state of mod/plugin support before assuming feature parity with more mature survival titles.

Will my world save carry over through future updates?

Not guaranteed during early access \x2014 major content patches can require a save-format change. Always back up before applying an update, and check patch notes for save-compatibility warnings.

How many players can join one Dragonwilds server?

Exact player caps are set by the developer and may change during early access; size your hardware for your actual group size rather than assuming a specific cap without checking current official documentation.

Is combat harder on players when hosted on a dedicated server versus peer hosting?

No \x2014 combat difficulty is a game-side setting, not a hosting-side one; dedicated hosting affects uptime and consistency, not combat balance.

What happens if I lose connection to my own dedicated server?

Unlike peer hosting, a dedicated server keeps running and other players stay connected even if your own connection drops, since no single player's machine is acting as the host.

A properly sized, well-backed-up Dragonwilds dedicated server turns a short co-op session into a persistent Gielinor homestead your group can keep building on for months. WebsNP's Linux dedicated servers and VPS hosting both give you the root access and SteamCMD flexibility this kind of early access title needs \x2014 contact our team if you want help sizing a server for your group.