Jagex Cancels Its RuneScape Reset Plan at Lightning Speed: Killed Under Two Weeks After Announcement, and the Route Battle Over Remaking Old Games#

Zhanlan Yingren | October 17, 2026

Hi everyone, Zhanlan Yingren here. Everyone in this line of work carries some youth soaked in old MMOs. I came up through Stone Age, so words like “legacy servers” and “the game as it used to be” trigger something almost instinctive in me. So when the veteran British MMO developer Jagex announced a “legacy-server reset” plan for RuneScape — a game it has run for 25 years, by foreign-media accounting — on October 3, then killed it with its own mouth on October 15, I stared at the story for a long time. From announcement to cancellation: 12 days, which English-language outlets framed as “under two weeks.”

12 days. A flagship project trumpeted at a company’s annual event, snuffed out by its own hand in under two weeks. In the live-service MMO industry, that is an extraordinarily rare move — some foreign media went so far as to call it a “lightning-fast rollback.” What’s more intriguing is the reason for the kill: not lost funding, not broken technology, but the old players refusing to accept it.

In today’s piece, I want to take this apart start to finish as an old-MMO player: what kind of blueprint the reset plan actually offered players, why it pushed the most loyal players to the opposite side, how the officials retreated in three steps across 12 days, and the twelve-year-old overhaul wound that still shapes this company’s decisions. At the end, we’ll widen the lens, line the plan up against Blizzard’s and Sega’s old-game revival routes, and talk about how much community voice really weighs in remaking old games.

1. Twelve Days From Announcement to Cancellation: A Rare Timeline#

First, the skeleton of the event. All dates below are cross-checked across multiple reports:

The rhythm on this table is unmistakable: announce (the 3rd), concede (the 6th), compromise (midweek), kill (the 15th) — each interval shorter than the last. Industry outlet Pro-Gamer noted in its recap that a live-service MMO operator scrapping a flagship announcement wholesale within two weeks of unveiling it, over community backlash, is rare in this business — that is media commentary, so I flag it as such before relaying it.

Also worth noting is the gap between official promises and delivery speed. In the October 6 news post, the officials promised “multiple revision options within the week”; as it turned out, that week indeed produced a compromise option first — and then they leapfrogged the compromise straight to cancellation. In other words, this rollback was not an emotional slam on the brakes; it was a decision made only after days of verifying that revision options could not save it. For a project announced with fanfare at an annual event, that decision density itself measures how heavy the backlash was.

Incidentally, just the day before, this site ran a recap of another old-game revival gone wrong — Sega’s two-day emergency delisting of Total War: Shogun 2 Complete Edition (see SEGA Delists Total War: Shogun 2 Complete Edition Within Two Days). The two stories landing in the same week make a striking contrast, but their natures are completely different: Sega’s was single-title damage control after a remaster’s quality failed; this one is a wholesale rollback after the direction itself was voted down by the community. One is about “was it done well,” the other about “should it be done at all.” We’ll unpack that distinction in section seven.

2. The Reignited Blueprint: A “Clean Room” for Newcomers, Paid for With a Wall#

To understand why the veterans exploded, you first have to see what the officials actually served up. Per the original setup announced at RuneFest, Reignited was neither a new expansion nor a new server, but a brand-new character type inside the game: players could create a “Reignited character” and experience the old game from zero. Original launch date: December 2, 2026.

Organize the announced mechanics into a table and the picture sharpens:

Read on its own, the design intent is actually quite clear: the officials wanted to open a “clean room” for newcomers and for players who wanted to run it all again — no decades-deep economy gap, no loot-box lottery, no paid items, a blank page from which to experience an old game “unpolluted by twenty-plus years of accumulation.” That official news post title — “As It Was Always Meant To Be” — is exactly the point.

Unpacked, the blueprint stacks three promises:

• For newcomers: a complete growth path from zero, an economy not monopolized, resources not bought with wallets;
• For returning players: a starting line independent of twenty years of drift — even veterans could re-experience the early grind;
• For the old community: social ties unbroken — same worlds, same chat channels, same clans; the officials repeatedly stressed “parallel,” not “split.”

The first two promises were genuinely appealing; the problem lay entirely in how the third was implemented.

And it didn’t fully sever the two groups: Reignited players could share worlds, chat, and clan up with veterans — socially, not alone. The officials even prepared ceremonial flourishes like the “Hall of Legends,” where the first players to hit specific achievements would leave permanent statues.

But the problem hid in exactly the price of that “clean.” The new house’s door was locked: a separate economy meant only Reignited players listing on the Reignited Grand Exchange, fully walled off from the main servers’ economy; no trading and no shared group bosses meant no genuine in-game cooperation between new and old players. The blueprint drew a wall and told everyone: people on both sides may talk through the wall, but can’t pass anything across it, and can’t fight shoulder to shoulder.

Interestingly, the blueprint’s twin strokes — “no Treasure Hunter, no Radiant Stars” — trace straight back to Jagex’s route this year: early in the year, the new chief executive, Jon Bellamy, led the removal of Treasure Hunter and other destructive monetization (more in section six). In other words, Reignited was, at the design level, meant to be a “de-monetized show home”: showing newcomers a RuneScape without loot boxes, without paid stars, with an economy starting from zero. The motive wasn’t bad; the implementation was — it didn’t clean the main servers, it built a separate clean subdivision next door and left the main servers’ longtime residents standing where they were.

To borrow a metaphor every old internet user knows: this is the reverse of a server merge — not merging several servers’ populations into one lively crowd, but fencing part of the population into a newer, cleaner courtyard and then shutting the gate.

3. Three Fuses: Dual Subscriptions, a Split Community, and the Shadow of a Record#

Once the blueprint dropped, backlash ignited almost instantly. Sorting through the media coverage, three fuses stand out.

3.1 The First Fuse: Dual Subscriptions, a Veteran’s Ledger#

This is the most concrete and most cutting item. Under the original plan, Reignited characters could access member worlds and content for free from December 2 to 12 — a mere 10-day trial window; once it closed, every Reignited character required its own membership, $14.99 a month at current pricing, and it did not stack with an existing account’s membership.

Run the numbers: a veteran wanting to play both sides pays one subscription for the main account and another for the Reignited character — the monthly bill doubles outright — while everything on the Reignited character starts from zero. Media coverage did this math explicitly, and the conclusion stings: you have poured twenty years of time and subscription fees into this game, and to enter that “clean future” you start over — and pay more.

The free window backfired here — a 10-day trial reads like a promotion, not respect. What veterans saw wasn’t an invitation; it was the sales pitch for “installment payments into another world.”

3.2 The Second Fuse: Fear of a Split Community — Hitting an Old MMO’s Lifeline#

RuneScape is not a vast, national-scale MMO. The veterans’ worry was blunt: the player base was already on the small side; once Reignited launched, it would siphon the already-limited flow of newcomers into a quarantine zone, drain the main servers’ fresh blood, and leave the rest guarding a world that slowly went quiet.

For an old MMO whose lifeblood is a player-driven economy, “people” are the infrastructure — the ones listing on the Exchange, chatting in clans, tanking the boss. Split the people and you dismantle the infrastructure. The blueprint’s “same worlds, chat, same clans” sounds like preserved community, but once trading and cooperation are severed, the two groups drift apart in daily play — a game world’s social fabric never runs on “can say hello”; it runs on “must deal with each other.”

3.3 The Third Fuse: The Shadow of a Record — 2022 Kept Coming Up#

In 2022, the officials ran a temporary-server experiment called “Fresh Start Worlds” — again from-zero characters, again a separate economy. That attempt’s lesson became the most persuasive argument in this backlash: this road has been walked before. When the officials packaged “reset” as major innovation on the RuneFest stage, plenty of people were thinking: isn’t this just the temporary servers with upgrades?

The record’s significance is that it upgraded the community’s vigilance from “is this plan good” to “is this direction viable.” Plans can be revised, prices adjusted — but if the direction itself was tried four years ago, more explanation is just relamping the same road.

The backlash didn’t stay on the forums. Per multiple outlets, some players protested inside the game itself — existing reports give no reliable data on the scale or form of participation, and I won’t speculate — but “the protest burned into the game world” says enough about the fire’s size.

Then there is the cut that hurts most: players holding 20-year-old accounts found that under the original plan, the only way into the officials’ “clean future” was to abandon twenty years of progress and start a new character. For an old-MMO player, an account isn’t a string of data — it is a twenty-year personal save file. The blueprint’s line about “returning to where it began” sounded, in these ears, like “your first twenty years were a waste.”

4. Three Steps Back: Re-Evaluation, Compromise, Formal Cancellation#

Facing this backlash, Jagex’s response speed deserves a record of its own. The process ran in three steps, each a retreat.

Step one, October 6: own it. The officials published a news post titled “Reignited: Where We Go From Here.” It acknowledged the community backlash, announced a re-evaluation of the plan, and promised multiple revision options within the week. Note the timing: just 3 days after the announcement. A company slamming the brakes while its annual event was still warm — that signal alone says the backlash exceeded expectations. And this response skipped the “thanks for the feedback, we’ll keep optimizing” boilerplate, flatly admitting the direction needed re-evaluation — unusual humility for a veteran operator built on the long haul.

Step two, midweek: compromise. The officials followed with a revision whose core was letting players convert existing accounts onto the Reignited path with a single membership — effectively patching the “two subscriptions” pain point first. It didn’t work; the backlash continued. To be fully transparent: this compromise’s complete rules exist only as a single media outlet’s summary; the official post has not been widely retrievable, so the details are uncertain. I’ll state only the multi-source confirmed part — the option shipped, the backlash didn’t stop. The result isn’t hard to understand: what the community opposed was never just the subscription fee, but the direction of “splitting” itself. Prices can be tuned; whether the wall comes down is the vital point.

Step three, October 15: kill it. Deputy creative director Philpott formally announced via official video plus blog: Reignited would not proceed. Two lines from that video belong in the industry archive, verbatim —

“Clearly we didn’t get the direction right, so we’re not moving forward.”

“Our goal is to see RuneScape grow again, but never at the cost of the existing community.”

Philpott also voluntarily dug up a twelve-year-old account as the cautionary tale: last time we didn’t listen to player feedback, combat changed forever, and it took us over a decade to recover. That self-indictment points at the famous November 2012 “Evolution of Combat” (community shorthand EoC) overhaul — more in section five.

Alongside the cancellation, the officials itemized “what stays,” so players wouldn’t burn December 2 down along with the plan:

The roadmap’s later content also stands: Hoard of Dragons, containing the Agility skill rework and Dragon Slayer II-related content; City of Gnomes; Secrets of Karamja; plus the conclusion of a gnome storyline spanning 15 years and a new group boss raid. In other words, what got cancelled was the “reset” direction, not the game’s update rhythm.

One easily missed detail hides in this keep list: the free-membership window survived, but its audience changed. Under the original plan, the window was the trial channel for Reignited characters; after the cancellation, it became a window for new characters and for accounts that have not held membership since June 2, 2026 — from “recruiting for a parallel server” to “recalling lapsed veterans to the main game.” Same December 2, same membership gift, but the target moved from “building a new hearth” back to “repairing the old house” — and that pivot is the officials’ most direct statement on the whole affair.

5. The 2012 Scar: Why a 25-Year-Old MMO Is Still Litigating a Twelve-Year-Old Overhaul#

This is the section I most wanted to write, because it is the most “old MMO” detail in the whole affair.

The history behind the passage Philpott cited deserves filling in: in November 2012, the officials performed major surgery on RuneScape’s combat system — the aforementioned Evolution of Combat overhaul. It drove a massive player exodus and tore the community so deeply that the game ultimately split outright along version lines: some players stayed on RuneScape 3, which kept the new combat route, while others gathered on Old School RuneScape — two versions walking separate roads ever since.

Fourteen years later, a deputy creative director announcing the death of a reset plan opens by admitting to players: last time we didn’t listen, and it took us more than a decade to recover. Lay this history beside the current affair and the officials’ decision logic is shadowed by old wounds throughout:

A game that has run for 25 years using a decade-old scar as direct input to a current decision — that is the live-service community’s peculiar “memory mechanism,” and I have rarely seen its like in any other game genre.

Think about the veterans’ context and it’s clear: for a single-player game, a controversy from three years ago already counts as “history”; but in a world where some players have played for twenty years, the 2012 overhaul is living memory — friends who left over that unwilling overhaul are still fishing and woodcutting on Old School servers today. The community’s wariness about “will they do it again” was purchased with real, measurable losses. So when words like “isolation” and “fresh start” appeared in the Reignited blueprint, what triggered wasn’t an evaluation of a new plan but a stress response to an entire history.

Seen this way, the 12-day cancellation is the terminus of a causal chain: the microtransaction cleanup since early in the year repaired part of the trust; Reignited nearly burned through that freshly repaired trust; and in the end, that fourteen-year-old scar spoke the community’s heaviest argument against the plan. The fast rollback is, in essence, one more apology paid to that history.

6. “We Said No, and They Removed It”: The Winning Chain of Community Voice#

After the cancellation was announced, the community’s dominant reaction was positive. One player on Reddit left a summary that got widely reposted: “We rejected Hero Pass, and they removed it. We rejected Reignited, and they removed it too.” Among players, it stands as the marker of an official listening to its community and rebuilding trust.

Place that line on this year’s timeline and the chain behind it is genuinely complete:

The chain teaches one thing: in a subscription-based long-running MMO, players are not just “users” — they are closer to “partners.” Their subscriptions are the stable cash flow, their twenty-year accounts are community assets, and their word of mouth decides whether an old game can still attract newcomers. When an operator stakes “renewed growth” on sacrificing these people, the backlash isn’t an emotional problem — it’s an interest problem. The veterans are defending their assets.

Push the chain half a step further back and a deeper logic appears: Bellamy’s microtransaction cleanup and Reignited’s “no Treasure Hunter, no Radiant Stars” design were, in direction, the same project — pulling the game back out of short-term monetization. But the former was “subtraction inside the existing world,” while the latter was “build another world” — and the latter trampled the very people the former was meant to reassure. Same direction, contradictory method: that is why a blueprint that should have been a crowd-pleaser ended up needing a fourteen-year-old scar to close the show.

A bucket of cold water is also due: cancellation-as-damage-control is still just that; it doesn’t mean every future step will bow to the community. The “renewed growth” goal remains — it now simply runs under a new constraint line that forbids sacrificing the existing community. How that constraint is honored will show in the delivery quality of the roadmap’s content. But at least on the specific matter of “listening,” the record this company filed this year is more honest than most of its peers'.

7. Three Routes: Blizzard Digs In, Sega Delists, Jagex Rolls Back#

Old-game revivals have produced three very different answer sheets in recent years. Side by side, they are fascinating.

(The full rundown of Reforged’s launch fiasco lives on our Warcraft III: Reforged guide hub’s FAQ page — no need to repeat it here.)

Three routes, three lessons. Blizzard’s lesson is the price of digging in: the product route was wrong but wouldn’t roll back; refunds stopped the headlines, not the reputation damage — a classic IP’s remaster pushed players straight onto third-party battle platforms. Sega’s lesson is the delivery floor: remastering is fine, but when quality collapses, pull it fast — a two-day delisting at least preserved the “owns its mistakes” posture. And Jagex’s sample this time is respect for direction: when a reset direction contradicts the core demands of your most loyal users, killing the whole plan is cheaper than patching it — patching a wrong-direction plan only carries the error further.

The three also share a commonly overlooked trait: in all three storms, the loudest objections came not from new players but from each community’s most senior members. That’s not hard to understand — a remake’s first buyers are always the veterans, and veterans are the only ones who remember the original down to every detail. Their obsession with “the game as it used to be” is the acceptance standard of any revival project itself. Whoever treats veterans as a replaceable legacy base against a new blueprint will get the bill on launch day.

For operators brewing old-game revival plans, this 12-day cancellation leaves three homework items ready to copy: first, run user research before announcing, and above all listen separately to the players with old accounts, rather than moving yourselves on a stage; second, old accounts and old progress are the veteran’s core assets, and no new path should be designed to make them the “default sacrifice”; third, community voice in a live service is real means of production — invisible in calm, and able to kill an annual project in 12 days the moment you cross the line.

Looking back, the Reforged crowd’s demand and this RuneScape veterans’ demand have identical cores: we don’t want a new coat — we want the original. Blizzard didn’t hear it back then; that 0.5 on Metacritic spoke for the players. Jagex heard it this time — the cost was 12 days of chaos; the return was a 25-year community still in its own hands.

8. Closing: How Much Is “the Game as It Used to Be” Worth? Veterans Set the Price#

Finishing this piece, I sat in front of the screen for a long time, thinking about my own Stone Age nights.

The proposals for old-game remakes always lead with “modernization” and “fitting contemporary player habits.” But the most glaring fact of this affair is that the first to rise against a clean, beautiful, newcomer-friendly reset blueprint were precisely the veterans the officials most hoped to keep. The reason, said aloud, is almost embarrassingly simple: to the people who played for twenty years, “the game as it used to be” is not a nostalgia filter — it is proof that their youth was not rewritten. The old graphics’ roughness, the old systems’ clumsiness, the old economy’s accumulated weight — outsiders read these as “outdated”; they read them as physical evidence that “I was here.”

From that angle, I can understand the people who protested inside the game. Our generation lived through too many “for your own good” overhauls: servers merged and split, interfaces changed and changed again, friends from the old pet-catching days scattered across every “fresh start.” So watching a company admit “we didn’t get the direction right” within 12 days and take back a beautiful-looking blueprint with its own hands, what I thought wasn’t “this company has no spine” — it was “this time, they put people ahead of the blueprint.”

The route wars over old-game remakes will probably rage for many years. But these 12 days in October 2026 left at least one precedent: in a live-service MMO, when the community says no, it can count.

— Zhanlan Yingren, NTGame Art Editor