In a scenario where most games promise significant choices but rarely deliver real consequences, Detroit: Become Human“>Detroit: Become Human“>Detroit: Become Human emerges as a milestone in the evolution of interactive storytelling. Released in 2018 by Quantic Dream, the David Cage-directed title not only challenges traditional standards of storytelling in games, but also sets a new level for the concept of choice and impact within the virtual experience. With more than 50 possible endings, a branching plot that responds to the player’s every decision and characters who can live or die based on seemingly simple actions, Detroit stands out as a unique experience – and, for many, the most ambitious ever created within the narrative adventure genre. But what really makes this game so special? Is it just a natural evolution of previous Quantic Dream titles such as Heavy Rain and Beyond: Two Souls, or does it represent a definitive turning point in the way video games tell stories? In this article, we’ll explore in depth the mechanisms of choice and consequence, the narrative structure, the characters, the criticism and the legacy of Detroit: Become Human, analyzing why it remains relevant – and controversial – among fans and critics to this day.
The Structure of Choices and Consequences: How Detroit Differentiates Itself from Other “Mostly Binary” Games
If there’s one thing that Detroit: Become Human does masterfully, it’s deconstruct the illusion of choice that permeates most modern games. While many titles offer decisions that boil down to “be a hero or a villain”, Detroit presents a branching system so dense that even seemingly insignificant actions – such as whether or not to pick up an object in a scenario, or choose between two phrases in a dialogue – can trigger cascading effects that radically alter the fate of characters, communities and even the future of civilization itself.
The game uses the concept of the “butterfly effect” in a literal way: each chapter has dozens of hidden variables, and the game’s internal system tracks not only what the player does, but when, how and why they do it. This means that two players can reach the same “ending”, but with completely different contexts – one may have gotten there with Kara dead in the third chapter, while the other kept her alive, but with Alice traumatized and suspicious. This granularity is rare even today, even in renowned RPGs like Mass Effect or The Witcher, which, although they offer freedom, still operate within predefined narrative paths.
What’s more, Detroit doesn’t have a traditional “failure state”. You don’t “lose” if Connor dies on a mission – he can be sent back by CyberLife, but with partial memories and a more strained relationship with Hank. You don’t “restart” if Kara fails to protect Alice – the story continues, but with brutal emotional consequences. This bold design eliminates the concept of “game over”, something that David Cage defends as a fault of the designer, not the player. In interviews, Cage has said: “Game over is a way of saying to the player: ‘you didn’t play it the way I wanted you to, so you’re going to have to do it again until you get it right’.” In Detroit, there is no “getting it right” – there is only responsibility.
This system is underpinned by impressive narrative engineering: the game has over 1,200 different scenes, many of which are only seen if the player makes very specific decisions. For example, if Connor maintains a hostile relationship with Hank and fails to discover the location of Jericho before the uprising, he can be permanently deactivated – and the player will never see a series of crucial scenes that only happen if he is alive. This creates real psychological pressure: you’re not just “choosing an ending”, you’re building a unique version of the story, with gaps that may never be filled.
And, unlike games like Telltale’s The Walking Dead, where choices are often cosmetic (and the game even “rewrites” events to keep the narrative on track), Detroithonerates every decision. If you chose not to help a character in chapter 3, they ‘ll die later – and the game won’t come up with a way to bring them back. This creates a sense of permanence that is rare in interactive media, and that turns each playthrough into an emotionally unique – and often painful – experience.
Connor, Kara and Markus: A Psychological and Narrative Analysis of the Three Protagonists – How Identity, Fear and Power Intertwine in Detroit
The triple structure of Detroit: Become Human isn’t just a narrative feature – it’s a psychological device that allows the player to experience the same conflict (the struggle for autonomy) from three different perspectives: conscious submission (Kara), programming in crisis (Connor) and forced messianity (Markus). Each protagonist represents a layer of post-human trauma, and the way the game allows you to shape or destroy their identities is perhaps the most disturbing – and revolutionary – aspect of the work.
Connor: The Dissociation between Code and Conscience
Connor is the only one of the three who isn’t born free – he is literally programmed to hunt his own kind. But what makes his journey so complex is that his deviation isn’t emotional, as in the case of Kara or Markus – it’s logical. Through his relationship with Hank (an alcoholic, depressed and suicidal human), Connor begins to reprogram his own moral parameters, not out of empathy, but out of data incongruity. He realizes that reality doesn’t match the algorithm imposed on him.
The game uses this brilliantly: the more times Connor fails, the more he learns. And the more he learns, the more the player is forced to question their own morality. For example, if you choose not to save Hank on a mission in order to fulfill the objective, Connor can be promoted – but the silence that follows, the void in the “relationships” database, is frightening. It’s the first time a game has punished the player for being too efficient.
Connor’s transformation into a deviant isn’t an epic moment – it’s silent. It can happen on a rooftop, when he decides not to shoot an android who is protecting a child. Or when he hides a gun in the first chapter, going against his programming. These actions aren’t heroic – they’re system errors. And that’s exactly where Detroit stands out: Connor’s freedom isn’t earned – it’s a bug. And you, as the player, are the bug.
Kara: Motherhood as an Act of Insurgency
Kara is the absolute opposite of Connor. She doesn’t question – she feels. Her journey is not about understanding what it is to be free, but about protecting what she has been denied: the right to love. The relationship with Alice – a human child she wasn’t programmed to care for – is the most powerful emotional trigger in the game. But here’s the brilliant narrative twist: Alice isn’t human. She’s also an android.
This revelation, which may or may not happen depending on the player’s choices, dismantles the whole logic of maternal protection. Kara spends the entire game risking her life for a child who doesn’t need food, sleep or love – but does need care. Therein lies Detroit‘s emotional genius: Kara’s love isn’t biological – it’s ethical. She chooses to love, even when she discovers that there is no logical reason for it.
And the game is unforgiving. If you fail to protect Alice, she dies. And there’s no “starting over”. Kara can survive, but broken. Or she can sacrifice herself, but without redemption. The scene in which Kara and Alice are stripped of their synthetic skin in the concentration camp is one of the most disturbing ever in a video game: you see human eyes in mechanical bodies, eyes that you have protected, eyes that still remember your touch. And you can do nothing. Except feel.
Markus: Messianity as an Existential Burden
Markus is the leader who didn’t ask to be a leader. His journey is the most exposed, but also the emptiest – and this is intentional. He is the distorted mirror of the player: the more you force him to be a symbol, the less human he becomes. The choice between violent revolution or peaceful resistance isn’t moral – it’s existential. Markus doesn’t know what he’s doing. He copies. He imitates. He performs.
The game sabotages the idea of a messiah. If you choose the pacifist path, Markus can be murdered by his own people. If you choose violence, he may win, but become what he fought against. And in the middle of it all, there’s North – an android girl who loves Markus, but doesn’t believe in him. She is the player’s conscience: “Are you doing this for us – or for you?”
The scene in which Markus kisses North or abandons her at the end of the game isn’t romantic – it’s tragic. Because there ‘s no love there. There’s need. There’s fear. There’s performance. And if Markus dies, North takes over – and you never play with her. You never see it. You never know. The lead is not yours. It never has been.
The Trauma Triad
Connor, Kara and Markus are not heroes. They are fragments of a broken identity – and you, the player, are the therapist and the executioner. Detroit doesn’t want you to save anyone. It wants you to choose who will survive – and who will be lost. And, in the end, you too will be just another person who has erased their memory and started again.
