Design tensions

What the developers wrestled with, in their own words.

Routes and budget

"The route system was, well, that was a product of our budget from Square Enix. We couldn't really make all that much content. So we ended up trying to make those route shifts and try to use the same content as much as possible."

— Yoko Taro, Famitsu/GamesRadar interview, 2023

The structural twist that made Automata famous (multi-route reread) was a constraint, not a vision. Yoko Taro says elsewhere he'd done it before in Drakengard 1; the technique is reusing the same world from a second protagonist's POV.

"The reason we did it is that Square Enix told us to 'add more content.'"

— Yoko Taro, same interview

So: a publisher demand, refracted through a technique he'd practised, became the work's defining structure.

The "happy" ending

"I don't think I'll have a happy ending. … This is the first time I've been able to do this kind of happy ending."

— Yoko Taro, Game Informer, 2017

Yoko Taro's prior catalogue (Drakengard 1, 2, 3, the original Nier) ends in apocalypse, dragon-eating-Tokyo, or worse. Ending E was framed by him as an experiment — can I write a hopeful ending?

The hope is structural: the player gives up their save so a stranger can finish. Hope is not in the story; it's in the verb.

The endings as layered reveals

"I structure my endings from A to E … each one reveals a new layer of something. So if you only saw it to the end of here, you'll maybe get one answer; if you move on, you'll see a deeper answer and something different."

— Yoko Taro, paraphrased from Siliconera interview

The rereading is the point. Each ending is a re-rendering of the same world with new information. Players who stop at A "got" the game's first answer; players who finish E "got" the question itself.

Combat as PlatinumGames

The combat was outsourced to PlatinumGames (Bayonetta, Vanquish, Metal Gear Rising) specifically because the original Nier (2010) had been criticised for sluggish combat. Yoko Taro on the partnership:

"I'm not really a developer. I'm just somebody who comes up with crazy ideas, and PlatinumGames are the ones who make it work."

— Yoko Taro (paraphrased, recurring in multiple interviews)

PlatinumGames lead designer Takahisa Taura was the gameplay director. The division is roughly: Yoko Taro owns the writing, structure, and "crazy ideas"; Platinum owns the moment-to-moment combat engineering. The chip-system idea came from Yoko Taro's side; the combat-feel came from Platinum's.

What the team chose not to do

Yoko Taro has mentioned (across interviews) that PlatinumGames pushed back on certain ideas:

• He wanted to allow players to delete each other's saves during multiplayer. This was rejected.
• He wanted Ending E's save deletion to be truly irreversible at the OS level. Square Enix's QA flagged this as an unacceptable risk — what if a player triggers it accidentally? — and the deletion is now reversible via cloud backup, though the in-game prompt does not mention this.
• He has stated in interviews that earlier drafts had more endings tied to deeper mechanical sacrifices (e.g. you lose access to a character permanently). Most were trimmed.

The constraint pattern: every Yoko Taro mechanical idea is a few clicks more committed than what ships. The team's job is to translate.

The chip system as accessibility lever

The chip system doubles as the game's accessibility configuration. Auto-Battle, Auto-Move, Auto-Aim, and Auto-Use Item chips are pre-equipped on Easy difficulty. A player who finds the combat overwhelming on Normal can manually equip these chips.

"We wanted to make the game accessible without making it boring. We added all those Auto chips so that someone who doesn't like action games can still play. But they're chips, so they have a cost. You can't have all of them. The player still has to choose."

— Yoko Taro / Takahisa Taura (paraphrased from interview material on the chip system)

The accessibility settings are part of the same loadout budget as the combat power-ups. Easy mode is a build, not a separate game.

This is a quietly elegant decision. The same budget enforces the same constraint everywhere: you can lean on auto-play, but you'll feel the storage cost.

See also

• Multi-route structure — the load-bearing trick
• Ending E + save sacrifice — the load-bearing payoff
• Sources — full interview citations