RuneScape: Dragonwilds 1.0: What Changes for Server Owners

RuneScape: Dragonwilds leaves Early Access on 15 September 2026. For a server owner that date is not just a content drop — it is a large game update, a simultaneous console launch, and the end of the Kuldra's Saga storyline, all landing at once.

This page collects what Jagex has actually announced about that transition and translates it into things a server owner has to do. It deliberately does not speculate.

Everything here is announced, not observed

This page was written before 15 September 2026. Every statement about post-launch behaviour is sourced to a public Jagex announcement made before the fact, and is flagged as such. Jagex has changed plans before — dedicated servers were originally earmarked for the 1.0 window and then pulled forward to March. Treat this as a plan of record, not a description of a shipped release.

The confirmed facts

On the last point, Jagex's Executive Producer was direct on 31 July 2026: "Our 1.0 release on September 15th is not the end of Dragonwilds. Far from it." — describing development as "a long voyage with many epic stages" with more detail promised at an October event. So 1.0 is a milestone in an ongoing update cadence, not a freeze. Plan for patches to keep coming.

What actually changes for a server owner

Here is the honest summary: Jagex has announced nothing that changes how a Dragonwilds dedicated server is configured or operated. No new startup values, no new config file, no change to the six-player cap, no migration step.

What changes is the scale of the update and the arrival of two new client platforms. Both of those affect you through mechanisms that already exist.

1. The update itself is the main event

Every Dragonwilds patch requires the dedicated server to be restarted before players can connect, and Jagex repeats it in nearly every patch note. The three hotfixes on 30 and 31 July 2026 each opened with the same line:

"Dedicated Servers will need to be restarted to sync updates."

A version mismatch between server and client does not produce a helpful error. Jagex describes the symptom in its dedicated-server guide: "If you cannot see your Dedicated Server any more, use the logs to ensure that the version it runs matches the one your game does. This is likely to happen any time an update or hotfix is released." The server simply stops appearing in the list.

1.0 is the largest update the game has had. Expect the server to need a restart on the day, and expect a wave of "the server is gone" messages from anyone who updated their client before you restarted.

The single most useful thing you can do on 15 September

Restart the server after the update lands, before your players try to join. On our platform the version check runs at boot, so the restart is the update. See How to update your server, and consider putting it on a schedule — How to setup Schedules.

2. Expect hotfixes, and expect them fast

This is worth planning for because Jagex's own history says so. Look at the pattern around previous major updates:

• 0.11 shipped 31 March 2026. Hotfixes 0.11.0.2 through 0.11.0.10 followed within thirteen days, several of them explicitly flagged as requiring a dedicated-server restart.
• 0.12 shipped 22 June 2026, with six announced hotfixes between 0.12.0.1 and 0.12.0.8 landing over the following nine days.
• 0.12.1 shipped 29 July 2026 and had three hotfixes within 48 hours.

A 1.0 release is not going to be quieter than that. The week of 15 September will very likely involve several restarts, not one.

3. Jagex asks you to prepare the world before a forced restart

This is a genuinely important operational detail and it is easy to miss, because it appeared inside routine hotfix notes rather than in the documentation. Jagex wrote it twice, on 9 April and 13 April 2026:

"To protect save file integrity, users on Dedicated Servers are encouraged to collect any belongings from gravestones and rest at beds before forcing restarts of servers to apply this fix."

In other words: before you force a restart, get players to retrieve their gravestone loot and rest at a bed. Jagex framed this around specific fixes rather than as a permanent rule, but it costs nothing and it is the developer's own guidance for protecting a save across a restart. Apply it on launch day.

Do not force-kill a server that has players mid-session

A graceful stop lets the game write its save out properly. An abrupt one risks losing whatever has happened since the last write. Stop the server cleanly from your panel and give it a moment.

4. Back up before the update, not after

Jagex has said it is "endeavoring to avoid wipes whenever possible; this includes updates and our eventual full release" — an intention, not a guarantee, and one written in a FAQ that predates the launch announcement.

A Dragonwilds world is a save file on disk. Copy it somewhere else before a version transition of this size. Worlds, saves and backups covers what to copy and the order to do it in; How to create a backup covers the panel mechanics.

5. Consoles arrive, with unanswered questions

PS5, Xbox Series X|S and Nintendo Switch 2 launch on the same day, and Jagex confirmed crossplay in one sentence and has published nothing further. Critically, Jagex has not stated whether console players can join a dedicated server, and the dedicated-server documentation has not been touched since 2 April 2026.

That is the single largest open question for anyone running a server for a mixed group. It is covered honestly, with a clear line between confirmed and unknown, in Is RuneScape: Dragonwilds crossplay?.

What is not changing, as far as anyone knows

It is worth stating the negatives explicitly, because absence of an announcement is itself information.

• The six-player dedicated-server cap. Raised from four to six in March 2026. Nothing since mentions 1.0 changing it.
• The configuration surface. Server name, world name, admin password, owner ID, optional world password. No new values announced.
• How players find your server. Search the exact, case-sensitive world name on the Public tab.
• How admin works. Password entered in the in-game Server Management screen.
• Modding. Jagex has never shipped official mod support. Its position, still live in the FAQ today, is that "We're open to the idea of modding, within reason" and that it is "working with our team to develop and publish a full guideline on our modding policy in line with the EULA". That guideline now exists as the Community Modding Guidelines on Jagex's legal portal — a DOs-and-DON'Ts framework, not a mod API. No in-game mod support has been announced for 1.0.

Two Jagex plans that were announced and have not visibly shipped

In December 2025 Jagex described a plan for two server types — "moddable, customizable servers" alongside "'Vanilla' Dedicated Severs [sic] which cannot be modified", to be "flagged differently in the server list". In April 2026 it announced "direct IP connections", "auto-discovery" and making the Owner ID optional. Some of these may have shipped quietly; Jagex's written documentation reflects none of them. Do not plan around any of them until you can see them.

A launch-week runbook

Concrete, in order:

1. Before the 15th — take a full backup of the world and store it off the server. Confirm you know your exact world name, capitalisation included, and that it is distinctive.
2. Before the 15th — check that automatic updating is enabled on the server, so a restart pulls the new build rather than pinning the old one. See Server settings and startup variables.
3. On the day, before restarting — ask players to clear their gravestones and rest at a bed, per Jagex's guidance.
4. On the day — stop the server cleanly, then start it. Watch for START SESSION - Success in the console.
5. On the day — join it yourself before telling anyone else it is up. If it does not appear, work Server not showing up rather than changing settings at random.
6. Through launch week — expect further hotfixes. Restart again each time Jagex ships one.
7. After the dust settles — re-check the crossplay position against what Jagex has published by then, because the useful detail did not exist when this page was written.

Summary

---

Made with 💜 by GameServerKings