RuneScape Rollback Over Trillions of Runes - What Happened on April 20

RuneScape faced an emergency rollback on April 20, 2026, after a Rune Pouch bug created a serious risk to the game's economy. The issue appeared after a quality-of-life update increased Rune Pouch capacity, letting existing Rune Pouches hold up to 2,147,483,647 runes of one type. Instead of only expanding storage, the update caused some players to log in with abnormal rune amounts in their pouches.

Jagex said the bug made it possible for players to duplicate billions of runes per person. PC Gamer and player reports described cases reaching trillions of runes, but the official Jagex explanation focused on billions per affected player and the wider economic risk. Because the bug spread quickly and could not be safely cleaned up account by account in time, Jagex rolled RuneScape back to the 10:30 UTC snapshot from the release of the morning update.

RuneScape Rollback on April 20 Started With the Rune Pouch Update

The rollback came from a Rune Pouch change that looked simple on paper. Jagex wanted existing Rune Pouches to match the storage scale players had seen with the Necromancy Nexus, so the update raised pouch capacity to 2,147,483,647 runes of a single type. That number is the signed 32-bit integer limit, because even fantasy economies eventually run into software engineering and its little collection of ancient traps.

The live result was not just larger Rune Pouches. After the update, some players found extreme rune quantities in their pouches. Jagex's emergency PSA said the bug allowed duplication at a scale of billions of runes per person, while PC Gamer and player screenshots pushed the public conversation toward "trillions of runes." The important distinction is simple: "billions per person" is the official Jagex wording, while "trillions" comes from media coverage and player-reported examples.

That distinction matters because the story is not only about a funny number appearing in an inventory. Runes are core consumables for Magic, combat, utility spells, trading, and the wider RuneScape economy. A large duplicated supply could damage prices, create unfair wealth, and undermine confidence in the market. For a player-driven MMO economy, that is not a cosmetic bug. That is a hole in the floor.

Jagex Used a Full RuneScape Rollback to Protect the Economy

Jagex said the bug was spreading too quickly for a targeted cleanup to be reliable. A selective fix would have required identifying affected accounts, removing duplicated runes, and tracing any movement of those runes before they could spread further through normal economic activity. In a live MMO, that kind of cleanup becomes harder every minute the game stays online.

The studio described the rollback as a last-resort decision. RuneScape was taken temporarily offline while Jagex fixed the underlying issue, then brought back online after the rollback. The rollback returned all player progress to the state it was in at the release of the morning update, using the 10:30 UTC snapshot.

That means the rollback did not only affect players who received bugged Rune Pouches. It affected everyone who played after the snapshot. Legitimate progress made during that window was lost, including skilling, combat drops, quest steps, trades, purchases, clue rewards, and other normal activity. It was a blunt solution, but Jagex's position was that letting duplicated runes move deeper into the economy would create a larger and more permanent problem.

RuneScape Players Lost Progress After the 10:30 UTC Snapshot

The rollback point was clear: RuneScape returned to the 10:30 UTC snapshot from the release of the morning update. Any activity after that point was not preserved. This included normal progress from players who had nothing to do with the Rune Pouch bug, which is why the decision frustrated part of the community even though the reason for it was easy to understand.

Player comments under the official PSA included reports of lost drops, lost quest progress, lost token progress, and confusion over how the rollback point lined up with each player's session. That is the cost of a general rollback: it protects the shared game state, but it also erases honest progress from unaffected players. Jagex chose that cost because the alternative was allowing duplicated runes to remain in circulation long enough to become harder to separate from legitimate activity.

The key point is that this was not a punishment wave, a planned reset, or a balance change. It was an emergency rollback caused by a live economy risk. The bug created abnormal rune quantities, the spread was too fast, and Jagex decided that a short universal rollback was safer than a slower investigation while the economy remained exposed.

RuneScape April 20 Rollback Timeline

Billions or Trillions of Runes: The Important Difference

The cleanest way to describe the scale is this: Jagex officially said the bug allowed duplication of billions of runes per person, while PC Gamer and player reports described cases involving trillions of runes. Both points can appear in the same article, but they should not be treated as the same kind of evidence. One is the developer's official explanation. The other is media and community reporting around visible examples.

This matters for accuracy, not because the difference changes the seriousness of the bug. Billions of duplicated runes per person would already be enough to threaten a live MMO economy. Trillions make the story more dramatic, and the screenshots helped drive attention, but Jagex did not need to prove a specific trillion-level total to justify the rollback. The official reason was the speed of the spread and the risk of irreparable economic damage.

For RuneScape, duplicated runes are not isolated inventory clutter. They can affect supply, prices, player wealth, and trust in the legitimacy of trades and item values. Once a duplicated resource moves through enough transactions, cleanup becomes slower, less precise, and more likely to harm innocent players later. That is why a quick rollback, ugly as it was, made more sense than waiting for a perfect targeted fix that might never arrive in time.

The Clean Read on the RuneScape Rollback

The April 20 RuneScape rollback was caused by a Rune Pouch update that went wrong. The intended change was larger pouch storage, bringing Rune Pouch capacity up to 2,147,483,647 runes of one type. The live bug created abnormal rune amounts for some players and made large-scale duplication possible.

Jagex rolled the game back to the 10:30 UTC snapshot, temporarily took RuneScape offline, fixed the underlying issue, and restored service afterward. The rollback erased legitimate progress from unaffected players, but Jagex framed it as the safer option compared with leaving duplicated runes in the economy and trying to untangle the damage later.

The confirmed facts are narrow but clear. This was an emergency rollback, not a planned reset or a disciplinary action. The official scale was billions of duplicated runes per affected player, while media and player reports described examples reaching trillions. Either way, the result was the same: a Rune Pouch quality-of-life update briefly became a major economy threat in a game literally named RuneScape. Sometimes the joke writes itself, then deletes everyone's progress after 10:30 UTC.