How a house-party bug reached Falador
RuneScape normally separated player-versus-player combat from safe towns such as Falador. That boundary was a game rule: in designated areas, players could not simply attack one another. A glitch tied to the newly introduced player-owned house mechanics let attackers carry permission to fight beyond the place where it was supposed to apply.
The key was the transition between spaces. Combat behavior inside a house could be manipulated so that, after leaving, a player remained able to attack in places where the rules should have blocked it. In effect, the game failed to properly reset a player’s combat status when they crossed the boundary.
Why the attack spread so quickly
Falador was a busy city, not a battlefield. Players there were not expecting to be attacked, and many had valuable items with them. Once the exploit was used in public, victims had little warning or time to escape. Attackers could kill them and take their dropped belongings, turning a software error into a large-scale loss for players.
The episode became known as the Falador massacre because the contrast was so striking: a peaceful hub suddenly behaved like a player-versus-player zone. It also showed how a seemingly local feature can affect the wider game. The house mechanics did not need to change Falador’s rules directly; they only had to leave behind a combat state that those rules were meant to prevent.
For game developers, the incident illustrates a difficult boundary problem: when a character moves between areas with different permissions, the game must consistently recheck what that character is allowed to do. In Falador, one missed transition was enough to turn a safe city into a place where players could be hunted and looted.
