Contents

Tomb Raider (2013): The Reboot That Rebuilt Lara From the Feet Up

Crystal Dynamics threw out the acrobat and built a survivalist, and the traversal system had to be rebuilt to match her

Contents

The original Tomb Raider, built by the six-person Derby team at Core Design in 1996, ran on a grid. Lara’s jumps, grabs and ledge-catches were all keyed to a fixed-size block, which is why the game’s traversal, however revolutionary at the time, always had a faint chess-piece quality to it — you weren’t climbing a tomb so much as solving a lattice. Crystal Dynamics’ 2013 reboot, developed after the studio had already spent two console generations trying to modernise Core’s formula through the Legend and Underworld years, made a decision more radical than a graphics update: it threw the grid out entirely and rebuilt Lara’s movement around scrambling, improvised grabs at ledges that don’t line up to any lattice, and momentum that carries through a jump rather than snapping to the next valid tile. The traversal had to change before anything else about the character could, because a woman who fights for every handhold reads as a different person than one who executes a pre-authored acrobatic routine.

Released 5 March 2013 for PC, PlayStation 3 and Xbox 360, the game strands a 21-year-old Lara — on her first expedition, aboard the research vessel Endurance — on the fictional island of Yamatai after a storm wrecks the ship, and spends its opening hours making her survival visibly effortful: she’s cold, she’s injured, she screams when she falls badly, and her early climbing is shown as genuinely uncertain rather than the confident freerunning the series had used since Legend. It’s a soft reboot dressed as an origin story, and the origin-story framing does real mechanical work — a character who hasn’t mastered tomb-raiding yet justifies a traversal system built on desperation rather than mastery.

The pickaxe as the whole design thesis

Advertisement

The single object that defines the reboot’s traversal is the climbing axe Lara recovers early and never puts down. Where Core-era Lara’s hands were an abstraction — she simply grabbed whatever the grid told her she could grab — 2013 Lara’s axe is a visible, physical tool she swings into rock faces, ice walls and wooden beams, and the animation sells effort every single time: a slight overhand wind-up, a grunt on impact, a visible strain when she’s dangling from a single stuck blade. This does two things simultaneously. Mechanically, it lets the level designers place climbable surfaces anywhere a pickaxe could plausibly bite, which is a far less restrictive design constraint than Core’s grid ever was — you get organic-looking rock faces instead of obviously gridded pillars. Thematically, it makes every climb cost something, because the tool itself looks improvised and precarious rather than like standard-issue adventuring equipment.

The bow, introduced almost as early as the axe, does comparable double duty for combat. It’s Lara’s first weapon, sourced from a corpse on the island rather than issued to her, and its slow draw-and-release rhythm — compared to the instant-hit pistols she picks up later — forces patience in a way that suits a character who’s meant to be over her head. The weapon progression across the campaign (bow, pistol, shotgun, assault rifle, all salvaged rather than found in ammo crates with a UI flourish) tracks Lara’s arc from prey to predator explicitly: by the endgame she’s dual-wielding pistols and mowing through Solarii cultists with the confidence Core’s Lara had from the character’s first outing. The 2013 game earns that confidence by denying it for the first three hours, which the original Tomb Raider, built as an already-competent adventurer from minute one, never had reason to do.

Salvage and camps as pacing tools, not just systems

The scavenging loop — picking through crates and corpses for salvage to upgrade weapons at campfire checkpoints — gets dismissed sometimes as a rote open-world-adjacent system bolted onto a linear adventure game, and there’s truth in that criticism, but it’s doing real pacing work that’s easy to miss. Camps are deliberately placed at the seams between the game’s tension beats: right after a set-piece (an escape from a burning building, a QTE-heavy chase down a mountainside) and right before the next area’s exploration opens up. Sitting at a camp to upgrade gear is a soft breather the game hands you exactly when the adrenaline needs somewhere to go, and the salvage economy gives that breather a purpose beyond waiting for your heart rate to drop. It’s a smaller, quieter version of the rhythm Resident Evil 4’s 2023 remake uses its merchant encounters for — a mechanical excuse to punctuate action with calm, structured around resource management rather than a cutscene.

Failure animations as characterisation

Advertisement

A detail that rewards close attention: Crystal Dynamics built a large library of context-specific failure animations rather than a single generic “you died” ragdoll. Miss a jump over a ravine and Lara flails and catches a ledge at the last second before the game decides whether that catch holds; misjudge a QTE during a rapids sequence and she’s shown being genuinely battered by rocks rather than simply resetting to a checkpoint. Most action games treat failure as pure friction — a fail state exists to be reversed as quickly as possible, with minimal animation budget spent on it because the player isn’t meant to dwell there. Tomb Raider 2013 spends real craft on the failure states specifically because they reinforce the survival thesis: a Lara who nearly dies convincingly at every ravine and rockslide sells the “in over her head” characterisation far more efficiently than any amount of dialogue could, and it costs the animation team meaningfully more work than a generic death screen would have. It’s a good example of a AAA production spending its budget on the theme rather than only on the marketing setpieces.

The case against — the island’s story doesn’t earn its mysticism

Tomb Raider 2013’s survival framing is its strongest asset for roughly two-thirds of the campaign, and then the plot pivots hard into supernatural territory — a sun-goddess cult, a storm-controlling deity called Himiko, an army of possessed Solarii soldiers — that the grounded, physically-effortful opening never quite prepares you for. The tonal problem isn’t that games can’t mix survivalism with the supernatural; it’s that the writing spends its first act building specific, careful stakes around cold, hunger and improvised weapons, then abandons that vocabulary for generic ancient-evil plotting once the mystical elements arrive, without translating the earlier grounded tension into the new register. Lara’s arc from victim to survivor lands; the island’s mythology mostly doesn’t, because it was clearly a lower design priority than the traversal and combat systems that make the reboot work, and it shows.

The other honest limit: the QTE-heavy set-pieces — several escape sequences reduce Lara’s newly physical, effortful climbing to timed button prompts rather than player-directed movement — undercut the exact thing the traversal redesign was trying to prove. A game arguing that Lara’s survival is earned through skilful, player-controlled scrambling shouldn’t need to fall back on quick-time reflexes at its most dramatic moments; it’s the clearest sign of a AAA production hedging its bets on a genuinely bold traversal redesign rather than trusting it fully.

The kill count problem, and why it’s a real design tension

Roughly ninety minutes into the campaign, Lara kills a man for the first time — a Solarii soldier who attacks her — and the game stages it as traumatic, a lingering close-up on her shaking hands and a genuinely upset reaction. By the final act she’s dispatched several hundred enemies with the same dual-pistol fluency the series has always offered, and the tonal gap between “first kill as trauma” and “hundredth kill as spectacle” is the reboot’s most-discussed writing problem, because the gap is baked into the difference between a linear story beat (one meaningful death, scripted and voiced) and an open combat system that needs the player killing dozens of enemies per hour to function as a game at all. Crystal Dynamics never solved this tension; they managed it, by simply not returning to the theme after that first kill, which is an honest admission that the mechanical demands of an action game and the character-study ambitions of the opening hours were pulling in different directions and the studio picked the game over the character study once it mattered.

Spoilers below

The endgame reveal that Himiko’s storm-controlling power is real rather than superstition — that the island genuinely has been trapping and killing shipwrecked sailors for centuries through supernatural means, not just a violent cult — is where the story fully commits to the mysticism the earlier acts hedge on. Lara’s confrontation with the possessed Mathias, the cult leader who has been feeding shipwreck survivors to Himiko’s ritual in exchange for a promised resurrection of his dead wife, resolves the human antagonist plot cleanly, but the Himiko fight itself — a magical boss encounter fought with fire and a bow rather than the grounded scrambling combat that defined the previous eight hours — is the moment the game’s mechanical vocabulary and its narrative ambition diverge most sharply. It’s a spectacular set-piece and a mechanically honest one (the traversal and combat systems the game built are still what you’re using), but it resolves a survival story with a fantasy climax, and the seam between the two never fully closes.

Sam’s survival at the end — Lara’s best friend, held captive throughout the back half as Himiko’s intended vessel — gives the “getting my crew off this island alive” throughline its payoff, and it’s the strongest piece of writing in the finale precisely because it’s the one thread the game kept grounded in relationships rather than mythology throughout.

The verdict, and what to play next

The 2013 reboot’s real accomplishment is proving that a character’s mechanics and her characterisation are the same design problem — Crystal Dynamics didn’t make Lara Croft more relatable by writing better dialogue, they did it by making her climbing look like it cost something, which forced every other system in the game (weapons, salvage, pacing) to justify itself against that same cost. It remains readily playable across PC and console storefronts, runs well on modern hardware given its 2013 vintage, and rewards a look specifically at how the traversal redesign compares to Core Design’s original grid-based Lara — the clearest case study on the desk of a reboot changing a genre’s foundational movement system rather than just its graphics budget.

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.