Metal Gear Solid 2 Speedrunners Find a Way to Skip Olga's Boss Fight Entirely

Metal Gear Solid 2: Sons of Liberty has produced one of its most consequential speedrunning discoveries in years. A newly demonstrated exploit allows players to skip the fight against Olga Gurlukovich altogether, removing the only proper boss battle from Solid Snake's Tanker chapter and potentially reshaping optimized runs of the game.

The technique was shown in a video by Metal Gear Solid 2 runner apel, with the discovery also highlighted by Time Extension. It is not a simple case of clipping past a door or exploiting a cutscene to dodge an arena. Instead, the route relies on an unusual interaction between an unconscious guard, the explosives' laser sensors, the game's internal event flags, and a carefully timed checkpoint save.

For a game that has been studied, routed, replayed, and speedrun for around a quarter of a century, the result is especially notable. The Olga encounter has long appeared to be an unavoidable part of the Tanker sequence. Now, speedrunners have a route that leaves Snake free to proceed without ever fighting her.

Why the Olga fight matters in Metal Gear Solid 2

Metal Gear Solid 2 is divided into two major sections: the Tanker chapter and the Plant chapter. The Tanker serves as an opening mission set aboard a ship, placing players in control of Solid Snake as he infiltrates the vessel in pursuit of evidence connected to Metal Gear development.

For useful background on this topic, read Control Resonant Urban Survival walkthrough: Mines, Olivia, Granny, and the Bunker.

That opening remains important beyond its role as a prologue. It is also the only substantial stretch of the game in which players directly control Snake. Once the story moves on to the Big Shell, Raiden becomes the player character for the overwhelming majority of the adventure.

Olga Gurlukovich is Snake's main boss opponent during that brief playable portion of his campaign. After Snake wins the fight, he takes Olga's USP handgun. Ordinarily, that weapon has a practical role in the next part of the Tanker: Snake needs a lethal firearm to shoot the sensors associated with explosives on the ship.

In typical play, the sequence is direct enough. Fight Olga, obtain the pistol, use it to deal with the bomb sensors, and continue through the story. Metal Gear Solid 2 frequently encourages non-lethal play, so the required use of a lethal weapon in this area is a distinctive constraint. The new skip changes that logic by making the bomb sequence resolve without Snake ever needing to acquire Olga's gun.

A guard becomes the key to setting off the explosives

The setup begins with a guard rather than with Olga. In apel's demonstration, Snake drags an unconscious guard into position near the laser sensors. Once that guard wakes up, the lasers are activated and the explosives detonate.

That alone would not normally provide a useful shortcut. Triggering the blast creates a game-over state, and selecting Continue would generally restore the game in a way that allows the explosive event to function again. The key is understanding the state value that determines whether the explosives are available to be activated.

As apel explains in the video, the detonation causes the game to set a flag governing whether the explosives can be triggered again. Under an ordinary failure-and-continue sequence, the game restores the stored value of that flag. In practical terms, that means the game behaves as though the explosive setup remains active when the player resumes.

The breakthrough comes from saving at a checkpoint at exactly the right moment. By rolling toward a checkpoint as the guard causes the explosives to go off, Snake can reach the save trigger while the game is updating that event state. The checkpoint records the post-explosion value instead of the earlier value that would usually be restored after the game over.

When the player continues from there, the bombs have effectively already been dealt with from the game's perspective. Snake can pass through the relevant section and keep moving forward. Since the pistol was only necessary for the explosive sensors in this portion of Tanker, the usual reason to defeat Olga disappears.

The first complete boss skip for the game

The importance of the exploit is not just that it saves a little time or provides an entertaining alternate route. It represents the first known method of completely avoiding a boss fight in Metal Gear Solid 2.

Speedruns often improve through small optimizations: more efficient movement, faster menu handling, better guard manipulation, refined damage strategies, or safer execution of previously known glitches. A boss skip is different because it removes an entire required encounter, along with the movement and item progression surrounding it. It can force runners to reconsider the route from the beginning rather than simply inserting a new trick into an established sequence.

Olga is especially significant in this context because she is the sole boss Snake faces in the Tanker. Skipping her does more than shorten one fight; it alters the structure of Snake's whole playable chapter. A run can now move from the Tanker's infiltration and explosive setup toward the transition to Raiden without completing the sequence that long functioned as Snake's mandatory climax.

It is also a fittingly Metal Gear-style discovery. The series is famous for layered systems, unusual player interactions, and edge cases that can produce surprising outcomes. Here, a sleeping guard is repositioned to trigger security lasers, an explosion changes a hidden status flag, and a roll into a checkpoint preserves that status at a very particular instant. The solution sounds improbable, but it emerges from the game's interacting systems rather than from an external modification.

What the trick could mean for future runs

Any major new skip must be tested before it becomes standard in competitive categories. Runners will want to establish how consistent the setup is, how much time it saves in practice, whether it behaves identically across versions, and whether category rules permit its use. A discovery can be fast in theory yet difficult enough to introduce major reset risk, especially if it requires precise guard placement and tight timing at a checkpoint.

There are also version questions that matter for a game with a long release history. Metal Gear Solid 2 has appeared in multiple forms across PlayStation, Xbox, PC, and Nintendo platforms through original releases, expanded editions, collections, and modern re-releases. Differences in loading behavior, performance, regional releases, or revisions can sometimes affect speedrun techniques. Until runners thoroughly investigate those variables, it is sensible not to assume the method will work exactly the same way everywhere.

Still, the core discovery gives the community a powerful new avenue to explore. If the technique proves viable in the primary categories, record routes may need substantial revision. The time saved is not solely the length of the Olga battle itself. Players also avoid the actions tied to obtaining and using the USP, while the new path may create different movement opportunities through the remainder of the Tanker chapter.

Even categories that do not immediately adopt the skip could benefit from the research around it. Examining why the checkpoint stores one game state rather than another can expose other possible interactions elsewhere in Metal Gear Solid 2. Speedrunning communities frequently turn one discovery into a broader understanding of a game's scripting, save behavior, collision, AI, and event handling.

A reminder that old games can still hold secrets

Metal Gear Solid 2 has been a fixture of discussion for decades, whether the topic is its stealth design, its famously ambitious narrative, the shift from Snake to Raiden, or its unusually deep mechanics. The newly found Olga bypass is another reminder that even heavily analyzed games can retain meaningful secrets.

It also underlines the collaborative and investigative side of speedrunning. The community's biggest advances do not always come from raw execution. They can arise from experimentation with seemingly minor details: what happens if an enemy wakes up in the wrong place, whether a scripted object can be activated by someone other than the player, or exactly when a checkpoint commits an internal value to a save state.

For casual players, the discovery offers a fascinating glimpse behind Metal Gear Solid 2's carefully directed opening. For runners, it may be the beginning of a new era for the game's routes and records. Snake may have been expected to duel Olga before leaving the Tanker, but with a guard doing the dirty work and a checkpoint timed just right, that expectation no longer has to hold.