The July 12, 2018 max cash incident occurred when an update designed to prevent pickpocketing automation contained a fatal flaw in the player death script, causing dropped item stacks to convert into 2,147,483,647 coins. Whenever an exploit of this magnitude corrupts the economy, players must immediately halt all trading, avoid picking up illegitimate items, and log out until developers complete a server rollback.
How the Coin Pouch Update Triggered Max Cash Drops
Jagex introduced coin pouches to curb automated pickpocketing at high-efficiency Thieving targets, primarily the Knights of Ardougne. Under this system, pickpocketing rewarded untradable inventory pouches that required manual clicks to open rather than generating loose gold directly.
Because coin pouches were untradable, developers added a conversion routine to handle player deaths. When a character died, the game engine was programmed to convert all held pouches into standard coins for the killer or ground drop. However, the update script contained a critical logic error. Instead of calculating the precise sum of coins contained within the player's pouches, the script assigned the maximum allowable value of a 32-bit signed binary integer (2^31 - 1), setting the dropped stack size to exactly 2,147,483,647 gold. Any player holding qualifying item stacks who suffered a lethal blow immediately spawned max cash onto the ground.
Once the glitch became public knowledge, players repeatedly committed suicide against aggressive NPCs in Lumbridge or eliminated each other in PvP worlds, generating hundreds of billions of coins within minutes. Traders then flooded the Grand Exchange in attempts to convert duplicate cash into high-value items such as the Scythe of Vitur and Twisted Bow.
| Mechanic | Intended Functionality | July 12, 2018 Bugged State |
|---|---|---|
| Coin Pouches on Death | Convert pouches into face-value loose gold | Dropped the maximum 32-bit cash stack (2,147,483,647 GP) |
| Stackable Item Behavior | Drop standard quantities based on inventory state | Overwrote quantity parameters with the maximum integer |
| Ground Loot Spawns | Standard loot timers tied to player or killer | Max cash spawned visibly across high-traffic areas like Lumbridge |
| Server Response | Normal automated tick processing | Required server shutdown and a full database rollback |
What to Do During Economy Glitches and Rollbacks
When a severe duplication bug or item glitch appears in Old School RuneScape, act immediately to protect your account and wealth from automated penalties and lost progress.
- Cease all trading immediately: Do not buy, sell, or accept items via player-to-player trade or the Grand Exchange. Transactions conducted during an active exploit window are either erased during database rollbacks or risk leaving your account flagged with illegitimate assets.
- Leave duplicated wealth on the ground: Never intentionally pick up bugged items, loot abnormal cash stacks, or participate in organized death loops. Jagex tracks rapid inventory wealth spikes, and exploiting game-breaking glitches violates Rule 4, resulting in permanent account bans.
- Pause high-value progression milestones: Stop running high-tier bosses, finishing Grandmaster quests, or hunting rare drops. When developers initiate an emergency rollback, server memory reverts to a backup snapshot captured before the exploit began. Any legitimate progress achieved between that snapshot and the server shutdown will be permanently erased.
- Log out in a safe area: Move your character to a bank or non-hostile zone and log out to preserve your inventory state safely.
- Monitor official communication channels: Check the Old School RuneScape website, official Discord, and developer Twitter/X feeds for status updates regarding downtime, exploit mitigation, and the timestamp of the incoming rollback.
Emergency Rollbacks and Long-Term Safeguards
The 2018 max cash glitch forced Jagex to execute the first full server rollback in Old School RuneScape history. Developers had traditionally avoided rollbacks because wiping server history invalidates legitimate achievements, rare pet drops, and Hardcore Ironman statuses. However, the trillions of coins generated in under an hour threatened permanent hyperinflation, leaving a database reset as the only viable solution.
The incident established technical safeguards that continue to protect the game. Jagex instituted stricter pre-deployment testing specifically targeting death scripts and inventory conversions. The development team also refined server snapshotting frequency, reducing backup intervals from hours to minutes. This enhanced infrastructure proved critical during subsequent emergencies, such as the 2019 Twisted Bow spawn bug, allowing rapid server reversions with minimal disruption to legitimate player progress.
Free Old School RuneScape Codes
Current active codes and how to redeem them.
COMMUNITY
Player Comments
126 players commented on this guide.
Can you add more details about strategy in a future update?
The explanation is clear, especially for beginners.
Nice guide. I am checking the other Old School RuneScape articles next.
I wish I had read this before upgrading the wrong thing.