RuneScape: Dragonwilds 1.0: What Changes for Server Owners

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

This page sets out what Jagex announced about that transition, what the release and its first patches actually changed, and what a server owner has to do about it. It deliberately does not speculate.

Written before launch, updated after it

This page was first written from Jagex's pre-launch announcements. It has been updated with the 1.0 release notes (15 September) and patches 1.0.0.4 (18 September) and 1.0.0.5 (announced 23 September for release on the 25th). Jagex has changed plans before: dedicated servers were originally earmarked for the 1.0 window and then pulled forward to March. Anything still marked as announced has not been confirmed by a 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." He described development as "a long voyage with many epic stages", with more detail promised at RuneFest on 3 October. So 1.0 is a milestone in an ongoing update cadence, not a freeze. Plan for patches to keep coming.

What actually changed for a server owner

Here is the honest summary: 1.0 added one server setting, crossplay, and changed nothing else about how a Dragonwilds dedicated server is configured. There are no new startup values, no change to the six-player cap and no migration step.

What changed is the scale of the update, the arrival of new client platforms, and the fact that patches now reach those platforms on different days. All of this affects you through mechanisms that already exist.

1. The update itself was 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.

If your server has not been restarted since before 15 September, it is still on an Early Access build and nobody can see it.

The single most useful thing you can do

Restart the server after each 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 with How to setup Schedules.

2. Hotfixes came fast, as expected

Jagex's history said a big update would be followed by a cluster of hotfixes:

• 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.

1.0 followed the pattern. 1.0.0.4 arrived on 18 September, three days after launch, and 1.0.0.5 was announced on 23 September for Friday the 25th. Each one means another restart.

3. Patches now reach platforms on different days

This is new with 1.0, and it matters if your group mixes platforms. Console patches have to pass each platform's certification, so they do not land everywhere at once. Jagex's 1.0.0.4 notes said so directly:

"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."

In practice, when you restart your server onto a new build, players on a platform that has not received that build yet cannot join until it does. After player feedback, Jagex said with 1.0.0.5 that it would submit patches to the consoles ahead of release, "with the expectation that this verification will take several days", to avoid knocking crossplay offline. If a Switch 2 player cannot get in the day after a patch, check their game version before you change anything on the server.

4. 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 before every patch restart.

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.

5. Back up before every update

Before launch, Jagex said it was "endeavoring to avoid wipes whenever possible; this includes updates and our eventual full release". That was an intention, not a guarantee, and the line was removed when Jagex rewrote its FAQ on 10 September. In the event there was no wipe: the 1.0.0.5 notes fix a recipe unlock "for users with existing character saves", so Early Access progress carried into 1.0.

The launch did bring save problems. 1.0.0.4 fixed "World Saves becoming corrupted when exiting a game session", and Jagex was still investigating world and character corruption on 23 September. It removed the Edit Appearance button as "the most common cause" until a fix lands. Jagex also warned that restoring some saves had "reset to default settings", turning Custom or Creative worlds into Normal ones. 1.0 also replaced the building system ("It's a new system"), which is the part of a world where a loss would hurt most.

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

6. Console players can join your server

PS5, Xbox Series X|S and Nintendo Switch 2 launched on the same day. The 1.0 notes say "Dedicated servers now also have crossplay option", and 1.0.0.5 fixes bugs that console players hit on dedicated servers: a save-corruption bug when "joining a modded Dedicated Server from consoles", and owners being unable to edit "their dedicated server worlds on consoles".

The setting is PlatformPolicy=Crossplay in the server's DedicatedServer.ini. The game writes it itself, and it was set on every server we host when we checked on 28 September. Jagex's dedicated-server guide still does not mention consoles or this key. The details are in Is RuneScape: Dragonwilds crossplay?.

What did not change

It is worth stating the negatives explicitly, because the absence of a change is itself information.

• The six-player dedicated-server cap. Raised from four to six in March 2026. Jagex's guide still says six after 1.0.
• The rest of the configuration surface. Server name, world name, admin password, owner ID and optional world password work as before. PlatformPolicy is the only new value.
• How players find your server. Search the exact, case-sensitive world name on the Public tab. 1.0 also added invite codes for worlds, but Jagex's notes don't say whether they work for a dedicated server.
• How admin works. Password entered in the in-game Server Management screen.
• Modding. Jagex has never shipped official mod support. Its FAQ now says "Many RuneScape: Dragonwilds players have already created some amazing mods" and points to its Community Modding Guidelines on Jagex's legal portal, a DOs-and-DON'Ts framework rather than a mod API. Note the 1.0.0.5 fix above. Until that patch, a console player joining a modded dedicated server could corrupt their save, so if your group mixes platforms, make sure the server is on 1.0.0.5 or later before running mods.

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. None of these is in the 1.0 release notes or in Jagex's dedicated-server guide, which still says "The server will not start without your owner ID." Do not plan around any of them until you can see them.

A post-launch runbook

If your server has not been touched since before 15 September, or for each patch from now on:

1. Take a full backup of the world and store it off the server.
2. Check that automatic updating is enabled, so a restart pulls the new build rather than pinning the old one. See Server settings and startup variables.
3. Before restarting, ask players to clear their gravestones and rest at a bed, per Jagex's guidance.
4. Stop the server cleanly, then start it. Watch for START SESSION - Success in the console.
5. Join it yourself before telling anyone else it is up. If it does not appear, work through Server not showing up rather than changing settings at random.
6. If console friends are joining, check that DedicatedServer.ini carries PlatformPolicy=Crossplay, and remember that their platform may get each patch a few days after Steam.
7. Keep restarting each time Jagex ships a hotfix. 1.0.1 is due in October.

Summary

---

Made with 💜 by GameServerKings