How Speedrunners Find Shortcuts Other Players Miss

Watch a world record speedrun of almost any game and you will see something strange happen. The runner walks toward a wall, jumps at an odd angle, clips through a texture and reappears three rooms ahead. To a casual viewer it looks like a glitch, or even cheating. To the speedrunning community it is a shortcut, the product of hundreds of hours spent studying a game more closely than its own developers ever did.

Here is how speedrunners find the paths that everyone else walks straight past, and why the search rarely stops once a run is finished.

The difference between a trick and a glitch

Speedrunners separate shortcuts into rough categories, even if the lines blur. A trick usually means a move the designers intended to be hard but fair, such as a precise jump that skips a long corridor. A glitch exploits a flaw in the game's code, like a collision box that does not fully cover a wall or a loading transition that forgets to lock the player's position. Both count as legitimate finds in most communities, and both get hunted for using the same patient methods.

What looks like luck on stream is almost never luck. It is the result of a search process that treats the game less like entertainment and more like a system with edges to be mapped.

Reading the game like a blueprint

Serious route finders stop playing the game the way it was designed to be played almost immediately. Instead of following the path the level design suggests, they ask what the game is actually checking at any given moment. Does a door open because the player walked through a trigger zone, or because a flag somewhere in memory flipped to true? If it is the second, is there another way to flip that flag?

This habit of asking what the game is really tracking, rather than what it appears to be asking of the player, is the single biggest difference between a casual run and a competitive one. It turns level geometry into a set of rules that can be tested, bent and sometimes broken outright.

The slow grind of testing every edge

Finding a new shortcut rarely happens through a flash of insight. Most discoveries come from repetition that would bore anyone outside the hobby. Runners will walk into the same corner of a map hundreds of times, adjusting the angle of approach by a few degrees each attempt, just to see whether the character model slips past a wall that looked solid. They will try jumping a frame earlier, then a frame later, cataloguing the outcome of each tiny change.

This mirrors the way online communities crack puzzles that were built to be solved collectively, something covered in how online game players uncover secrets through teamwork. The tools differ, but the discipline is the same: propose a small change, test it, record the result, and move to the next variation whether or not it worked.

Tools that turn guessing into measurement

Modern speedrunning leans heavily on tools that were never meant for players. Frame-by-frame video review lets a runner see exactly which frame a jump connected, something impossible to judge by eye at normal speed. Memory viewers, used openly by many communities for research rather than live cheating, show which values change when an action succeeds versus when it fails. Input display overlays reveal the precise button sequence behind a trick that looks instantaneous on stream.

None of this guarantees a discovery. It simply makes the search faster and the results easier to share, so one runner's careful measurement becomes the whole community's shared knowledge within days.

Why developers leave these doors open

It is tempting to assume every shortcut is a mistake the developers would patch if they noticed. Sometimes that is true. More often the door was left open because closing it would have cost more time than it was worth, or because the team simply never imagined anyone would approach the level from that angle. Testing a game for the way it is meant to be played is very different from testing it for every conceivable sequence of inputs a determined player might try years later.

The broader question of why certain secrets survive untouched is explored in why game developers hide secrets in the first place, and the same logic applies here even when the shortcut was never deliberately hidden at all.

The community that keeps score

Few shortcuts stay a secret for long. Leaderboards reward the fastest verified time, and verification usually means submitting a full video so other runners can check every step. That scrutiny has an unexpected side effect: it turns the entire community into a distributed research team. A viewer rewatching a submission at quarter speed might spot a frame where the runner's character clips slightly into geometry that was not being used on purpose, and within a week that accident becomes a documented, repeatable strategy.

This pattern of careful, data-driven observation is close to the approach described in how online game analysts read player data to spot trends, just applied to a single run instead of an entire player base.

Is breaking the game still playing it?

Some players find the whole pursuit strange. If the goal is to avoid most of the game's content, skip its story beats and clip through its carefully built rooms, is that still playing it at all?

I think it is a different kind of play rather than a lesser one. A speedrunner's relationship with a game shifts from experiencing its world to understanding its machinery, and that understanding is its own reward. The runs that clip through walls still require precision, memorisation and nerve under pressure. They just measure mastery against the system itself instead of against the story it tells.

Skills that shortcut hunting builds

Breaking a system down into rules rather than accepting its surface behaviour.
Patient, incremental testing with careful notes on every failed attempt.
Reading frame-level detail that casual play never requires.
Separating an intended challenge from an accidental opening.
Sharing findings so the whole community benefits from one person's grind.

Getting started with route research

Pick one short, well-mapped game rather than a sprawling one for your first search.
Watch existing world record runs in slow motion before trying anything yourself.
Pay attention to collision edges, loading zones and camera transitions, where most shortcuts hide.
Change one variable at a time, such as approach angle or timing, and log every result.
Join the game's speedrunning community before claiming a discovery, since it may already be documented.

The habits are patient rather than flashy, which is exactly why the shortcuts stay hidden from anyone just passing through. For players who want to practice the same close reading on a game's secrets rather than its geometry, tips for finding easter eggs in games covers a closely related search with a different target.

Most of what separates a world record from an ordinary playthrough is not talent in the traditional sense. It is the willingness to treat a finished game as an unfinished question, and to keep testing long after everyone else has moved on.