gamesbriefs
8:50in productionCh. 1 · The Horn and the Hand/ 8:50 · ceiling 15 min
Action & adventure · Game design

Ico

Fumito Ueda · 2001

Ico makes you responsible for another person — not as a mechanic, but as a moral condition.

Ico is a third-person action-adventure built around protecting and guiding Yorda through an abandoned castle. Its minimalist design removes UI, dialogue, and combat options for Yorda — making her presence a structural necessity, not a narrative flourish. The player jumps, climbs, pushes, pulls, and lifts — always in service of moving her forward. The fixed camera follows both characters, panning slightly to reveal environment. Light is overexposed and desaturated. Story is minimal and told in fictional languages. Mechanics were conceived before story.

Action & adventureGame designMinimalismVideo gamesAbstractionMinimalism across the network →
Chapters & takeaways5
  1. 1:07
    The Horn and the Hand

    Ico is not about escaping a castle — it is about escaping alone.

  2. 2:22
    No Progress Without Her

    Yorda is not a companion — she is a condition of movement.

  3. 3:22
    A Fixed View of Dependence

    The camera and controls enforce shared vulnerability — not shared power.

  4. 4:14
    Design by Subtraction

    Desaturation and silence are not style choices — they are structural omissions.

  5. 5:20
    Mechanics Before Myth

    The puzzle comes first. The story is what sticks to it.

Worth your time?

Yes. Play the whole thing.

4.5/ 5
What works
  • dyadic relationship as core mechanic
  • design by subtraction as worldbuilding
  • light and silence as structural tools
  • mechanics preceding story
What does not
  • combat
  • exposition
  • player autonomy
Play it if
  • players who value intentionality over instruction
  • players who accept silence as narrative texture
  • players who find meaning in constraint
Skip it if
  • players who rely on feedback loops
  • players who need mechanical variety
  • players who require contextual clarity
The written brief2 min read

What the game is

Ico is a third-person action-adventure built around a dyadic relationship between Ico — a horned boy imprisoned in an abandoned castle — and Yorda — the Queen’s daughter, whom he must free and escort to escape. Its design is defined by subtraction: no UI, no combat verbs for Yorda, no spoken language, no visual clutter.

How it actually plays

You control Ico in third-person as he explores a decaying castle. You jump, climb, push, and pull objects. Yorda follows or waits. You must lift her over gaps or reconfigure the environment so she can cross. The camera is fixed but swivels to follow either character; you can pan slightly to survey surroundings. Shadow creatures appear only when Yorda is threatened. You cannot fight them directly — you must draw them away or break their hold on her. Dialogue is absent or in fictional languages. There is no health bar, no map, no objective marker.

What works

The physical bond between Ico and Yorda is enforced by mechanics: lifting, holding hands, waiting, guiding. Every puzzle requires her presence and cooperation. The overexposed, desaturated light flattens detail but amplifies scale and solitude. The sparse landscape and fictional language remove cultural signposts, making the castle feel both ancient and unplaceable. Mechanics precede story — and the story exists only to justify the loop.

What does not

It does not sustain tension through combat or escalation. Yorda’s fragility becomes a constraint that limits player agency rather than deepening consequence. The fixed camera occasionally obscures spatial relationships needed for precise platforming. The minimalism cuts out exposition — but also context, leaving motivation thin beyond the immediate loop.

Who it is for, and who it is not

It is for players who value intentionality over instruction, atmosphere over exposition, and relational play over individual prowess. It is not for players who need clear feedback loops, rapid iteration, or mechanical variety. It assumes attention, not expertise.

Is it worth your time

Yes — if you want to experience a game where every mechanic serves a single emotional contract: protect Yorda, trust her presence, and move forward together. It asks for patience with its pacing, acceptance of its silence, and willingness to read intention from gesture and light. It does not ask for speed, reflexes, or mastery of systems.

Same strand · Action & adventure4 of 51
10:09
Shadow of the ColossusFumito Ueda · 2005Shadow of the Colossus is a third-person action-adventure built around sixteen large-scale boss encounters in a seamless open world. It was directed and lead-designed by Fumito Ueda at Sony Computer Entertainment’s Japan Studio. Its structure is cyclical, minimal, and mechanic-first—designed under PlayStation 2 hardware constraints that forced reduction: from 48 planned colossi to 16, and no day/night cycle.
8:42
Armored Core (video game)FromSoftware · 1997Armored Core (1997) is FromSoftware’s first mecha combat game. Players pilot highly modular Armored Cores across open desert bases and space stations, engaging enemies that appear from all directions. Customisation is functional: swapping leg units changes mobility; weapon choices define combat range. Credits earned from missions fund upgrades, but ammunition and repair costs are deducted even on failure. There is no hand-holding — no map, no waypoints, no enemy indicators. The loop is austere, spatial, and penalised.
9:51
BloodborneFromSoftware · 2015Bloodborne is a third-person action role-playing game developed by FromSoftware and directed by Hidetaka Miyazaki. Released in 2015, it belongs to the Soulsborne subgenre. Players control a customizable Hunter exploring the interconnected Gothic city of Yharnam, engaging in aggressive, strategic combat with trick weapons and firearms. Progression hinges on lamp checkpoints, resource management (Blood Echoes, Insight), and environmental storytelling. Combat emphasises dodging, counterattacking, and close-range aggression. The game’s structure rewards repeated exploration and spatial memory. It offers no narrative hand-holding — story emerges through item descriptions, NPC interactions, and architectural cues.
11:50
Castlevania: Symphony of the NightKonami · 1997Castlevania: Symphony of the Night restructures the action genre around exploration, transformation, and consequence. It replaces linearity with layered access. It replaces exposition with environmental logic. It replaces certainty with discovery — and demands the player pay attention.
Up next in Games

Jet Set Willy

Software Projects · 1984 · 10:38

Jet Set Willy isn’t about jumping — it’s about memorising death traps one room at a time.

Play nextBack to Action & adventure
10:38