An excerpt from a 2013 university talk by Valve co-founder Gabe Newell has resurfaced online, reviving a design debate that remains highly relevant to live-service games, MMOs, sandbox worlds, and community-driven online experiences. Newell's point is deceptively simple: developers can make a serious mistake when they classify a surprising but entertaining player action as nothing more than hacking.
The widely circulated clip comes from a longer appearance Newell made at the University of Texas' LBJ School of Public Affairs. During a question about the security risks inherent in interactive digital worlds, Newell drew a line between malicious technical abuse and the kinds of unforeseen events that can become part of a game community's shared history.
"First of all, there are multiple kinds of hacking," Newell said in the talk. "One of the biggest mistakes game developers make is to mistake a genuinely entertaining action by a player as hacking."
To explain what he meant, Newell returned to one of PC gaming's best-known MMO stories: the day Ultima Online's Lord British was killed in public by a player. The incident, which occurred in 1997, was the result of a real vulnerability created during a live event. Yet Newell's interest was not primarily in the bug itself. His argument was that the aftermath could have become an enduring piece of the world's fiction rather than an event to be undone.
For useful background on this topic, read Palworld: Palfarm Won't Simply Be 'Stardew Valley With Pals,' Pocketpair Lead Says.
The assassination of Lord British
Richard Garriott, a foundational figure in computer role-playing games and the creator behind Ultima, used the in-game identity Lord British. In Ultima Online, Garriott sometimes appeared in that persona during events, usually protected by invulnerability.
On August 9, 1997, a server crash disrupted one of those events. When Garriott returned to the game, Lord British's invulnerability had reportedly not been restored. That left the character exposed in a crowded online world full of players eager to test the boundaries of a then-new kind of persistent multiplayer game.
A player named Rainz cast a fire spell at Lord British and killed him. In an era when an MMO's unscripted public moments could still feel truly unprecedented, the apparent assassination immediately became legend. It was not simply a player defeating a powerful NPC. It was a player killing the visible in-world representative of a game's creator, in front of a crowd, during an official gathering.
The chaos did not end there. Starr Long, an Ultima Online developer who appeared in-game as Lord Blackthorn, responded by summoning demons that attacked players nearby. The situation escalated into one of the medium's earliest and most memorable stories about emergent online behavior, developer authority, role-play, player punishment, and the fragile boundaries between a game's planned narrative and what its community actually does.
Over time, killing Lord British became a recurring Ultima tradition and Easter egg. The original Ultima Online event has remained especially notable because it represents a moment when a live virtual world visibly slipped beyond the intended control of its creators.
Newell's case for embracing the memorable
Newell described the Lord British incident as an example game developers tell each other, but he took a more critical view of the response than the usual retelling of an amusing exploit story. In his framing, rolling back the world missed an opportunity.
"When Lord British was killed during his first speech in Ultima Online, they rolled the world back rather than recognizing that it was the coolest thing that had ever happened in Ultima Online," Newell said.
His suggested alternative was not that studios should ignore every flaw, abandon moderation, or allow cheats to overwhelm a game. Rather, he argued that a development team needs to recognize when an unplanned event has genuine dramatic and social value. A singular event can become the start of new fiction: an assassination, a succession crisis, a revenge story, a world-changing disaster, or a memorable chapter players recount for years.
"They should have let that instance turn into whatever an instance turned into after they killed off Lord British," Newell said.
That perspective goes beyond nostalgia for the rougher and stranger early days of internet games. It poses a difficult question for teams operating persistent worlds: when players do something unexpected, is the priority restoring the intended state of play, or can the unexpected outcome become more meaningful than the original plan?
Unexpected play is not automatically destructive
Newell's distinction matters because "exploit," "hack," and "emergent behavior" are often used interchangeably in community conversations. They are not necessarily the same thing. Some abuses clearly damage a game: cheating software that creates an unfair competitive advantage, attacks that compromise accounts or servers, item duplication that wrecks an in-game economy, and targeted harassment all demand intervention.
But games also thrive on players discovering unusual uses for mechanics. Speedrunners turn movement systems, physics, and obscure interactions into new forms of performance. Fighting-game players find advanced techniques that may not have been explicitly planned but add depth to the competitive scene. Sandbox communities transform ordinary building, trading, travel, and social tools into elaborate player-run institutions.
For an MMO, the stakes can be even higher. These games are not only rules systems; they are places where groups form memories. Players frequently remember server-specific rivalries, improvised ceremonies, accidental disasters, political betrayals, and hard-won community projects more vividly than a particular quest or patch note.
The Lord British assassination carries that kind of weight because it was dramatic, public, accidental in its setup, and impossible to separate from the fact that Ultima Online was a new social frontier. It became a story not just about a spell hitting a temporarily vulnerable target, but about what could happen when thousands of people were given a persistent world and room to test it.
Security still matters in a persistent world
Newell also made clear that his comments should not be read as a dismissal of security. After discussing the need to be careful about treating entertaining behavior as hacking, he shifted to the importance of stability and confidence in social systems.
His broader point was that people need faith in the future of a world they inhabit. In practical MMO terms, players need to believe that their characters, possessions, progression, and investments will not vanish arbitrarily. If ownership and property feel provisional, the value players attach to them changes. In a persistent online game, technical failures and weak protections can have consequences that spread throughout the larger "meta world" around the game.
That remains a useful qualification to the Lord British example. Preserving a remarkable moment does not mean leaving the underlying weakness unaddressed. A studio could patch the vulnerability while still allowing the consequences of the event to remain in the game's history. The design challenge is deciding what must be fixed for fairness and trust, and what should be retained because it makes the world feel alive.
Modern live games face this balancing act constantly. Developers must protect accounts, prevent fraud, safeguard competitive integrity, and respond to player reports. At the same time, overly rigid responses can erase moments that a community sees as harmless, clever, funny, or creatively transformative. Newell's old lecture remains compelling because it argues for judgment rather than a blanket rule.
An MMO story with a long legacy
The Lord British incident has accumulated an additional historical connection over the years. Naoki "Yoshi-P" Yoshida, who would later lead the turnaround of Final Fantasy 14 and oversee Final Fantasy 14: A Realm Reborn, was present for the assassination. That link gives the event a notable place in the wider history of online RPGs: one of the medium's most influential modern MMO leaders witnessed one of its earliest famous moments of player-driven chaos.
It is also why the resurfaced Newell clip has resonated so strongly. The discussion is not about whether a 1997 bug should have remained unfixed. It is about the mindset used to interpret player behavior. A live game can be a carefully maintained product, but it can also be a stage where the audience occasionally becomes the author.
For developers, that may mean asking a question before reaching for a rollback, ban, or emergency patch: did players merely break the experience, or did they create an experience that people will talk about long after the usual content is forgotten?
Newell's answer, at least in the case of Lord British, is clear. Some accidents expose weaknesses. Others become history. The best online worlds need the technical discipline to tell the difference.
Community
Discussion
Start the conversation.
No comments have been posted yet.