Back to BlogHISTORY

The Fall of Falador (2006): the Durial321 massacre explained

The Fall of Falador — the 6 June 2006 Durial321 massacre — is OSRS history. How the glitch worked, who died, and how Jagex responded.

OSRS HistoryOSRSFall of Falador 2006
Quick answer

The Fall of Falador (2006): the Durial321 massacre explained

The Fall of Falador was a game-breaking glitch on 6 June 2006, the same day the Construction skill launched. A server-side PvP flag meant to mark players in the wilderness or a minigame was not cleared when a player left those areas. The player Durial321 exploited the lingering flag to attack and kill other players anywhere in the world, mostly in Falador, where hundreds of players died and lost their entire inventories — there were no gravestones or death chests in 2006, so everything dropped on the floor. Jagex responded by rolling back the game servers by several hours to restore lost items, banning Durial321, and patching the bug. The incident became one of RuneScape's most legendary events, and it was memorialised in 2016 with a special World 666 anniversary event where players fought an NPC Durial321 for a green partyhat drop.

Key takeaways

  • The Fall of Falador happened on 6 June 2006, the day Construction launched, when a PvP flag failed to clear after leaving a minigame/wilderness.
  • Durial321 exploited the glitch to attack other players in safe zones, killing hundreds of players in Falador.
  • In 2006 death dropped your entire inventory on the floor with no gravestones, so victims lost everything they carried.
  • Jagex rolled back servers by hours to restore lost items, banned Durial321, and patched the bug.
  • The event is commemorated in OSRS via the 2016 World 666 anniversary event (NPC Durial321, green partyhat drop).
01

What happened on 6 June 2006

The Fall of Falador began as a bug introduced by the Construction skill update on 6 June 2006. Players could build Player-Owned Houses and move between worlds using the new House Teleport, and the update also touched how the game tracked players who had recently been in the wilderness or a PvP minigame.

The bug left a small number of accounts flagged as 'attackable in the wilderness' even after they had left the wilderness. Durial321, a level-126 player, discovered that the flag stayed active in normal, safe areas of the game, which let him attack and kill other players who could not fight back or escape.

Durial321 began his rampage in Falador's busy town square, where hundreds of players were gathering. Because so many players were clustered there, he was able to kill a huge number of them in a short window before being stopped.

02

Why it was so damaging: 2006 death mechanics

The massacre was especially devastating because of how death worked in 2006. When a player died, their entire inventory and worn equipment dropped to the floor in a single pile — there were no gravestones, no death chests, and no item retrieval services.

This meant every victim of the massacre lost everything they were carrying: partyhats, whips, dragon armour, and other items worth hundreds of millions of gold pieces in total. In the chaos, the dropped items were picked up by other players, and some could not be recovered at all.

The financial loss across the server was enormous by 2006 standards, and the emotional impact on the victims made the event legendary in the community.

03

Jagex's response and the rollback

Jagex acted quickly once the bug was confirmed. They rolled back the game servers by several hours, which restored the items lost during the massacre and effectively erased the damage from the incident.

The account Durial321 used was banned, and the underlying glitch was patched so the wilderness flag could no longer persist into safe zones. The rollback also meant that players who had legitimately gained items or progress during those hours had that progress reversed as well.

The incident became a defining moment in RuneScape history, discussed for years afterward and used as a cautionary example of how quickly a single game-breaking bug can reshape a world.

04

The legacy: the 2016 World 666 event

In 2016, for the 10th anniversary of the massacre, Jagex ran a commemorative event in OSRS. Players could enter World 666, an unrestricted world, teleport to Falador, and take part in free-for-all PvP, or fight an NPC version of Durial321.

The player who dealt the most damage to the NPC Durial321 was rewarded with a green partyhat drop — a nod to the rare items that were lost in the original event. A unique track called 'Massacre' played during the event.

The Fall of Falador remains one of the best-known stories in RuneScape and OSRS history, remembered both as a cautionary tale about bugs and as a defining community moment.

Questions players ask

Questions players ask

What was the Fall of Falador?+

A game-breaking glitch on 6 June 2006 (the day Construction launched) that let the player Durial321 attack other players in safe zones, killing hundreds in Falador.

How did the Durial321 glitch work?+

A server-side wilderness/PvP flag was not cleared when a player left those areas, so Durial321 stayed flagged as attackable-in-the-wilderness and could attack players anywhere.

How did Jagex fix the Fall of Falador?+

Jagex rolled back the servers by several hours to restore lost items, banned the Durial321 account, and patched the glitch.

Did players lose items in the massacre?+

Yes — in 2006 death dropped your whole inventory on the floor with no gravestones, so victims lost everything, later restored by the rollback.

How is the Fall of Falador commemorated in OSRS?+

The 2016 World 666 anniversary event let players fight an NPC Durial321 for a green partyhat drop.

Sources and verification

Sources and verification

These references support the game mechanic or live-data boundary described above. Check the current source before a large in-game decision.

Editorial reviewPublished and reviewed by the LootPath editorial team

Independent fan-made OSRS content. No Jagex affiliation or endorsement.