Contents

Metal Gear Solid V: The Phantom Pain — The Open World That Swallowed the Story

Kojima built the series' best sandbox and shipped it a third missing

Contents

Metal Gear Solid V: The Phantom Pain, released in September 2015, is the best pure stealth sandbox Hideo Kojima ever built and one of the most publicly, visibly unfinished major releases the medium has produced. Both things are true simultaneously, and understanding why requires separating the systems — which are extraordinary — from the production collapse that cut the story off roughly two-thirds through its intended shape, following Kojima’s very public split from Konami during the game’s final year of development. This is a review of a genuinely great toolset wearing the scars of the company that built it falling apart around the release date.

The mission structure as a systems argument

Advertisement

Every infiltration in The Phantom Pain runs on the same underlying logic Snake Eater established a decade earlier — camouflage, patrol reading, resource management — scaled up to an open Afghan and African map and given genuine emergent tools rather than scripted set-pieces. Buddies are the clearest expression of this: D-Dog scouts and marks enemies at a distance, Quiet snipes from cover positions you direct her to, D-Horse provides mobile cover and a getaway option, and each fundamentally changes how you’d approach the exact same outpost. Bring D-Dog to a base and you’re playing a recon-heavy, patient game; bring Quiet and you’re playing an overwatch game where you bait guards into her sightline. The base design underneath stays constant, but the buddy you’ve equipped effectively reskins the entire mission’s texture, which is a more elegant way to generate variety than most open-world games’ answer — simply making the map bigger.

Fulton Recovery — the balloon-extraction system that lets you kidnap unconscious soldiers, vehicles and even livestock and whisk them skyward to Motherbase — turns Diamond Dogs’ base-building into the actual reward loop for good stealth play. Extract a well-armed guard and he becomes a staff member back at Motherbase, improving your R&D, combat or support teams; extract enough specialists and you unlock better weapons, better armour, better intel gathering for the next mission. It’s a closed economic loop that makes every successful infiltration feed directly into your capacity for the next one, in a way Hitman World of Assassination’s more contained, mission-by-mission puzzle-box structure deliberately doesn’t attempt — Hitman resets you to a blank slate each level by design, while Phantom Pain’s whole appeal rests on watching a base you’ve built with your own captured soldiers grow across dozens of hours.

Reflex Mode as an honest concession

Get spotted and the game offers Reflex Mode, a brief slow-motion window to eliminate the spotting guard before the alarm fully triggers. It would be easy to read this as difficulty-softening, and on base difficulty it functions that way, but the more interesting reading is structural: Reflex Mode exists because a fully simulated, systemic stealth sandbox this large will inevitably generate situations where a guard notices you through no real failure of planning — a patrol route recalculates, a vehicle headlight sweeps wider than expected — and punishing that with an instant failure state would make the systems feel unfair rather than demanding. Reflex Mode is the game’s admission that its own simulation is complex enough to occasionally surprise its designers, and it’s a more honest solution than pretending the simulation is perfectly predictable and punishing the player for its edge cases.

The weapon and equipment R&D loop as a second progression track

Advertisement

Layered underneath the buddy system and Fulton economy is a genuine research tree, staffed by extracted specialists in your R&D team, that lets you develop suppressors, tranquilliser variants, non-lethal takedown gear and increasingly esoteric weapons like the cardboard-box-mounted rocket launcher across a real time investment. This matters because it gives the open world an actual reason to reward exploration beyond collectibles: a diamond found in a cave or a rare plant sample gathered on patrol feeds directly into unlocking better gear, which feeds directly into being able to attempt harder infiltrations non-lethally, which is the playstyle the game’s better ending states quietly reward. Compare that to a loot system like Nioh 2’s, which generates gear as a direct drop from combat encounters; Phantom Pain’s version routes the same dopamine loop through base management and patience instead, which fits a stealth game’s slower rhythms far better than random combat drops would.

The empty map as a deliberate design choice

Afghanistan and the Angola-Zaire border region are enormous, sparsely populated stretches of terrain connected by long horseback or helicopter rides, and the game has taken real criticism for the amount of empty space between objectives. That criticism is fair on its own terms, but it undersells what the emptiness is doing: long, uneventful stretches of travel are where the buddy system actually gets to breathe, where D-Dog will occasionally alert to a hidden supply cache or a wandering patrol you’d otherwise have missed, and where the game’s ambient wildlife and weather systems — sandstorms that kill visibility for both you and enemy patrols equally, rainstorms that mute footsteps — establish that the world runs on rules rather than existing purely to host missions. A tighter, more densely populated map would have generated more constant incident, at the cost of the specific, patient rhythm the extraction-based economy is built to reward. Reading the emptiness as a deliberate trade-off rather than a shortfall changes how the map plays, even in the stretches that genuinely test patience.

Motherbase management, and where the loop gets thin

The Motherbase management layer — assigning captured soldiers to R&D, Combat, Support or Intel teams, researching new weapons, defending against occasional enemy raids on your own base — is a genuinely deep economic system bolted onto the stealth sandbox, and it’s also where the game’s demands on your patience are steepest. Menu navigation between deployment screens, staff reassignment and mission select adds real friction to what should be a satisfying loop, and the later game’s difficulty spikes lean on forcing repeat playthroughs of earlier missions at higher difficulty tiers to farm resources, which is where The Phantom Pain’s hundred-plus-hour running time starts to feel like padding rather than generosity. Side Ops in particular — shorter missions reusing the same outpost geometry with modified objectives — are a legitimate way to keep engaging with a great toolset, but the game leans on them so heavily in its back half that the sandbox’s genuine excellence starts working against it, asking for a time commitment the main story can no longer justify.

Demon Points and the game’s quiet moral ledger

The Phantom Pain tracks a hidden metric — Demon Points, accrued through lethal kills and civilian casualties — that gradually alters Snake’s physical model, growing a horn and blackening his skin the further into brutality a player leans, and Motherbase staff will eventually react to a sufficiently demonic commander with visible unease. It’s a quieter, more diegetic version of the karma meters other open-world games bolt on as an explicit UI element, and it works better for staying out of the player’s face: there’s no popup telling you your morality score dropped, just a slow visual transformation that mirrors, and comments on, the “Big Boss” mythology the entire series has spent three decades building around a man who becomes a legendary villain through an accumulation of small, justified-sounding decisions. It’s a rare example of an open-world morality system that trusts environmental storytelling over a meter, and it fits a game otherwise obsessed with showing its systems through consequence rather than through spreadsheets.

The production collapse, honestly

Chapter 2 is where the seams show plainly: missions repeat earlier objectives with cosmetic changes, key story threads involving Skull Face’s defeat and Eli’s (young Liquid Snake’s) arc are compressed into cutscenes rather than played out, and the game ends on a structural whiplash that reads, correctly, as a studio running out of both time and the parent company’s patience. Kojima Productions’ split from Konami during 2015’s final development stretch is now public record, documented well beyond the point of speculation, and Chapter 2’s compressed shape is the visible fault line of that collapse rather than a deliberate artistic choice. It’s a rare case where a AAA game’s production history is legible directly in its final structure, and reviewing the game honestly means naming that rather than pretending the back half was intended to feel this thin.

The verdict

The Phantom Pain’s systems — the buddy variety, the Fulton economy, the honest concession of Reflex Mode — represent the most sophisticated stealth sandbox Kojima’s team ever built, genuinely ahead of where the genre’s open-world attempts have mostly landed since. The story built around those systems is a fragment of what it was designed to be, and the two facts sit uncomfortably next to each other across the entire runtime: a masterclass in systemic design housing an unfinished narrative that the marketing never fully acknowledged at launch. Play it for Motherbase and the buddy system and go in knowing Chapter 2 is a shadow of Chapter 1; that combination of brilliance and visible damage is, in its own way, more honestly discussed than pretended away. Available on every current platform via backward compatibility or native release.

Spoilers below

The Quiet twist — that she’s mute because parasites in her throat require oxygen exchange through skin rather than lungs, meaning she communicates almost entirely through gesture and humming — is one of the more inventive body-horror justifications the series has produced for a character mechanic, though the game’s handling of her design and the manner she’s introduced remains one of the more legitimately criticised choices in the Metal Gear catalogue, and it’s worth separating the mechanical inventiveness of the writing from the discomfort of the presentation.

The final act’s revelation that the player has spent the entire game as Venom Snake, a medically and psychologically conditioned body double believing himself to be Big Boss, retroactively reframes every mission — the title card reading “Venom Snake” rather than “Big Boss” throughout was there from the opening hours, visible to anyone paying attention, and the twist rewards a second playthrough more than almost any other reveal in the series specifically because the game never actually lied to you about it.

Advertisement
Advertisement
Jay
Written by Jay

vo.rs's games critic. Jay covers the medium as a system rather than a spectacle — this month's release, the indie nobody bought, and the Amiga game it's quietly descended from — asking what a mechanic makes you feel and why the loop holds. Learned to wait through a C64 tape load, never stopped playing since, and still finishes the odd 60-hour RPG out of spite. Expect argued verdicts, no score ever, spoilers below the line, and a running list of older games worth your weekend.