New 31-Step GTA: San Andreas Skip Explained
More than two decades after Grand Theft Auto: San Andreas first arrived on PC, its speedrunning community has found a way to bend the game further than ever before. A newly documented 31-step route chains glitches, mission exploits, and script manipulation into a single sequence that can end an any% run of the original PC port in less than an hour.
This article breaks down what that discovery means, how it works at a high level, and why it’s such a big deal for both speedrunners and fans of Rockstar’s open-world classic.
Why a New Skip in a 21-Year-Old Game Matters
At first glance, shaving minutes off a run of a 2000s open-world game might sound niche. In practice, these breakthroughs are a blend of technical experimentation, community collaboration, and deep understanding of game systems.
There are a few reasons this skip stands out:
- Age of the game: The original Windows version of San Andreas released in 2005. Finding such a radical new route after so long shows that even well-studied games can hide surprising complexity.
- Scope of the skip: Instead of cutting a mission or two, the 31-step setup rearranges the game’s internal story progression to jump forward to the finale.
- Impact on leaderboards: Any% runs on the original PC port have been pushed down to well under one hour, with time still likely to fall as runners refine execution and routing.
- Pure in-game exploit: The method works on the original PC build without external tools, memory editors, or mods, which is critical for legitimacy in most speedrun categories.
Speedrunning San Andreas: From Long Campaigns to Hour-Long Clears
Traditionally, completing San Andreas is a long haul. Even for skilled players, a casual story playthrough can take dozens of hours when you factor in cutscenes, travel time across the three main cities, and mission retries.
Speedrunners pursue faster times in several categories, each with its own rules and expectations. The 31-step skip primarily influences the original PC any% route, which allows heavy use of glitches.
Key San Andreas Speedrun Categories
| Category | Core Rule | Typical Length* | Glitches Allowed? |
|---|---|---|---|
| Any% | Reach the ending as fast as possible | ~45–90 minutes (varies by platform/route) | Yes, most glitches allowed |
| No Major Glitches (NMG) | Beat main story without large sequence breaks | Several hours | Minor tech allowed, no big skips |
| 100% | Complete all missions and collectibles | Double-digit hours | Glitches allowed, must still meet objectives |
*Approximate, based on publicly available leaderboards and runs hosted on Speedrun.com.
Any% categories are often the most volatile. As new tricks appear, entire routes can be reworked, and established records quickly fall. The 31-step skip is the latest example of this pattern.
Foundations: Mission Scripts and Why They’re Abusable
To understand why the new route is so powerful, you need a rough idea of how San Andreas controls progression. Like many games of its era, it relies on a mission scripting system that tracks:
- Which missions are available or completed.
- Where the player should spawn after a mission or cutscene.
- What flags, NPCs, and vehicles should exist for each scene.
The scripts read data from memory and set variables that affect what the game does next. If you can manipulate those variables in unexpected ways—using tricks such as opening menus at precise times, forcing unusual mission failures, or desyncing cutscenes from gameplay—then you can sometimes make the script “jump” to a different part of the story than intended.
This kind of manipulation is not unique to San Andreas. Researchers and speedrunners have documented similar behavior in other games when scripts or memory addresses are exposed to unusual player actions or timing. In general, exploiting script behavior hinges on the same principle: creating states that developers never anticipated and never protected against.
The 31-Step Route: A High-Level Walkthrough
The new strategy is often described as a 31-step process because it depends on a specific, tightly ordered chain of actions. While the precise sequence is complex, the flow can be broken into four broad phases:
1. Early-Game Setup and Money Manipulation
The run begins in a fairly standard way, completing key opening missions quickly. The early goal is to reach a state where the player can:
- Access a save point reliably.
- Interact with shops or services that change the player’s cash.
- Position CJ and various mission markers in convenient locations.
One of the more surprising ingredients is the deliberate use of negative money values. In many older games, currency is stored as a signed integer. That means it can represent both positive and negative numbers. If the game doesn’t enforce a floor at zero, underflow (or careful subtraction) can push the money value below zero, which in turn affects conditions or calculations elsewhere in the scripts.
By deliberately manipulating CJ’s cash into specific ranges, runners can influence how certain scripts interpret his status or trigger branches intended only for specific mission states.
2. Persistent Menus and Cutscene Skips
The next phase focuses on destabilizing the normal relationship between gameplay, menus, and cutscenes. Runners work to create a situation where:
- Menus remain partially active while the game continues to update in the background.
- Cutscenes are started or canceled at moments when the engine is in transition.
- CJ’s position or mission status becomes misaligned with what the story expects.
By layering inputs and menu interactions around teleport events and fade transitions, the route effectively “stretches” the script. Parts of the game think a mission is at one stage, while other systems are convinced something else is happening.
Getting these transitions right is one of the most execution-heavy parts of the route. A single missed input, or a mistimed pause or skip, can cause the game to revert to normal behavior, softlock, or advance in an unintended way that ruins the later steps.
3. Script Misalignment and Story Jumps
Once the setup has created the desired instability, the route aims to force the story script to jump to a much later point in the campaign. This is often achieved by:
- Entering or exiting certain mission markers with the menu state still glitched.
- Triggering failure or success conditions out of their intended order.
- Leveraging the earlier money manipulation so that checks on CJ’s status behave unexpectedly.
Internally, the game maintains a series of flags and pointers that tell it which mission should run next and where CJ should be placed. When the script logic reads corrupted or mismatched values, it can end up calling the mission or scene associated with a completely different part of the game—often the final act in this route.
This kind of story warp is reminiscent of sequence breaks seen in other speedruns, where the game is convinced you’ve completed objectives that were actually skipped. In San Andreas, the 31-step route uses a chain of many small misalignments instead of a single massive glitch, which is why documentation emphasizes each individual step.
4. Sprint to the Final Mission and Credits
If everything has been executed correctly, the game abruptly jumps forward, loading the finale and associated assets. From this point, the run looks more familiar: the player still has to complete the last mission under speedrun pressure, but they’ve dodged the majority of the story in between.
Because the route relies on the original PC version’s behavior, details like framerate, input timing, and load performance all play a role in consistency. Runners often practice this endgame portion heavily: failing the final mission after 40–50 minutes of fragile setup is costly.
Why This Works Only on the Original PC Port
One important detail is that this exact 31-step method is currently tailored to the original PC port of San Andreas. Other platforms—even those emulating the game—may not behave identically. Reasons include:
- Different executable builds: Patches and ports may fix or alter the way scripts and variables are handled.
- Framerate differences: Timing-sensitive tricks can break if the engine updates at different rates across platforms, something also observed in other games where physics and scripts are tied to framerate.
- Memory layout: Even minor changes in how data is stored in memory can affect which variables are corrupted or manipulated by a glitch.
Because the method uses no external tools and relies solely on interactions allowed by the game’s own systems, it fits comfortably within the rules of most any% categories for the original PC version. Other categories, such as No Major Glitches, may forbid this approach as it clearly bypasses a large portion of intended gameplay.
Implications for the Speedrunning Community
The discovery of such a dramatic skip has ripple effects beyond a single leaderboard time.
Route Overhauls and Record Chasing
Whenever a major new strategy appears, established records effectively gain an asterisk: runners who set older times were operating under different conditions. This does not diminish their skill, but it usually motivates top players to return, relearn, and attempt new records with the updated route.
In practical terms, this means:
- New runners have a fresh, exciting path to practice.
- Veteran players face the challenge of mastering a fragile and highly technical setup.
- Leaderboards often see a flurry of submissions as the community pushes the strategy to its limits.
Community Collaboration and Documentation
Complex routes like this rarely emerge fully formed. Instead, they grow out of smaller discoveries: a strange mission behavior, a weird teleport, a money bug. Over time, players connect these pieces into a cohesive strategy.
Once a technique looks promising, runners typically:
- Produce detailed guides, often step-by-step, annotated with timing notes.
- Share video breakdowns explaining not just what to do, but why it works.
- Test consistency and search for backup strategies to save runs after small mistakes.
Public leaderboards, such as those hosted at Speedrun.com, serve as hubs where routes, categories, and rulesets are discussed and refined. This open structure helps keep the scene healthy and reduces the odds that powerful strategies remain gatekept.
Watching and Learning: Tips for New Viewers
For people who haven’t followed San Andreas speedrunning closely, the 31-step skip can look confusing. CJ may jump across the map, missions appear out of order, and menus pop up in seemingly random places. A few tips can make runs easier to follow:
- Look for commentary: Many top runners publish post-commentary videos where they walk through the run and explain each major trick or timing cue.
- Focus on the big beats: You don’t need to understand every frame-perfect input. Pay attention to key transitions—moments where the route jumps from one mission chain to another.
- Compare to a casual playthrough: If you’ve played the story yourself, spotting which sections are being skipped can give you a better sense of how powerful the route is.
Even without deep technical knowledge, watching a decades-old game get turned inside-out by new discoveries can be fascinating. It also highlights the creativity and persistence of speedrunning communities.
Frequently Asked Questions
Does the 31-step skip use cheats or mods?
No. The strategy is executed entirely within the unmodified original PC version of Grand Theft Auto: San Andreas, using regular in-game mechanics, menus, and mission triggers. External cheat tools or trainers are not part of the route and would invalidate runs on standard leaderboards.
Can this method be used on console versions?
As currently documented, the route is specific to the original PC port. Console builds and later releases may have different timing behavior, patched scripts, or altered memory layout, which can cause the method to fail or behave unpredictably. Separate research would be needed to adapt similar ideas to other platforms.
Why is it called a 31-step skip?
The community often describes the strategy as having 31 steps because the full setup is broken down into that many key segments in guides. Each step is required to reach the precise state of money values, mission flags, and menu behavior needed for the final story jump.
Is the route consistent enough for marathons?
Right now, the route is considered fragile. Missing a single input or timing window can collapse the setup and force a reset. Over time, runners often discover safer variants and backup strategies that make marathon use more realistic, but initially, such complex skips are usually reserved for record attempts rather than live events.
Will this discovery end interest in longer categories?
Unlikely. While any% categories often become faster and more glitch-heavy over time, many players and viewers still enjoy longer categories such as No Major Glitches or 100%, which preserve more of the intended story and gameplay. New skips usually diversify the scene rather than replace existing interests.
References
- Grand Theft Auto: San Andreas — Rockstar Games. 2004-10-26. https://www.rockstargames.com/games/sanandreas
- Grand Theft Auto: San Andreas – Speedrun Leaderboards — Speedrun.com. Accessed 2026. https://www.speedrun.com/gtasa
- Preventing the Exploitation of Software Vulnerabilities — National Institute of Standards and Technology (NIST). 2020-11-16. https://csrc.nist.gov/projects/software-assurance
- Video Games in Education: Why They Should Be Used and How They Are Being Used — Becker, K. The Journal of Educational Multimedia and Hypermedia. 2007. https://www.learntechlib.org/p/21609/
- Speedrunning: Networked Videogame Play and Emotional Labor — Scully-Blaker, R. et al., Game Studies Journal. 2017-12-01. http://gamestudies.org/1701/articles/scullyblaker

