The short answer
| Resource | Minimum | Recommended (6 players) |
|---|---|---|
| CPU | 4 cores | 4+ modern cores |
| RAM | 4 GB | 8 GB |
| Storage | 10 GB | 20 GB+ SSD/NVMe |
| Ports | 1 UDP port | 1 UDP port |
| OS | Linux or Windows | Linux (native server build) |
RAM: 2 GB, plus 1 GB per player
This is the rule the server's own documentation gives, and every plan sold here is built from it. It is worth stating as a formula rather than a table, because it explains the tiers instead of just listing them: the baseline covers the world simulation, and each connected player adds about a gigabyte on top.
| Players | RAM by the rule | Plan |
|---|---|---|
| 2 | 4 GB | Dragonwilds 4GB — $4.19/mo |
| 4 | 6 GB | Dragonwilds 6GB — $5.93/mo |
| 6 (full world) | 8 GB | Dragonwilds 8GB — $7.13/mo |
CPU
Four cores is the documented minimum and also the practical one. Dragonwilds is an Unreal Engine title and its dedicated server is single-threaded in the places that matter, so clock speed does more for you than core count past four. The plans here allocate 2, 3 and 4 dedicated vCores respectively, matched to the same player tiers as the memory.
Storage
The Steam install is the bulk of it; saves are small by comparison and grow slowly. Ten gigabytes is enough to hold the game, and twenty or more leaves room for the install to grow with updates plus a few world backups alongside it. Every plan here provisions 40 GB of SSD/NVMe, which is deliberate headroom rather than a figure to plan against.
One thing worth budgeting for on your own hardware: the server revalidates its files against Steam on start if you have set it up to, so a machine with a slow disk or a slow line spends that time on every boot.
Network and ports
A Dragonwilds server needs exactly one port, UDP, reachable from the internet. The default is 7777; servers deployed here use 27777. There is no separate query port, and nothing listens on TCP.
| Port | Protocol | Purpose |
|---|---|---|
| 7777 (default) | UDP | All game traffic |
| 27777 | UDP | The same, on servers deployed on Flux |
What you do not need
- A game licence on the server machine — the dedicated server downloads from Steam anonymously.
- Proton or Wine. There is a native Linux server build.
- A query port, a TCP port, or a server-browser registration.
- An RCON port. Dragonwilds has no remote console; administration is in-game.
On Flux, none of this is yours to size
Each plan is already matched to a player count using the rule above, the UDP port is opened and routed for you, and DDoS protection is included. Pick the tier that fits your group and deploy.
Frequently asked questions
How much RAM does a Dragonwilds server need?
About 2 GB plus 1 GB per player. That is 4 GB for two players, 6 GB for four, and 8 GB for a full six-player world — which is as large as Dragonwilds worlds get.
How many CPU cores does a Dragonwilds server need?
Four is the documented minimum and enough for a full world. Beyond four cores, clock speed matters more than adding more of them.
How much disk space does a Dragonwilds server use?
Around 10 GB for the Steam install, with 20 GB or more recommended so updates and backups have room. Plans on Flux provision 40 GB.
Which ports does a Dragonwilds server need open?
One UDP port — 7777 by default, 27777 on Flux. No query port and no TCP port. The internal and external numbers must match.
Can more than 6 players join a Dragonwilds server?
No. Six is the ceiling Jagex sets for a Dragonwilds world, it is enforced by the server, and 1.0 does not lift it. No plan or setting raises it.