Ludonarrative reading

Reading Nier: Automata's mechanics through the resonance lens.

Verdict: structurally affirms. Automata is the rare case where the form of the design — chips, routes, ending — argues the same thing as the content of the writing. Almost every load-bearing mechanical decision is also a thematic claim.

The diagnostic question, applied

Describe the loop without the fiction. Does the description still read as a story about this character?

Yes. The mechanical description of Nier: Automata reads like a précis of its themes:

• The player is software running on a body. (Chip system, including the OS chip.)
• The player's understanding of the world is incomplete on first encounter. (Route A → B reread.)
• The verbs available to the player change with the frame they're in. (Genre-shifting camera.)
• A weapon's history is heavier than its statline; you only earn the history by using it. (Weapon stories at upgrade levels.)
• Endings are not the end. (Routes A, B, C, D each terminate in credits.)
• Hope, in this world, is paid for in shared sacrifice. (Ending E save deletion.)

Each of those reads as both a system and a thematic line. The game does not tell you "perception is software" — the chip menu does.

What resonates, and how

Chip system as "the body is configurable software"

The fictional premise of Nier: Automata is that 2B and 9S are YoRHa androids — combat units with a OS, a body, and a memory that can be backed up before death. The chip system instantiates this: everything the android can do is a chip. Including see. Including survive.

The OS Chip — mandatory, but unequippable, killing the character if removed — is the load-bearing joke. It's also a structural argument: the character is not a body the system runs. The character is the system. Removing software from the system removes the character. The android is software all the way down.

Resonance level: maximum. The fiction's premise is the menu's interaction language. They are the same thing.

Multi-route as "your first reading was incomplete"

The story's central pivot — that the YoRHa androids are not what they think they are, that the war they fight is not what it appears to be, that the antagonist they kill in Route A is grieved in Route B — is enacted by replaying the game. Route B is mechanically the same world as Route A, but the information the player has makes it read differently.

This is the lens's diagnostic in its purest form: what the player does mechanically (replay) affirms what the writing argues (rereading is the only way to understand). The mechanic doesn't symbolise rereading. It is rereading.

Resonance level: maximum. This is the game's signature instance.

Ending E as "shared sacrifice creates the future"

The game's writing makes a sustained argument that connection across difference is what makes meaning in a meaningless universe. Pascal's machine village, A2's grief, 9S's collapse, the failed peace negotiations — all are short stories about beings who cannot connect failing, and one (Ending E) where they can.

The mechanic of Ending E is the player paying their own save data so a stranger can finish the same fight. The verb of the ending is sharing, asynchronously, with someone the player will never meet.

The game does not say "shared sacrifice creates the future." The save-deletion prompt asks if you want to save someone. Yes is the verb.

Resonance level: maximum. Possibly the cleanest single instance of ludonarrative-resonance in commercial games.

Genre-shift as "the frame changes what you can do"

The Bunker is in 2D side-scroller because YoRHa is a cage. The Earth surface is in 3D because Earth is a world. The hacking minigame is in twin-stick shmum because hacking is a different kind of action than swordplay.

Camera framing as rhetoric is unusual but coherent. Resonance level: strong.

What's slightly less coherent

Sidequests

Most main-story mechanics resonate. Sidequests are a mixed bag: some are structurally tied to the themes (Pascal's village, Emil's quest, Resistance Disappearance) and some are pure fetch-quests. The fetch-quests feel particularly orthogonal because the rest of the game is so consistently thematically loaded.

This is partly intentional. Yoko Taro has noted that the bored, indifferent texture of YoRHa life is part of the world — bored androids do bored fetch-quests. But the median sidequest's mechanical loop ("collect 5 of X") is not making a thematic claim; it's just a quest.

Resonance level: mostly orthogonal, with occasional standout exceptions.

Combat moment-to-moment

PlatinumGames combat is a sustained joy that does not particularly resonate with the writing. Cancelling a heavy attack into a perfect-dodge is a mechanical pleasure; it's not making a thematic argument.

Yoko Taro himself has observed (paraphrased from interviews): "PlatinumGames makes the combat fun. I don't think too hard about whether the combat is meaningful." The division of labour shows. Combat is the medium of the verbs; the verbs themselves carry the thematic load.

Resonance level: orthogonal, by design.

Why this game matters for the lens

Nier: Automata is the case study that demonstrates ludonarrative-resonance is achievable across multiple mechanical layers in one game. The chip system, the route structure, and Ending E all argue thematically. Few games argue thematically with one mechanic; Automata does so with three load-bearing ones.

It's also the strongest available counterexample to the claim that "deep" mechanics and "thematic" mechanics are opposed. The chip system is mechanically deep (Storage budget, fusion economy, three loadouts) AND thematically loaded (UI as software). These are the same property.

Where it sits in the table

In the main resonance table, Nier: Automata sits at the densest affirmation end — alongside Hades, Hollow Knight, MMBN, Moonlighter 2, and Xenoblade. The qualifier is that Automata is the only entry where the affirmation is structurally enforced (you cannot complete the game without doing the rereading) rather than emergent from the loop's pacing.