RuneScape Rolled Back Its Servers After a Game Jam Bug Handed Players Trillions of Runes

A quality-of-life update turned into a full server rollback after a rune bug spiraled out of control faster than Jagex could contain it.

As part of the Game Jam update, a number of quality-of-life changes made their way into RuneScape. These updates come off the back of internal hackathons where Jagex developers are free to work on whatever they like.

One of the most notable changes this time around was the removal of the 16,000 rune cap on the rune pouch, replacing it with an unlimited capacity. A welcome change on paper, and exactly the kind of thing players had wanted for a while.

It didn't quite go to plan.

A Bug With Very Big Numbers

Shortly after the update went live, reports started coming in of players logging in to find their rune pouches absolutely stuffed. Not just a few extra runes, but figures in the trillions. Some players reportedly had 1.5 trillion runes sitting in their inventory, a number that almost sounds made up until you're staring at it on your screen.

The problem wasn't just the scale of it. These runes could be sold. Within a short window of the bug becoming widely known, the RuneScape economy was already starting to buckle under the weight of it – the price of water runes had already dropped to 1 gold each, which gives you a reasonable sense of the kind of damage that was unfolding.

Jagex Moved Quickly

Just over an hour after the situation became widely reported, the servers were taken offline. By the time Jagex posted their statement on Reddit, they had already made the call: a full rollback, returning all player progress to the state it was in at 10:30 AM UTC, when the morning's update had gone live.

In their own words, the amount of runes that could flow into the economy "would cause irreparable economic damage and challenge the economic integrity of the game." The spread was too fast, and the number of affected players too large to address individually in the time they had available.

This is where things get difficult. A rollback is never a clean solution. For a lot of players, those hours contained real, meaningful progress, especially when considering that the rollback went about an hour further back than the update itself. Boss drops they had been grinding for. Masterwork bow progress. Capes.

Jagex acknowledged this directly, expressing empathy for anyone who lost progress they had worked for. Whether that softens the blow is another matter.

A Familiar Risk With Live Games

Bugs introduced through well-intentioned updates aren't unique to RuneScape, and a quality-of-life change removing a cap creating an exploit is almost poetically GameDev. The Game Jam format, where developers have more freedom to push changes through, adds an interesting wrinkle here – it is precisely this kind of structure that allows for both creative output and unforeseen consequences.

Jagex's response time was notably fast, and the decision to act rather than wait appears to have been the right call, given how quickly the economy was already reacting. The rollback is inconvenient at best and genuinely gutting at worst for those affected. For the wider health of the game, however, the alternative would likely have been far messier to clean up.