RuneScape: Dragonwilds 1.0 changes for dedicated server owners
News & Updates

RuneScape: Dragonwilds 1.0: What Changed for Dedicated Server Owners

1.0 on 15 September 2026: platforms, the crossplay option Jagex added to dedicated servers, invite codes, and what the 1.0.0.4 and 1.0.0.5 patch notes mean for anyone running a server.

September 28, 20267 min read
Share

On This Page

RuneScape: Dragonwilds left Early Access on Tuesday 15 September 2026 — Jagex's Steam post "Our 1.0 Release is live!" announced it that morning. For players, 1.0 is consoles, crossplay, the Scorned Wilderness and Kuldra. For dedicated server owners the list is shorter, and the two hotfixes that followed within eight days matter as much as the launch. Here is what changed, what Jagex has and has not said, and what to do about each patch. Everything quoted is from Jagex's Steam news posts, dated by the posts' own timestamps.

The launch: 15 September 2026

Jagex's post lists the platforms: "We're now live on PlayStation 5, Nintendo Switch 2, XBOX Series X | S and PC on Epic Games Store, Jagex Launcher and Steam." Xbox Game Pass holders could start the same day, per a Jagex news item from 19 August. Console and PC launched together.

The 1.0 notes credit Early Access with the server itself: "In March, we launched our next Major Update … We launched support for Dedicated Servers". So the server you run today is the 0.11-era tool on the 1.0 build, and Jagex's dedicated-server guide (30 March 2026), not rewritten for 1.0, is still its official documentation — which is why the crossplay lines below are the only official words on how 1.0 touches servers.

Skip the setup headache

Get a server running in under 60 seconds.

Configure Server

What 1.0 changed for dedicated servers

1. A crossplay option

Jagex's 1.0 notes, under "Added Crossplay!":

In the in-game menu, worlds can now be enabled as crossplay when you load them. Crossplay worlds will be shown in the world browser. Players now have the option to make their worlds crossplay or not each time they host a multiplayer world. Dedicated servers now also have crossplay option.

That last sentence is the whole of what Jagex has published about crossplay on dedicated servers: no default, no setting, no per-platform join flow. Jagex's server guide, written before 1.0, does not mention crossplay at all. We are documenting the option on our own servers and will publish the tested flow; until then we will not describe a procedure we have not run.

2. Invite codes

Also new in 1.0: invite codes — Jagex's notes say they can be entered on the world browser screen and are shown in the pause menu. Jagex frames this around worlds in general; the notes do not single out dedicated servers, and the documented way to reach a dedicated server remains searching the exact, case-sensitive world name in Worlds → Public. Jagex's server guide still lists Steam invites to a dedicated server as a known issue.

3. A new build, which means a restart

Every patch is a version bump, and Jagex's guide is explicit that a server on a different version from the client stops appearing in the browser. 1.0 was the biggest such bump the game has had. If a server was left on the Early Access build, its players lost it on 15 September and got it back only when the server was updated. That has been true of every patch since — see below.

What did not change

  • The player cap. Jagex's guide says up to six players as of 0.11. Nothing in the 1.0, 1.0.0.4 or 1.0.0.5 notes restates or changes it.
  • The RAM rule. 2 GB + 1 GB per player. Details in how much RAM a Dragonwilds server needs.
  • The INI. Five documented fields, with world rules living in the save rather than the file.
  • The port. UDP 7777 by default.
  • The price. Jagex said before launch that the game's price was not rising with 1.0.

Patches since 1.0, newest first

Kept current as Jagex ships; dates are the Steam posts' timestamps, UTC.

1.0.0.5 — 25 September 2026

The lines that touch servers and multiplayer:

  • A fix so players no longer fail to connect to multiplayer servers when more than two players are already present.
  • A fix so Sworn Servant can be cast on multiplayer and dedicated servers.
  • Several console-specific dedicated-server fixes — among them one for a save-corruption issue when joining a modded dedicated server from a console. We are testing the console route on our own servers and will document it here once we have run it ourselves.

The notes also say Jagex is still investigating save corruption; nothing in them says whether dedicated-server worlds are affected, so we do not claim either way. The next Jagex-dated update is 1.0.1, in October.

1.0.0.4 — 18 September 2026

A hotfix three days after launch. From the notes:

  • A fix for world saves becoming corrupted when exiting a game session, plus two crash fixes.
  • Jagex said it was still investigating reports of worlds going missing or turning invisible from players' world lists, in conversation with the console platform teams.

The line server owners with a mixed group needed to read: "The process for deploying this patch does, however, mean that Nintendo Switch 2 and Jagex Launcher systems will no longer be able to crossplay until the patch has been processed on their respective platforms." A patch can reach launchers at different times, and until it has, players on different launchers may not be able to play together. Whether that had cleared before 1.0.0.5 is not something Jagex's posts state, so we do not.

What to do on each patch

  1. Update the server. Self-hosted: stop, back up DedicatedServer.ini and Savegames, re-run +app_update 4019830, confirm the INI is intact, start. On Connect: restart — the server checks Steam for the current build on every start, and the INI is kept across the update.
  2. Compare versions. Top of RSDragonwilds.log against the game's top-left corner.
  3. Expect a lag. Host guides report the server depot can trail the client build briefly after a patch; if versions still differ, wait and update again.
  4. Tell the group. A patch can reach one launcher before another and split the group for a while, as 1.0.0.4 did. That is on Jagex's side, not the server's.

The full symptom list is in server not showing in the world browser, and the from-scratch install is in the dedicated server setup guide. RuneScape: Dragonwilds server hosting at Connect turns the update routine into a restart.

Frequently Asked Questions

When did RuneScape: Dragonwilds 1.0 release?

15 September 2026, on PlayStation 5, Nintendo Switch 2, Xbox Series X|S, and PC via Steam, Epic Games Store and the Jagex Launcher, per Jagex's Steam post of that date.

Did 1.0 change the dedicated server player cap?

No. Jagex's guide says up to six as of 0.11, and the 1.0 and hotfix notes do not change it.

Does the dedicated server support crossplay after 1.0?

Jagex's 1.0 notes say "Dedicated servers now also have crossplay option." Jagex has not documented the default, the setting, or the join flow per platform, and we will publish ours once tested.

Do I need to update my server for 1.0.0.4 and 1.0.0.5?

Yes. Any version difference between server and client removes the server from the world browser, per Jagex's guide. Update (or restart, on Connect) after each patch.

What is next after 1.0.0.5?

Jagex's launch post names the 1.0.1 update for October and Luminance, the next content update, for "this winter". No day is given for either.

Skip the setup headache

Get a server running in under 60 seconds.

Configure Server

Or see plans, specs and regions on RuneScape: Dragonwilds server hosting.

Related Help Articles

Need step-by-step instructions? Check out these guides in our Help Center.