# When Players Become Co-Authors: The Speedrunning Philosophy Problem ## The Core Tension Imagine someone buys a novel, then discovers that by creasing the pages in a specific way, they can jump from chapter 3 directly to chapter 8, bypassing entire plot threads. Is this reading? Is it cheating? Is it *brilliant*? This isn't hypothetical in speedrunning—it happens constantly, and it's precisely why the community perpetually argues about legitimacy. ## What Actually Happens: A Concrete Example In *The Legend of Zelda: Ocarina of Time*, runners discovered they could use a precise combination of sword slashes and positioning to walk through walls that should be impassable. By exploiting this, elite players skip entire dungeons and essential story sequences. **The intended experience**: ~40+ hours, following a narrative arc. **The glitch experience**: ~18 minutes, jumping between disconnected moments. This isn't a small optimization—it's a complete reimagining of what the game *is*. ## Why This Creates Actual Philosophical Arguments ### The "Game as Intended" Camp These players argue: "The designer created specific challenges in a specific order for a reason. When you glitch past them, you're not playing *their* game anymore—you're playing something else." Their concern isn't snobbish. There's real substance here: the designer's intent matters morally and aesthetically. A speedrun that respects the game's architecture proves something different than one that exploits its broken scaffolding. ### The "The Game Is What It Is" Camp These players counter: "The game exists as code. Every possible action—including glitches—emerges from the designer's work. If the game *allows* wall-clipping, then wall-clipping is part of the game. The designer chose to create a machine with these properties." There's substance here too: you can't actually separate "intended" from "unintended" once code is released. Players didn't add the glitch—they discovered it in what already existed. ### The "Collaborative Artwork" Position This is where it gets genuinely interesting philosophically. Some argue that glitch exploitation represents something new: **the player as creative partner**. When a speedrunner discovers that frame-perfect

Imagine you're watching a world-class athlete compete, but instead of running on the track, they're leaping over fences, cutting through spectators' tents, and vaulting onto the roof of the stadium to bypass entire laps. That's a bit like what a speedrunner does when they engage in **sequence breaking**, and it throws the entire concept of "playing a game" into a fascinating, ongoing philosophical debate. Let's break it down for a curious general audience: ### What is Speedrunning? At its core, speedrunning is the art of beating a video game as fast as humanly possible. It's a competitive sport, a demonstration of mastery, and a deep exploration of a game's mechanics. Speedrunners dedicate thousands of hours to learning intricate button presses, movement optimizations, and enemy patterns, all to shave milliseconds off their time. ### Enter Sequence Breaking: The Art of Subversion Sequence breaking is a specific, highly advanced technique within speedrunning. It's not just about moving fast; it's about **deliberately exploiting unintended glitches, bugs, or oversight in a game's code to skip entire sections, challenges, or narrative progression.** Think of a game designer creating a lock-and-key puzzle: you need to find Key A to open Door A, which leads to Key B, to open Door B. Sequence breaking is finding a way to: * **Clip through Door A** without Key A. * **Warp directly to Door B** from the start of the game. * **Force the game to believe you have Key B** when you don't. Famous examples abound: In *The Legend of Zelda: Ocarina of Time*, runners use complex maneuvers like "Reverse Bottle Adventure" to trick the game into granting them the power to warp to the final boss within minutes. In *Metroid* games, "bomb jumping" or "shinesparking" allows players to reach areas far before the designers intended, often bypassing entire upgrades or boss fights. **Why do speedrunners do this?** Because it's often the fastest way. It demonstrates an incredible understanding of the game's underlying systems, an ability to think "outside the box" (or outside the intended walls), and it unlocks entirely new, often bizarre, pathways through familiar worlds. It feels like hacking the Matrix, but with a controller. ### The Philosophical Collision: "Are We Still Playing the Game?" This is where the fun begins. Sequence breaking ignites two major philosophical arguments within the speedrunning community and beyond: #### Argument 1: "Are They Still 'Playing' the Game the Designer Intended?" **The "No, Not Really" Camp (The Purists):** This perspective argues that a game is an artwork with a specific structure, narrative, and set of challenges meticulously crafted by its designers. When a speedrunner bypasses these elements using glitches, they are not engaging with the game as it was *meant* to be experienced. They're effectively breaking the "rules" of the game's artistic integrity. * **Analogy:** Is listening to a song by fast-forwarding through all the verses and only hearing the chorus truly "listening to the song"? Is reading a novel by skipping chapters still "reading the novel" in its intended form? For purists, glitches are like using a cheat code – they undermine the designer's vision and the player's legitimate struggle. The "game" is the journey, not just the destination. **The "Yes, Absolutely" Camp (The Code Explorers):** This viewpoint contends that "the game" isn't just the designer's intention; it's the executable code itself. If the code *allows* a player to clip through a wall or trigger an unintended warp, then that interaction is inherently part of the game's reality. The "rules" are defined by what the system actually permits, not by what a human *thought* it would permit. * **Analogy:** If a chess piece could, under specific, rare circumstances, move diagonally through another piece due to a hidden rule flaw, then exploiting that flaw would still be "playing chess" – just playing it at a deeper, more analytical level than the average player. Speedrunners aren't breaking the game; they're simply discovering its full, often hidden, range of possibilities. They are pushing the boundaries of the system itself, not just the intended narrative path. #### Argument 2: "Does the Game Become a Collaborative Artwork Between Designer and Exploiter?" This is perhaps the more intriguing and modern perspective, suggesting a synthesis rather than a conflict. **The "Yes, It's a Co-Creation" Camp:** This argument proposes that the game, especially in the context of speedrunning, transcends its initial form. 1. **The Designer as the Initial Artist:** The designer creates the raw materials: the game engine, the physics, the world, the characters, the initial narrative, and the programming logic. They build the canvas, the paints, and the brushes. 2. **The Exploiter (Speedrunner) as the Performance Artist/Reinterpreter:** The speedrunner takes those materials and tools, and instead of using them in the "prescribed" way, they find new, unexpected ways to interact with them. They uncover the hidden logic, the emergent properties, and the vulnerabilities of the system. In doing so, they create a new performance, a new interpretation of the original work. * **Analogy:** Think of a classical music piece. The composer writes the score (the designer's intent). A musician can play it exactly as written, or they can interpret it, improvising within the structure, adding flourishes, or emphasizing different dynamics – creating a new, unique performance. Or consider abstract art: the artist provides the medium, and the viewer brings their own interpretation, completing the artwork. * **In this view, the speedrun itself, particularly one laden with mind-bending glitches, becomes a performance art piece.** It's a dialogue between the game's underlying code (the designer's raw creation) and the player's ingenuity, persistence, and ability to push boundaries. The game isn't just a static product; it's a dynamic medium that can be reshaped and reinterpreted, revealing depths its creators might never have foreseen. The glitches aren't "broken"; they're merely *unintended features* that contribute to a richer, more complex interaction. ### Why This Debate Endures These philosophical arguments are central to speedrunning because they touch on fundamental questions about creativity, intent, rules, and the nature of digital art. There's no single "right" answer, and that's precisely what makes the discussion so vibrant. Practically, these debates often lead to different speedrunning **categories**: * **Any%:** Beat the game as fast as possible, using *any* means necessary (glitches, sequence breaks, etc.). This is where the wildest exploits thrive. * **Glitchless/No Major Glitches:** Beat the game as fast as possible, but without using specific, game-breaking exploits. This category often aligns more with the "designer's intent" perspective. * **100%:** Complete every objective in the game as fast as possible. These categories allow different philosophies to coexist, ensuring that both those who appreciate the purity of the designer's vision and those who revel in the subversive brilliance of the exploiter can find their niche. The speedrunning community continues to thrive precisely because it's constantly questioning, pushing, and redefining what it means to "play a game."