Ico: The Game About Holding a Hand

Every player who has ever groaned at an escort mission has the same complaint: the person you’re escorting is a worse version of you. They can’t fight, they can’t keep up, they walk into things. The genre’s answer for thirty years has been to make the escortee more competent — give them a gun, give them better pathfinding, let them keep pace — until they’re basically a second player character and the escort is over.

Ico went the other way. Yorda is slow. She cannot climb. She cannot jump a gap you can clear without thinking. She stands where you left her. Fumito Ueda’s team took every property that makes an escort character annoying and made those properties the entire game, and the result, twenty-plus years later, is still the only escort design anyone talks about with affection.

The button

Everything routes through R1. Hold it near Yorda and Ico takes her hand. Hold it away from her and he calls out to her. That’s the whole verb set for the relationship, and the amount of design pressure sitting on one shoulder button is remarkable.

Consider what holding hands actually does mechanically. It slows you down, because she can’t run at your speed. It anchors your camera and your attention to a second body. It converts every gap in the environment into a two-body problem — you can cross it, so now the question is how she crosses it. And it makes the physical tug of the connection legible: on the DualShock, calling her buzzes the pad. The hand is the interface.

The genius move is that the game never explains any of this. There’s no tutorial box telling you Yorda cannot climb ledges. You learn it by walking to a ledge, climbing it, and finding yourself alone with a girl standing at the bottom looking up. That’s a lesson taught by consequence in about four seconds, and it’s the school of design the tutorial and the art of not explaining exists to defend. The castle is the manual.

Subtraction as a working method

Ueda has described his approach as design by subtraction, and Ico is the purest demonstration of it in the medium. Look at what’s absent. No HUD. No health bar. No music through most of the runtime — the soundtrack is wind, water, stone and footsteps, with cues held back so hard that when strings finally arrive they land like a door opening. No dialogue you can understand: Yorda speaks an invented language rendered in glyphs, and Ico’s speech is subtitled while hers stays foreign. No inventory. No experience points. No map.

Subtraction is easy to praise and hard to do, because every removed system is a system that was doing a job, and the job doesn’t go away. Take the health bar. Ico replaces it with the shadow creatures’ behaviour: they don’t attack you for damage so much as they go for Yorda and try to drag her into a black pool. Your failure state is her failure state. That single substitution kills the need for a health economy, kills the need for a fail-screen explanation, and makes the combat — which is genuinely clumsy, a wooden stick swung at smoke — carry emotional weight it has no right to carry. You’re batting shadows away from someone. The clumsiness is fine because you’d be clumsy too.

That’s the trick underneath all of Ueda’s subtraction. He doesn’t remove a system and leave a hole. He removes a system and lets the relationship absorb its function. Health becomes fear for someone else. Objectives become a door only she can open. Motivation becomes her hand in yours.

Why nobody has copied it properly

Two decades of games have tried to bottle this and mostly produced something else. The instructive comparison is Resident Evil 4, which arrived four years later with Ashley — an escortee widely disliked at the time and, in the 2023 remake, substantially rebuilt to be less of a drag. Capcom’s fix was to make her more capable and less present. That’s the industry’s standard reflex, and it works: the remake is a better action game for it.

But look at what the reflex costs. Ashley’s incompetence in the original is a tax on your play. Yorda’s incompetence in Ico is the content of your play. The difference isn’t tuning. It’s that Resident Evil 4 is a combat game with an escort bolted to it, so the escort competes with the good part, while Ico has no good part underneath — remove Yorda and there’s nothing left. A system only earns your patience when it’s the only system in the room.

The other common attempt is the companion who is secretly a tool: Elizabeth throwing you ammunition, the dog that finds the collectible, the partner who opens the doors marked partner-shaped. Those characters are frictionless by design, which means they never cost you anything, which means you never invest. Yorda costs you constantly. Every ledge is a negotiation. The affection people report for her is the residue of that expenditure, and you cannot fake it by writing better dialogue for a companion who never slows you down.

Where the design fights itself

I want to be honest about the parts that grind, because Ico gets written about in a register of reverence that flattens it.

The camera is a period problem and it’s a real one. Fixed, sweeping, architecture-first shots are how the castle achieves its scale, and they’re also how you end up swinging a stick at a shadow you can’t see while Yorda is being dragged off screen-left. The combat sections in the back third get longer and denser, and the game’s own systems are least equipped for exactly the thing it asks for most by then.

Yorda’s pathfinding is likewise of its era. She’ll snag on geometry. She’ll take the long way. Most of the time this is indistinguishable from the design intent — she’s meant to be hesitant — which is a very convenient place for a technical limitation to hide, and I’d be lying if I said I could always tell them apart.

And the puzzle vocabulary is thin. Push the block, pull the chain, light the bomb, ride the lift. If you strip the emotional layer, the box-and-switch content in Ico would be unremarkable in any 2001 action-adventure. The layer is the game. Take it off and you’re looking at a competent, slightly sparse puzzle-platformer.

The real ancestor

People reach for cinema when they write about Ico — the European cover art Ueda painted himself, with its debt to Giorgio de Chirico’s long shadows and empty arcades, invites that. The actual lineage is a game.

Another World, Éric Chahi, 1991. I played it on an Amiga when it was new and it rewired what I thought the machine was for: no HUD, no dialogue, no explanation, a wordless alien world, an animation-first presentation, and — this is the part people forget — a companion. Buddy, the alien who follows you, gets you through doors you can’t open and dies for you. Everything Ico is famous for is in Chahi’s cinematic game with no words, a decade earlier, at a fraction of the fidelity.

What Ueda added was duration. Another World is a taut couple of hours and the companion arrives late. Ico takes the same austerity and makes you live inside it for seven or eight hours with the companion attached from the first act, and duration converts a device into an attachment. You don’t feel much for a mechanic in twenty minutes. You feel a great deal for one you’ve been holding onto all evening.

The forward line is obvious, and it runs through the same studio: Shadow of the Colossus is subtraction applied to a bestiary instead of a companion. Sixteen enemies, no others. Same method, different noun.

Where to play it

The PS2 original is the artefact, and the regional situation is a genuine footnote: the later PAL and Japanese releases carry content the earliest North American discs don’t, including a two-player mode and an extra sequence. The 2011 high-definition version bundled with Shadow of the Colossus is the practical choice, and it’s the version most people have actually played this century.

Either way, play it in a dark room in as few sittings as you can manage. This is a game whose central effect is accumulated, and a stop-start schedule will strip it out.

Spoilers below

Yorda’s mother is the Queen, and Yorda is being kept alive as a vessel — the horned boys sealed in the coffins at the start were previous sacrifices, and Ico is meant to be another. The reveal reframes the escort completely: you have not been protecting a helpless girl through a hostile castle. You’ve been walking her back towards the thing that made her.

The ending does the one thing the whole design has been building towards, which is take the button away. Yorda is turned to stone. You go on alone, and the castle you’ve been solving as a two-body problem becomes a one-body problem again, and it is awful — the pacing suddenly loose, the platforming suddenly trivial, R1 doing nothing. That’s not a lull in the game. It’s the game handing you the bill.

Then the queen fights you, the castle comes down, and Ico wakes on a beach with Yorda’s shadow-form beside him, which is either an epilogue or a wish. Ueda leaves it exactly ambiguous enough that a decade of forum argument couldn’t settle it, and refusing to settle it is correct. The alternative is a cutscene explaining a feeling you already had.

The reason it lands is arithmetic, not mysticism. Seven hours of holding R1 taught your thumb a habit. The last twenty minutes take the habit away and let you notice the shape of the absence. There isn’t a line of dialogue in the medium that does that job, which is presumably why Ueda didn’t write one.