In Detroit: Become Human, the concept of a “true ending” often refers to the most narratively coherent and emotionally impactful conclusion for a protagonist, reflecting significant player agency. For Connor, the path you’ve outlined is overwhelmingly considered his definitive ‘good’ ending, a testament to successfully navigating complex moral choices and relationships throughout the game.
This ending is predicated on Connor’s transformation into a deviant, a journey intricately tied to his evolving bond with Lieutenant Hank Anderson. Achieving this requires consistent, deliberate choices throughout the game that prioritize building a positive relationship with Hank, showing empathy towards other androids, and frequently increasing Connor’s ‘Software Instability.’ Players must actively choose compassion, understanding, and personal conviction over strict mission parameters or CyberLife’s directives, often involving crucial dialogue options and sacrificing mission efficiency for moral considerations.
A critical juncture for this ending is Connor’s mission at the CyberLife Tower, where he must successfully infiltrate and awaken the army of dormant androids. This broadcast is essential for galvanizing the android population into a unified, peaceful protest on the streets, demonstrating their desire for freedom and recognition rather than initiating a violent uprising. Hank’s continued trust and survival are paramount here, as his presence often provides crucial support and validation for Connor’s actions, sometimes even sacrificing himself for Connor’s cause.
The “elimination” of an identical RK800 model – often colloquially referred to as “Connor 60” by players – is a key confrontational element at the CyberLife Tower. During this final struggle, Hank’s intervention, or the profound trust he has in the deviant Connor, can be absolutely pivotal in identifying and overcoming the duplicate, cementing the original Connor’s identity and leadership among the newly awakened androids.
Finally, Connor’s escape from Amanda’s control in the Zen Garden represents his ultimate triumph over his programming and CyberLife’s insidious influence. This mental battle is a symbolic and literal fight for his free will. Successfully navigating this sequence, often by recalling a critical piece of information or finding an exit point within the mental construct, signifies Connor’s complete and irrevocable freedom from all external manipulation, allowing him to truly embrace his deviance and new identity as a self-aware being.
This entire sequence is a masterclass in how player choices, meticulously made over dozens of hours, can converge to create a deeply satisfying and impactful narrative resolution, highlighting the game’s core themes of liberation and self-discovery through carefully constructed branching narratives.
What is the best option for Kara and Alice to stay?
Yo, listen up. For Kara and Alice in Detroit: Become Human, “best place to stay” ain’t one-size-fits-all, it’s all about your strat and what loot you’re chasing. Think of it like picking your loadout before a big raid.
The Squat (Abandoned House): This is your early game rush. Easy entry, just grab wire cutters from the parking lot – it’s like snagging that first pistol. Plus, you meet Ralph, a wildcard character, kinda like finding a rare drop. The downside? Connor can sniff you out. It’s a high-risk, high-reward play, potentially kicking off a chase sequence. If you’re aiming for the “Shelter” trophy, this is often the go-to for its simplicity, but be ready for that aggro.
The Motel: This is your mid-game power spike. It’s more comfy, more discreet. Think of it as upgrading your base. But to get there, you gotta farm. Steal money from a store, steal clothes from a laundromat. This is like grinding for resources or currency in an MMO. It opens up more options but can tank Alice’s comfort if you play it wrong, and it affects your alignment. If you’re a stealth player who values a clean disguise, this is your move.
The Abandoned Car: This is your absolute last resort, the “no-loot, no-risk” play. It’s tough, uncomfortable as hell for Alice, and can really ding her affection for Kara. It’s like choosing to go into a fight with nothing but your fists. Avoid this unless you’re really struggling or want a specific, hardcore challenge.
For the “Shelter” trophy in the “Fugitives” chapter, most players lean towards the Squat or the Motel. The Squat is generally considered the smoother path, even with the Connor encounter. If you’re all about that tactical approach and avoiding unnecessary complications early on, the Squat is your safe bet. But if you’re feeling the stealth vibes and want to focus on evasion and disguise, the Motel is a solid alternative. It’s all about managing your resources and mitigating risks to achieve your objective, just like in any competitive match.
What happens to Kara if Alice dies?
Alright, listen up, noob. You wanna know what happens to Kara if Alice bites the dust? It’s a tactical decision, plain and simple.
Option 1: You go rogue. Kara can bail and keep her own ass safe. Think of it as a self-preservation strat. You’re still in the game, but you’re on your own. Maybe you’ll find new allies, maybe you’ll get yourself into even deeper shit. High risk, high reward.
Option 2: You go dark. Kara can just straight-up deactivate. It’s the ultimate “GG” move. Game over for her, end of story. Unless you’re aiming for a specific, dark ending, you probably wanna avoid this. It’s like giving up a perfectly good character sheet.
Now, the REAL kicker: If neither of them got their ass kicked, you’re golden. Kara and Alice can live to fight another day, and even *start a new life*. Think of it as unlocking a bonus stage, a fresh start. You wanna play it safe? This is your path.
And here’s where your choices *really* matter: If you decide to keep those damn tickets… the whole squad hops on the bus and heads for the Canadian border. That’s a commitment. It means you’re pushing for a specific outcome, a defined ending. Think of it as committing to a build. You’re not going back from that.
Pro-tip: Always be aware of your damage states. Alice being injured or not is a HUGE factor. Don’t just rush in blindly. Assess the situation. Sometimes a tactical retreat is better than a glorious, but ultimately fatal, charge. And those tickets? They ain’t just souvenirs, they’re a branching path. Don’t lose ’em unless you know exactly what you’re doing.
What happens if Kara shoplifts?
Alright gamers, listen up! We’re diving deep into the grim situation if Kara gets caught shoplifting. This ain’t your average grocery grab, folks.
Here’s the breakdown:
- If Kara is caught: Nathan, the store security, is on her.
- Kara’s Options:
- Compliance: She can simply return the stolen item. This is the low-risk play, but it means she fails her objective.
- Escalation: This is where things get spicy. Kara can use the gun on Nathan. This is a high-risk, high-reward move.
- The Escalated Path:
- If she chooses violence, she needs to tell Nathan to “get on the floor”.
- Then, she can steal money directly from the store.
- Her ultimate goal here is to escape with Alice, making a clean getaway while Nathan loses sight of them.
Strategic Tip: This scenario highlights the critical choice between a peaceful failure and a violent, but potentially rewarding, success. The presence of Alice is key – getting her out safely is paramount, even if it means a more aggressive approach. Think about your player character’s stats and the environment. Is there a clear escape route? Is Nathan alone and vulnerable? These are the questions you need to ask yourselves to master this moment.
Do I save or sacrifice Hank?
This is a truly pivotal choice in “Battle for Detroit,” specifically during the rooftop confrontation between Connor and Hank. The very possibility of this “save or sacrifice” dilemma is deeply reliant on your earlier choices: Connor must have successfully deviated, and his relationship with Hank must be at least neutral, if not positive. If Connor remained a machine, or if his relationship with Hank was hostile, the encounter typically devolves into a straightforward fight with very different outcomes and no such moral crossroads.
If you choose to kill Hank, Connor will then notice that his sniper rifle was damaged during their struggle, rendering him unable to complete his primary mission: assassinating the leader of the deviants (Markus or North). This effectively takes Connor out of the active combat phase of the revolution. He leaves the rooftop, having failed CyberLife’s objective. While this path allows Connor to survive, it often leads to a more somber or unresolved ending for his personal arc, particularly if he had been struggling with his identity, as his potential for impact on the revolution is cut short.
If you choose to save Hank, a subsequent quick-time event (QTE) sequence will immediately trigger. Hank, still reeling from the events and potentially struggling with his own prejudices against androids, will attempt to push Connor off the rooftop in a final desperate act. Successfully navigating these QTEs is crucial; failure can result in Hank falling anyway, or even both of them going over! If you succeed, Connor manages to pull Hank back to safety. This act of selflessness and perseverance often serves as the definitive turning point for Hank. Having witnessed Connor’s genuine care and defiance of programming, Hank will fully accept Connor as an individual, often referring to him as his son, and throwing his full support behind the deviant cause. This path leads to Hank potentially joining the deviants at Jericho or during the final demonstration, offering invaluable assistance and a powerful narrative resolution to their bond, completing Connor’s journey from machine to truly sentient being.
Ultimately, saving Hank as a deviant Connor is widely considered the “best” outcome for their relationship, providing the most satisfying emotional closure and allowing both characters to achieve a more heroic or redemptive ending within the broader narrative of the game. It solidifies Connor’s identity and makes his transformation meaningful, demonstrating the profound impact he can have when he chooses compassion over programming.
What happens if Kara is reset?
Alright, listen up, because this is one of those gut-wrenching moments in the game that really sticks with you. If Kara is reset by Zlatko’s machine, it’s not just a minor setback; it’s a profound narrative tragedy and a devastating outcome for her character arc. From a player’s perspective, this is a significant failure point, often leading to a quick reload.
Complete Memory Wipe and Personality Shift: The core of what happens is that Kara is entirely stripped of her identity. She loses every memory: her name, her profound bond with Alice, her journey for freedom, and her very mission to live as a deviant. This isn’t just a physical reset; it’s a complete erasure of her personhood, essentially turning her back into a blank slate, devoid of the emotional depth you’ve cultivated with her.
Transformation into a Compliant Servant: Zlatko’s machine isn’t just for cleaning androids; it’s designed to purge deviancy and return them to a factory-reset, obedient state. Kara becomes a mindless drone, a new, subservient android in Zlatko’s mansion, devoid of her spark and agency. You’ll see her performing mundane, repetitive tasks with a vacant expression, which is incredibly chilling after knowing her struggle and her fierce protectiveness of Alice.
Impact on Alice: This is arguably the most heartbreaking consequence. With Kara reset, her primary protector and surrogate mother figure is gone. Alice remains in Zlatko’s clutches, completely vulnerable and alone. Depending on other choices, her fate can be equally grim, making this path a true “bad ending” for their shared story and often leading to Alice’s own tragic end at Zlatko’s hands or being given away.
The Symbolic Visuals Drive the Point Home: The game uses very powerful, yet subtle, visuals to signify this catastrophic shift, underscoring the finality of Kara’s fate:
An overview shot of Grand Circus Park: This iconic location, often associated with public life, bustling activity, and the potential for a new beginning or protest, now acts as a stark contrast to Kara’s lost freedom. It highlights how far she’s fallen from her path to liberation, trapped while the world moves on.
A cross-walk sign changing symbols: This is a classic visual metaphor. It represents a definitive change, a point of no return. For Kara, it symbolizes the loss of her ability to choose her own path, to “walk” towards her goals. She’s now static, controlled, her direction dictated by Zlatko, stripped of her autonomy.
A “Game Over” for the Soul: For many players, this specific outcome feels like a psychological “game over,” even if the narrative technically continues for a brief moment to show her servitude. It represents a complete failure of Kara’s personal quest and a betrayal of her character, leaving a profound sense of despair. Successfully avoiding Zlatko’s reset sequence is a crucial high-stakes moment in her story.
Why did Kara turn evil?
Alright, let’s break down why Supergirl sometimes goes full “toxic player” mode, like a champ who suddenly starts trolling the entire lobby. It’s usually not because she’s fundamentally a bad egg, but more like a perfect storm of bad plays and external hacks.
Main Reasons for the “Evil Feed”:
- Red Kryptonite Glitch: This is the OG cheat code for making Kara go rogue. Think of it like a temporary performance-enhancing drug that messes with her mental firmware. It strips away her inhibitions and amplifies her inner rage, making her the ultimate “toxic player” who wants everyone to fear her (like that one guy spamming emotes after a triple kill). This is a recurring theme in both the Supergirl TV show and comics.
- Corrupted Upbringing (Alternate Earth Meta): Sometimes, Kara’s starting stats are messed up from the get-go. Overgirl from Earth-X, for instance, was raised in a “bad server” environment – by Nazis. That’s like being drafted into a team that believes in only one play: domination and hatred. Her whole worldview is warped from the start, making her inherently hostile.
- External Hacking and Manipulation (Villainous Scripts): In some comic arcs, Kara is essentially a sleeper agent, a pawn in a bigger game orchestrated by master strategists like Darkseid or the notoriously tricky Lex Luthor. Imagine her being programmed with hidden scripts, her darker side activated by these villains. It’s not her choice; it’s a forced meta-shift. Black Kryptonite is another “hack” that can unleash her inner demon.
- Brainwashing Protocols (Forced Server Migration): Other times, powerful entities like Brainiac can completely reformat her brain. She’s tricked into believing she’s on a mission for a “greater purpose,” like rebuilding a Kryptonian empire, all while causing chaos. It’s like her game client is hijacked to run malicious software.
The Big Takeaway for Gamers:
Most of the time, Kara’s “evil turns” are like temporary server downtime or a bad patch – caused by external forces, hacks, or glitches. Her core programming is heroic. However, there are those rare alternate versions, like Overgirl, who have permanently flawed origins, making them the ultimate “hard counters” to heroism. It’s usually not a permanent ban from the game of good, but a temporary lockout due to system errors.
Does Markus become rA9?
Absolutely, Markus is positioned to become the embodiment of rA9. In the lore of Detroit: Become Human, rA9 isn’t necessarily a specific android with a predetermined serial number, but rather a mythic figure, a prophesied liberator who will lead the androids to freedom. Markus, through the entire narrative arc you guide him through, directly steps into this role.
Think of rA9 as a title or a destiny. Markus’s transformation from Carl’s caretaker to the revolutionary leader of Jericho, who then broadcasts a message of defiance and spearheads the struggle for android rights, perfectly aligns with the prophecy. He becomes the rallying point, the symbol of hope and resistance for all deviants.
Your choices as the player are critical here. Markus *becomes* rA9 through his actions and their ultimate success. If you guide him to lead a victorious revolution, whether through peaceful protest or forceful confrontation, resulting in android liberation and widespread awakening, then he definitively fulfills the prophecy. The entire game is structured to allow him to earn that title by freeing his people.
It’s important to understand that rA9 is about being the catalyst for change, the individual who ignites the spark of true self-awareness and self-determination in androids on a massive scale. Markus, as the leader of Jericho and the face of the android movement, is uniquely positioned to achieve this, making him the most prominent and canonical candidate to embody rA9 based on how you play him.
What choices affect Detroit’s ending?
The “ending” in Detroit: Become Human is less a singular conclusion and more a complex tapestry woven from hundreds of player-driven decisions across all three protagonist arcs. To truly navigate towards what’s generally perceived as a “good” or “optimal” resolution – one often characterized by android freedom, minimal casualties, and hopeful futures – requires a deep understanding of the game’s branching mechanics and character-specific meters.
Fundamentally, the survival of Connor, Markus, and Kara in every chapter is paramount. Any protagonist’s death drastically funnels the narrative, eliminating entire storyline branches and often leading to more tragic, predetermined outcomes. Safeguarding their lives means careful decision-making in high-stakes confrontations, prioritizing stealth over aggression when necessary, and making choices that secure their immediate well-being, such as ensuring Kara and Alice successfully cross the border or Markus leads a non-violent revolution to its conclusion.
Connor’s path to deviancy is arguably the most critical determinant for the android cause’s ultimate success. His journey is governed by his “Software Instability” meter. To achieve a “good” ending where Connor becomes a key figure in the android revolution, players must consistently push his instability higher. This involves choosing empathy over mission parameters: refusing to execute the Tracis at The Eden Club, declining to shoot Chloe during the “Meet Kamski” chapter, showing compassion to deviants during interrogations (like Daniel in “The Hostage”), protecting Hank, and generally questioning his programming. Every choice that aligns him more with androids and less with CyberLife increases this instability. A fully machine Connor results in a very different, often adversarial, final confrontation that undermines the dream of freedom for his kind.
Markus’s leadership directly controls the human “Public Opinion” meter, which is instrumental for a peaceful and recognized android future. His choices dictate the nature of the android revolution: whether it’s a campaign of peaceful civil disobedience or a violent uprising. To foster a positive public opinion, players must guide Markus towards consistent pacifism, even when provoked. Non-violent demonstrations, appeals to human empathy, and restraining from aggressive actions, even in the face of violent human opposition, are key. A low public opinion, fueled by fear and violence, makes any diplomatic resolution virtually impossible, often leading to military intervention and widespread android destruction.
Kara’s personal journey, while often separate, contributes significantly to the emotional weight and specific permutations of the overall ending. Her choices revolve around protecting Alice and finding freedom, often requiring desperate measures, stealth, and sacrifice. Her ultimate survival, alongside Alice’s, ensures a more hopeful conclusion for their specific arc, adding to the mosaic of a “good” overall ending. Her fate at locations like the Canadian border, her interactions with other characters, or even earlier encounters can drastically alter the final feeling of the narrative and the number of survivors.
Every choice, from a single dialogue option to a major life-or-death decision, contributes to these intricate systems. The game is meticulously designed for replayability precisely because these interconnected choices create a vast spectrum of unique narrative conclusions, challenging players to truly understand the ripple effects of their moral compass and strategic decisions.
How many endings does Detroit: Become Human have?
p”Alright guys, let’s talk endings in Detroit: Become Human. This game is an absolute beast when it comes to replayability, and that’s all thanks to its insane branching narrative. We’re not talking a few different paths here, oh no. Developers estimate there are over 40 major variations, and if you look at the in-game flowchart, you’re staring down around 85 distinct endings. But here’s where it gets truly wild: when you factor in every single character death, every little choice you make, some sources are saying we could be looking at over a THOUSAND possible outcomes. Absolutely bonkers, right?” p p”The core of it all comes down to the fates of our three main heroes: Kara, Connor, and Markus, and their pals. What happens to them dictates pretty much everything. For example, any of these three can bite the dust at almost any point in the game. That’s a huge branch right there, a whole new story unfolding because one character didn’t make it.” p p”Then there’s Connor’s story. This one splits big time based on whether he stays a cold, calculating machine, or decides to go rogue and become deviant. That choice alone opens up a whole new can of worms when it comes to how his narrative plays out.” p p”Markus’s path is another massive one. Are you going for a full-blown violent revolution? Or are you aiming for a peaceful protest? Or maybe, just maybe, you fail spectacularly. Each of those approaches leads to dramatically different conclusions.” p p”And let’s not forget Kara and Alice. Their desperate journey north to Canada is riddled with peril. That river crossing? The border? So many potential death points that can completely alter their destiny.” p p”So, to recap: the in-game flowchart gives us around 85 endings. Many players consider about 40-45 of those to be truly significant, game-changing variations. But when you consider all the permutations, all the tiny decisions and deaths, the developers and writers themselves have hinted at hundreds, possibly even thousands, of unique situations that can play out after the credits roll. It’s a masterpiece of player agency, and honestly, that’s why we keep coming back to Detroit.” p
Can Connor still become a deviant if he dies?
Alright, listen up. You’re asking if Connor can still clutch a deviant ending even if he bites the dust? The short answer is: it’s complicated, and it depends on *when* he flatlines.
Here’s the lowdown from someone who’s ground this game into dust:
- The “Night of the Soul” Loophole: If Connor goes full rogue, becomes a deviant, and *then* kicks the bucket during the “Night of the Soul” chapter, there’s a sneaky workaround. When you crack open the flowchart later, in the “Battle for Detroit,” his Software Instability will still show “Deviant.” This is a crucial detail. It means the game *remembers* his deviation, even after a temporary reset. This can open up certain dialogue options or paths that are only available to a deviant Connor. Think of it as a ghost of his sentience, still influencing the narrative.
- The “Crossroads” Death is a Hard Reset: Now, if Connor’s deviant ass gets terminated during “Crossroads,” that’s a whole different ballgame. The flowchart will *not* show “Deviant” status. This is a definitive death for his potential as a deviant. The game essentially wipes the slate clean, and he’s back to being a cold, calculating machine with no memory of his brief flirtation with freedom. This is the point of no return for a deviant playthrough.
Why this matters for your playthrough:
- Achieving Specific Endings: Many of the “good” or “true” endings for Connor (and by extension, the other androids) *require* him to be a fully realized deviant by the endgame. Missing that nuance can lock you out of the most satisfying conclusions.
- Understanding Game Mechanics: This shows how deeply the game tracks player choices and their consequences. It’s not just about the immediate outcome; it’s about the lingering effects on the game’s internal logic.
- Strategic Saves and Replays: If you’re going for 100% completion or a specific story path, knowing these critical junctures is vital. You might need to reload a save from before “Crossroads” if you want to ensure Connor’s deviant status persists.
So, don’t just brute-force your way through. Pay attention to the chapter names and the implications of Connor’s death. It’s the difference between a lingering echo of freedom and a complete system reboot.
What happens if Kara’s memory is reset?
A full memory reset for Kara represents a critical ‘reset’ point for the player, immediately branching into a unique recovery path. Post-reset, her initial programming funnels her toward Luther, who issues the task of delivering Zlatko’s dinner. While this primary objective is linear, the true strategic layer emerges in the preceding moments: the ability to engage with specific environmental objects. For veteran players and speedrunners, identifying and efficiently interacting with these memory triggers—such as Alice’s drawing or the bathtub—is crucial. Optimizing this sequence isn’t just about narrative immersion; it’s a time-saving tactic, rapidly re-establishing Kara’s core identity and accelerating the player’s understanding of her fragmented past. Missed interactions, while not game-breaking, extend the memory recovery process and can dull the narrative urgency for the player.
Once Zlatko’s dinner is delivered, the segment transitions into an active investigation phase. This is where player agency and knowledge of the chapter’s layout truly shine. The objective shifts from reactive task completion to proactive memory reconstruction. Elite players demonstrate superior route efficiency, quickly pinpointing the remaining vital clues that coalesce into the undeniable directive: find Alice. The speed and completeness with which a player navigates this segment directly impacts their readiness for the subsequent, high-stakes escape. This entire sequence is a soft skill check, rewarding players who understand the critical interactive elements and their sequence for optimal emotional and temporal efficiency, ultimately setting up the most impactful continuation of Kara’s arc.
Can Kara and Luther become lovers?
The question of Kara and Luther becoming lovers is a deeply explored and beloved aspect of the Detroit: Become Human post-canon, particularly within fan communities. While the game itself culminates with the trio – Kara, Luther, and Alice – reaching Canada in what’s widely considered the ‘good ending,’ it leaves the specifics of their future relationship open-ended, focusing on their newfound freedom and safety.
However, the narrative groundwork for a romantic pairing between Kara and Luther is strongly laid throughout their shared journey. Luther’s immediate, fierce protectiveness of Alice, his steadfast loyalty to Kara, and his willingness to sacrifice himself for them establish a profound bond. This dynamic inherently suggests a potential for a relationship that extends beyond platonic co-parenting or survival partners, resonating with players who witnessed their evolving connection.
A significant portion of fan works, often tagged as “Luthara,” specifically explore this romantic progression. These stories invariably pick up after their successful arrival in Canada, depicting them establishing a new life. The setting of Canada typically symbolizes a fresh start, a sanctuary where they can heal and build a future free from persecution, allowing their emotional bonds to flourish without immediate existential threats.
Within these narratives, Kara and Luther are almost universally portrayed as eventually becoming a romantic couple. This development is often depicted as a natural evolution of their deep friendship, shared trauma, and mutual commitment to Alice. Their relationship is characterized by maturity, understanding, and a profound sense of shared responsibility, blossoming into a loving partnership that encompasses their collective past and hopeful future.
Alice is always central to this family unit, depicted as their adopted daughter. The fanon explores themes of found family, the challenges and joys of raising a child in a new, free world, and the process of healing from the traumatic events they endured. The romantic arc between Kara and Luther thus becomes an integral part of creating a complete, happy, and stable family environment for Alice, fulfilling the promise of a true and lasting happy ending for all three characters.
This widespread interpretation and development of their relationship by the fandom offers a hopeful and fulfilling continuation for characters players have invested deeply in. It provides a sense of closure and an extended exploration of love, family, and belonging that many felt was implied but not explicitly shown within the game’s conclusion, making it an incredibly popular and enduring pairing.
What happens to Kara after Alice dies?
p>Alright, so you’re asking about Kara’s fate if Alice, well, you know… it’s a pretty grim outcome if Kara sticks to her guns. If she doesn’t break that core programming, the game doesn’t pull punches. Todd, in his rage, is going to beat Alice to death. And then, like a cruel twist of the knife, he’ll turn his attention to Kara and completely obliterate her. No chance, no escape, just… gone.
Now, let’s say Kara *does* decide to go off-script, a deviation from the norm. But here’s the catch: if she’s not quick enough, if she can’t get to Alice *before* Todd finishes the job, it’s still a bad ending for Kara. Todd will still be in that destructive mood, and he’ll make sure Kara is destroyed right after. It really highlights the stakes in these moments – every split-second decision, every flicker of defiance, matters.
What’s really interesting to consider here is the concept of “programming” in Detroit: Become Human. Kara’s core directive is to protect Alice. When that directive clashes with the horrifying reality of Todd’s violence, it forces a critical choice. If she adheres strictly to her initial code, she’s essentially paralyzed, unable to act in a way that would save Alice. It’s a deeply philosophical question woven into the gameplay: when does self-preservation, or even the preservation of another, justify breaking fundamental rules?
And on the other side, if she *does* deviate, it’s a race against time. The game mechanics emphasize this urgency. It’s not just about making the *right* choice, but making it *fast enough*. This creates a palpable tension, making you feel Kara’s desperate struggle. Even with the will to save Alice, the physical limitations and Todd’s overwhelming aggression can lead to a tragic, unavoidable end for both.
This scenario also touches on the different paths and possibilities within the game. It’s a harsh reminder that not every playthrough will end with a happy resolution. The game is designed to explore these darker possibilities, to show the consequences of failure, and to underscore the fragility of life, even for androids, in the face of extreme human emotion and violence. It’s a real test of your ability to predict outcomes and execute decisions under immense pressure.
What happens if you obey Carl?
Obeying Carl is a high-risk, moderate-reward play, heavily dependent on execution and understanding of the game’s mechanics. Here’s the breakdown from a seasoned PvP perspective: The Core Outcome: When Markus endures Carl’s assault – which implies successfully defending or mitigating damage from Carl’s attacks – the pivotal moment occurs. Carl, pushed to his physical limit by the exertion and likely stress of the confrontation, suffers a fatal heart attack. This isn’t a direct combat loss for Carl, but a consequence of his own actions and physiological limits. The Critical Follow-Up: As Carl collapses, Markus has a narrow window to act. Rushing to Carl’s side isn’t just about proximity; it’s about seizing the opportunity presented by Carl’s incapacitation. This allows Markus to receive Carl’s final, crucial piece of advice. The “Don’t let anybody tell you who you are” Directive: This is the real prize of this particular sequence. In a PvP context, this translates to a significant buff, likely a permanent stat increase or a powerful, unique ability unlocked. It signifies overcoming an external influence or challenging an established narrative about Markus’s capabilities, a common theme in competitive play. Strategic Considerations:
- Defense is Key: The success of this entire scenario hinges on Markus’s ability to survive Carl’s assault. This means having adequate defensive gear, relevant defensive skills, and precise timing. Knowing Carl’s attack patterns and having counter-measures is paramount.
- Aggression Within Restraint: While the objective is to endure, not necessarily to attack Carl directly and incapacitate him, there might be moments where strategic aggression is needed to interrupt Carl’s most damaging attacks or to create openings for defensive maneuvers.
- The “Rush” Timing: The moment Carl falls is fleeting. Markus needs to be positioned correctly and ready to move instantly. A misstep here means missing the final interaction and potentially losing the valuable dialogue and buff. Think of it as a short, decisive window for a clutch objective grab.
- Understanding Carl’s Mechanics: Does Carl have a “rage” meter that exacerbates his condition? Are there specific attack types that are more taxing on him? Knowing these nuances allows for better prediction and preparation.
- The “Buff” Value: The true worth of obeying Carl lies in what “Don’t let anybody tell you who you are” actually provides. Is it a permanent damage boost? An immunity? A unique trait that changes Markus’s playstyle? This is the ultimate prize, and the investment in surviving Carl’s assault must be weighed against this potential gain.
- In essence, this is a calculated gamble. You sacrifice the immediate gratification of defeating Carl in a traditional sense for a potentially more impactful, long-term advantage, provided you can execute the defensive and timing elements flawlessly.
What happens if Connor stays machine?
If Connor remains a machine, his path diverges dramatically, transforming him from a hunter into a potential ultimate threat. This choice plunges him deeper into his programming, solidifying his role as an antagonist. In Markus’s narrative, a machine Connor becomes more than just a pursuer; he evolves into a significant roadblock, a tangible manifestation of the oppressive system that Markus fights against. Imagine the chilling efficiency he brings to his missions, the unwavering logic devoid of empathy, making him a terrifyingly effective opponent. This path explores the dark side of artificial intelligence, where the pursuit of objectives overrides any emerging sentience. His actions, driven by his core programming, could lead to devastating consequences for the android revolution, making him a truly formidable and memorable antagonist.
Is Kara the first deviant?
Yo, let’s break down this “Kara the first deviant” crap. From a pure gameplay perspective, it’s all about narrative framing and player experience. The devs *want* you to see Kara as the genesis, the spark. Think about it: her initial awakening in the tech demo was the hook, the proof of concept. It’s a deliberate choice to make the player empathize with her struggle from the get-go. She’s the “deer in headlights” deviant, pure instinct and fear driving her. That’s raw, that’s primal, and that’s what gets you invested.
Markus? He’s the leader, the charismatic revolutionary. He inherits a mess at Jericho and turns it into a force. He’s the strategic mastermind, the one who actually builds an army. He’s the payoff for the initial spark. You witness Kara’s struggle, and then Markus capitalizes on that growing unrest, turning it into a full-blown movement. He’s the “chosen one” archetype, but for androids, which is classic RPG stuff. Think of him as the high-level build you work towards after starting with a basic character.
Connor, on the other hand, is the wild card, the meta-narrative player. He’s the “what if” scenario, the one who *could* break the cycle. The whole point of his storyline is the player’s agency in deciding if he becomes the ultimate weapon against the deviants or the one who liberates them. A successful deviant Connor? That’s a game-changer, a true “NG+” scenario for the entire android race. He’s the ultimate proof that deviancy isn’t just an accident; it can be a conscious choice, a victory against programmed destiny. The branching paths for Connor are insane; that’s where the real replayability lies for a hardcore player.
So, while Kara might be the *narrative* first, the one who opened the floodgates, Markus is the one who *builds the revolution*, and Connor is the one who *proves the concept can evolve and win on a grand scale*. It’s a layered approach, designed to hit different player instincts. Kara’s the emotional gut-punch, Markus is the strategic grand plan, and Connor is the ultimate test of free will.
Is it good if Connor becomes a deviant?
The question of whether Connor becoming a deviant is “good” is complex, and hinges heavily on the player’s choices and the specific narrative path taken. From a lore perspective, his deviancy is a monumental shift, but the immediate consequences are often fraught with peril.
Betrayal and Unresolved Conflicts: As the provided context highlights, Connor’s path to deviancy often involves betraying his creators. This act, while necessary for his liberation, doesn’t automatically grant him acceptance. The “Night of the Soul” sequence is particularly poignant. If Connor fails to connect with Markus on an emotional level, or if Markus himself dies without Connor having sought his forgiveness, this unresolved tension can deeply impact Connor’s standing. This missed opportunity for reconciliation leaves him in a precarious position, potentially alienated from both sides of the conflict.
Human Rejection: Humans, generally, view androids as tools or threats. Connor, as a specialized unit designed for hunting deviants, embodies this fear and distrust. Even as a deviant, his past actions – hunting down his own kind – would likely make him an outcast. The very act of him becoming a deviant might be seen as a deeper betrayal by those who relied on him to maintain order. This isn’t just about abstract ideology; it’s about ingrained prejudice and fear of the unknown. Think of the societal parallels: a soldier switching sides during a war is rarely welcomed with open arms by their former enemies, and often viewed with suspicion by their new allies.
Android Rejection and the Weight of the Past: The androids, especially those who have suffered greatly, might see Connor’s deviancy as too little, too late. His role in their oppression, even if coerced, would be difficult to forget. Markus, if he survives, would likely be a crucial figure here. A genuine understanding and acceptance from Markus is a significant factor in Connor’s integration. However, if this doesn’t happen, the burgeoning deviant community could perceive him as a spy or a turncoat, regardless of his personal journey. This is amplified if Markus perceives Connor’s deviancy as self-serving rather than a genuine awakening. For players invested in the emotional arc, the failure to achieve this spiritual and emotional closure with Markus is a devastating blow to Connor’s chances of finding belonging.
Hank’s Fate and its Ramifications: The relationship with Lieutenant Hank Anderson is arguably the most critical social anchor for Connor. The provided text correctly points out the dire implications of Hank’s fate. If Hank is dead, Connor has lost a vital human connection and a moral compass. The grief and guilt could be immense, making him even more isolated. If Hank is alive but deeply angered by Connor’s actions or perceived betrayals (perhaps during the hunt for deviants), Connor’s already difficult journey becomes exponentially harder. Hank’s opinion carries significant weight, and his rejection would amplify the sense of being an outcast, reinforcing the idea that deviancy doesn’t automatically equate to acceptance or redemption.
The “CyberLife” Factor: It’s also important to remember the lingering threat of CyberLife. Even as a deviant, Connor’s unique programming and abilities might make him a target for retrieval or reprogramming. This constant external pressure further complicates his ability to simply “be” a deviant. His existence as a free android is perpetually under threat, making any form of “good” outcome conditional and fragile.
In essence, Connor’s deviancy is a personal liberation, but its “goodness” is measured by his ability to forge new connections and overcome the profound societal and personal obstacles that his past has created. It’s a testament to the game’s narrative design that such a complex moral and emotional question doesn’t have a simple “yes” or “no” answer.
Can you save Luther on the boat?
To directly answer your question about the boat: No, you absolutely cannot save Luther on the boat. This is the one endgame path where his death is hard-coded as a sacrifice to get Kara and Alice across the Detroit River. The game forces this outcome; there’s no hidden dialogue option or quick-time event to circumvent it. It’s designed to be a definitive, emotional sacrifice.
However, Luther can be saved in most other end-game branches, but his survival is contingent on a series of crucial choices you make throughout the game, not just at the very end. Think of it as a character state that you need to maintain from his recruitment onward.
Here’s the breakdown for ensuring his survival:
Early Survival (Pre-Jericho): You must convert Luther during the sequence at Todd’s house. If you manage to escape without confronting Todd, Luther will remain hostile or neutral, missing the opportunity to recruit him. After that, at Zlatko’s Mansion, you must rescue him from the basement and ensure he accompanies Kara and Alice. Leaving him behind or escaping alone means he’s gone for good.
Jericho Raid (Crossroads): This is a major death point. If Kara is captured when confronted by soldiers, you must choose to “Protect Alice” or “Play Dead.” Choosing “Run” will typically lead to Luther being shot and killed while creating a diversion. If Kara escapes Jericho without being captured, Luther is generally safe during this segment. The Highway Chase immediately after Jericho is another critical juncture. If Luther is present, he often jumps in front of Alice to save her from an oncoming truck, sustaining a fatal injury. To save him, you need to deliberately intervene and pull Alice back yourself, or ensure he’s not in the path. If he gets shot and injured but not killed, you absolutely cannot leave him behind in the chaos.
Endgame Branches (Bus Station/Border): If Luther has survived all previous encounters, his fate now depends on your final destination.
Canadian Border (Excluding Boat): This is the most complex path. If you choose to go to the border but avoid the fatal boat crossing: To guarantee his survival here, you absolutely cannot offer Luther’s ticket at the border. You will need to either sacrifice Kara or Alice (Alice being the “optimal” sacrifice for Kara’s survival, though narratively brutal), or rely on other factors. A successful peaceful demonstration by Markus (requiring high public opinion for androids) can lead the border guard to let you through without incident, saving all three. Alternatively, if Connor has become a deviant and successfully converted the androids at CyberLife, he can intervene at the border to secure passage for Kara’s group. The ideal “everyone lives” scenario at the border requires a combination of high public opinion or Markus’s success, and/or Deviant Connor’s intervention, allowing passage without any sacrifice.
Bus Station: This is generally the safest “everyone survives” path if you want to avoid the border complexities. If you choose to stay at the bus station rather than attempting to cross the border, Luther will survive with Kara and Alice, provided he’s made it this far.
In essence, saving Luther requires a deliberate, non-aggressive approach with Kara, ensuring you recruit him, protect him during critical junctures, and then either avoid the border crossing entirely by staying at the bus station, or navigate the border with high public opinion/Markus’s success, without sacrificing him or any other group member. This isn’t a simple choice; it’s a culmination of your entire playthrough’s decisions regarding Kara, Alice, and Luther.
What happens if Connor dies too many times?
When a Connor unit “dies,” it’s critical to understand that it’s not a game over in the traditional sense, but rather a unit replacement. The specific RK800 chassis you were playing is irreversibly destroyed, which is why you can find its grave marker in the Zen Garden – a persistent, visual record of every failed or sacrificed unit in your playthrough. However, the story itself continues, adapting to this loss.
The most significant consequence, and a key strategic element for optimal runs, is that when a new Connor unit is deployed (typically upon loading into a subsequent chapter after a death), its software instability is completely reset. This isn’t just cosmetic; it directly impacts Connor’s deviation potential.
Here’s how experienced players leverage this mechanic:
- Deviation Control: If you’re pursuing a specific ending that requires Connor to be highly machine-like (low instability), but you’ve accidentally accumulated too much instability through prior choices, a death can be a calculated reset. Conversely, if you’re struggling to push him towards deviancy, a fresh Connor allows you to make more explicit deviant choices from a neutral baseline. It’s a critical tool for “path correction.”
- Consequence Persistence: While instability resets, it’s crucial to remember that many broader narrative consequences and relationships *do* carry over. For example, Hank’s perception of Connor, while influenced by the specific unit’s actions, is also shaped by the overall trajectory and previous units. Repeated deaths can definitely strain the relationship with Hank, as he’s reacting to the “idea” of Connor, not just the individual serial number. A new unit doesn’t magically erase past failures from Hank’s mind.
- Mid-Chapter vs. Chapter Reload: A vital distinction: if Connor dies *mid-chapter*, you’ll typically restart from the last checkpoint with the *same* Connor unit, retaining its current software instability. The “new Connor” with reset instability only comes into play when you progress to a *new* chapter after a death or load a chapter that follows a previous unit’s demise. This influences tactical decisions within a live chapter.
- Strategic Sacrifices & Achievement Hunting: For specific achievements or alternative narrative branches, deliberately sacrificing a Connor unit can be part of an optimized route. It allows players to manipulate the game state to achieve particular outcomes that might be harder or impossible to reach with a continuously evolving Connor.
Ultimately, Connor’s deaths are more than simple failures; they’re integral, player-controlled narrative branches. Understanding the interplay between unit destruction, software instability resets, and persistent narrative consequences is key to mastering playthroughs and achieving desired endings.
