Jagex spent the last big announcement before launch saying something studios usually avoid saying out loud. RuneScape: Dragonwilds is not raising its price when it leaves Early Access on September 15, 2026. It stays at £24.99 or $29.99, exactly what Early Access buyers paid on day one, and the 1.0 build carries the whole of Kuldra's Saga plus every free update that shipped around it.
If you have been keeping a Dragonwilds server warm through Early Access, the September 3 post is more useful than the usual pre-launch hype reel. It answers the two questions that actually affect a server community: what it costs the friends who still have not bought in, and whether there is any reason to keep the world alive after the credits roll.
The Price Holds at $29.99
The normal Early Access arrangement is a discount on an unfinished game. You buy in cheap, you tolerate the rough edges, and the price steps up when the finished version arrives. Jagex went the other way, and the wording left no room for interpretation: the game, "containing the entirety of Kuldra's Saga and the Free Updates around it, is staying the same price once 1.0 releases."
The reasoning they gave points at two groups. Early Access buyers funded and shaped 17 months of development. The second group is everyone who deliberately waited for the Saga to be finished before touching it, and Jagex thanked them by name for the patience.
For a server owner this is a recruitment detail, not just a nice gesture. The friend who has been saying "I'll get it when it's done" arrives on September 15 with no price wall in front of them. If your world has been running on three or four regulars, this is the week your roster grows, and it grows on the same day console players join through crossplay.
Luminance Lands This Winter, and It Is Free
The second half of the announcement is the part that decides whether a server is worth keeping past launch month. Jagex confirmed that Dragonwilds "is not stopping at our 1.0 release" and committed to monthly updates as the game grows. The next major one already has a name: Luminance, arriving this Winter, and free like the minor updates before it.
That matters more for hosted multiplayer than it does for solo players. A survival RPG that stops shipping content at 1.0 loses its server population inside two months, because there is nothing to log back in for once the group has cleared the story. A monthly cadence with a named Winter release gives a community a reason to keep the same world, the same base and the same progression instead of drifting off to whatever launches next.
It also means your server is going to be patched, repeatedly, indefinitely. More on what that costs you below.
RuneFest on October 3 Sets Up 2027
Jagex is holding a Summit at RuneFest on October 3 to talk through 2027 plans and the next Saga in Ashenfall's story. That is three weeks after launch, which reads as deliberate: they want 1.0 out and stable before they start selling anyone on what comes after it.
If you are weighing how much to invest in a long-lived server, that is the date to watch. A second Saga announced on October 3 means the world you build now has years of content ahead of it rather than a finished story and a slow fade. It is a good argument for not wiping in November just because the group has run out of things to do.
What This Means If You Run a Dedicated Server
Monthly updates are good news for a community and a standing chore for whoever administers the server. Dragonwilds has one operational quirk that Jagex states plainly in their own patch notes: "Dedicated Servers will need to be restarted to sync updates." A running server does not pick up a new build on its own, and clients on the new version will not connect cleanly to a server still sitting on the old one.
July shows what that cadence looks like in practice. 0.12.1 went live on July 29, 0.12.1.1 followed on July 30, and 0.12.1.2 and 0.12.1.3 both landed on July 31. Three hotfixes inside three days of a major update. Launch week will look the same, only busier, because console clients arrive on September 15 and console patches do not always ship at the same hour as the Steam build.
Your Launch Week Checklist
Five things worth doing before September 15:
- Take a manual backup on September 14. A major version transition is the one moment a save file is genuinely at risk. Do not lean on the automatic schedule alone.
- Be ready to restart, not just update. Budget a few minutes on every patch day. A stale server build reads to players as "the server is down" even while it is running perfectly.
- Size for a bigger roster. Crossplay plus a finished-game launch means more concurrent players than your Early Access peak. Plan for roughly 1.5x your usual concurrents rather than matching them exactly.
- Send the connect details out early. Console players joining for the first time have never touched your server address. Get it to them before launch day, not during it.
- Do not wipe in September. Shared progression is what carries a group through the Saga. Save the fresh world for Luminance in the Winter if you want one.
The Short Version
Dragonwilds arrives finished on September 15 at the price it has always been, with monthly updates and a named Winter release already committed. For a game that lives or dies on whether a group of friends keeps logging into the same world, that is the good outcome. The work on your side stays small and predictable: back up before launch, restart after every patch, and leave headroom for the people who were waiting for 1.0 to buy in.
If you are standing a server up for launch week, our Getting Started with Your RuneScape: Dragonwilds Server guide covers the first-run configuration, and our 1.0 release breakdown has the full content list and the crossplay details. You can also rent a RuneScape: Dragonwilds server from us with instant setup if you would rather not run one at home.
