Episode 6, Moving Parts, is where Dispatch finally stops pretending your earlier calls were just flavor. This chapter pulls multiple dormant variables out of the save file and puts them under pressure, often mid-scene, with no rewind safety net. If Episode 5 felt like setup, Episode 6 is the stress test, checking which alliances hold, which lies collapse, and which NPCs are still willing to take your calls.
Why Episode 6 Changes the Rules
Moving Parts is built around compounded consequences rather than single binary choices. Several decisions trigger while you’re already managing active objectives, meaning dialogue options can be locked out by timing, positioning, or who currently has narrative aggro. Miss a prompt or stall too long, and the game silently defaults to a path that can’t be undone without a full replay.
This episode also introduces overlapping consequence windows. One choice can immediately change a scene’s dialogue tone while also flagging a delayed outcome that won’t pay off until Episode 7 or later. Completionists should treat every conversation like it’s tracking hidden meters, because in many cases, it is.
Returning Threads From Earlier Episodes
Episode 6 heavily references decisions made as far back as Episode 2, especially how you handled early authority figures and information leaks. Characters remember if you stonewalled them, fed them partial truths, or openly burned bridges, and those memories directly affect who shows up, who stays silent, and who actively undermines you.
Side characters previously considered optional can re-enter the story here with upgraded narrative weight. If you invested in their arcs earlier, they can intercept negative outcomes or unlock alternate dialogue branches. If you ignored them, Episode 6 doesn’t compensate; it escalates without them.
What Carries Over Into Moving Parts
The episode checks several persistent flags before the opening scene even finishes loading. Your standing with central factions, unresolved favors, and any morally gray calls you made under pressure are all evaluated. These checks don’t just alter flavor text; they change which choices even appear on-screen.
Some carryover effects are subtle, like different phrasing that nudges you toward compliance or defiance. Others are blunt, removing entire decision paths or forcing you into damage control mode. Understanding what carries over is critical, because Episode 6 assumes you remember your past calls and punishes you if you don’t.
Choice Density and Player Control
Moving Parts has one of the highest choice densities in Dispatch so far, but not all choices are equal. Some are loud and cinematic, clearly signaling a branch point, while others are quiet micro-decisions buried in procedural dialogue. Those smaller moments often have the longest tails.
Players aiming for full completion should expect multiple replays, not just for alternate endings, but for entirely different scene structures. Episode 6 isn’t about picking the right answer; it’s about understanding when the game is even letting you choose.
Opening Briefing Choices: How Your Attitude Shapes Early Trust and Information Flow
The first interactive moment in Moving Parts isn’t an action beat or a timed prompt. It’s the briefing. This scene quietly sets your trust baseline for the entire episode, determining who feeds you clean intel, who withholds details, and who starts laying narrative traps before you even leave the room.
If you skim this conversation or assume it’s just flavor, you’ll miss some of the most important structural forks in Episode 6. Your attitude here controls information flow the same way aggro management controls a tough encounter: misplay it, and everything downstream hits harder.
Professional Compliance vs. Controlled Pushback
Your first real choice comes when the briefing officer outlines the operation parameters and casualty tolerances. You can respond with full professional compliance, acknowledging the chain of command without challenge, or push back by questioning the assumptions behind the plan.
Choosing compliance immediately raises your internal Trust flag with central command. The immediate effect is subtle but powerful: follow-up dialogue becomes more detailed, and you receive a clean timeline of moving parts instead of a summarized version. Later in the episode, this also unlocks an optional mid-mission call that can redirect resources in your favor.
Pushing back doesn’t burn the bridge, but it marks you as a variable. You’ll still proceed with the mission, but key briefing details are deliberately vague, forcing you to uncover them through environmental storytelling or side conversations. Long-term, this path increases your leverage with field operatives while lowering command reliability.
Empathy, Detachment, or Sarcasm
Mid-briefing, the conversation pivots to potential civilian impact and internal fallout if things go sideways. This is where tone matters more than content. You can respond with empathy, emotional detachment, or sharp sarcasm.
Empathy reinforces relationships established in earlier episodes, especially if you previously protected non-combatants or exposed cover-ups. The immediate payoff is an extra dialogue line from a secondary analyst that flags a hidden risk not marked on your objective HUD. That risk becomes avoidable later only if you heard this warning.
Detachment keeps things strictly procedural. You don’t gain or lose trust outright, but you also don’t unlock supplemental information. This is the cleanest path mechanically, but it leads to a more rigid mission structure with fewer improvisational outs.
Sarcasm lowers surface trust but raises narrative tension. Characters respond defensively, and the briefing ends faster, skipping one optional clarification entirely. However, this path flags you for an alternate confrontation later where withheld information comes out under pressure, changing who takes the blame when systems fail.
Accepting the Narrative or Questioning the Source
The final briefing choice asks whether you accept the official explanation for why this operation is happening now. You can acknowledge it at face value or openly question the timing and motives behind it.
Accepting the narrative locks in a streamlined information path. Objectives update cleanly, NPCs stay on-message, and the game subtly nudges you toward efficiency over investigation. This is the fastest route through Episode 6 and ideal for players chasing specific endings tied to operational success metrics.
Questioning the source immediately tags you as skeptical. You gain access to a hidden dialogue tree with a logistics officer after the briefing, opening a side channel of intel that reframes several later events. The tradeoff is delayed support and higher friction with command during critical moments.
Why These Early Choices Matter More Than They Look
None of the opening briefing choices trigger a splashy “choice saved” indicator, but they’re among the most mechanically influential decisions in Moving Parts. They determine which dialogue nodes even exist later, not just how characters feel about you.
For completionists, this means at least three distinct briefing outcomes to catalog, each with unique information availability and downstream consequences. Episode 6 doesn’t reward guessing the right attitude; it rewards committing to one and understanding what systems you’re activating by doing so.
Workshop & Prep Decisions: Resource Allocation, Dialogue Branches, and Hidden Flags
Once the briefing ends, Episode 6 quietly shifts from talk to systems. The workshop and prep phase looks like downtime, but this is where Moving Parts starts hard-locking variables that won’t surface until much later. Every choice here affects loadouts, NPC availability, and which failure states the game considers “acceptable.”
Allocating Parts: Efficiency vs. Redundancy
Your first real decision is how to allocate limited mechanical parts across the workshop stations. You can fully optimize one system or spread resources thin to cover multiple contingencies. Focusing on a single system boosts its reliability, reducing RNG during scripted failures later in the episode.
Spreading parts across multiple systems increases your improvisational options but lowers overall stability. This flags the mission for dynamic malfunctions, where failures trigger dialogue checks instead of outright mission penalties. Completionists should note that at least one unique repair scene only appears if no system is fully optimized.
Who You Assign to Prep Matters More Than the Gear
After parts allocation, you choose which crew members handle specific prep tasks. This isn’t just flavor dialogue; it directly modifies trust values and competence checks. Assigning the “wrong” character to a task won’t fail it immediately, but it sets a hidden stress counter that can break under pressure later.
Pairing characters with overlapping expertise reduces failure chances but skips several character-driven conversations. Mismatched assignments unlock deeper banter and hidden flags tied to personal arcs, at the cost of higher risk during timed sequences. If you’re chasing all narrative beats, intentional inefficiency is the play.
Optional Workshop Conversations and Silent Flags
Before finalizing prep, you can freely move around the workshop and initiate optional conversations. These don’t show dialogue icons unless you’re close, and skipping them doesn’t trigger a warning. Each conversation plants a silent flag that alters how those NPCs interpret your decisions mid-mission.
Some of these flags only matter if systems start failing. For example, acknowledging a technician’s concern earlier can prevent blame-shifting during a later meltdown, even if you made objectively worse prep choices. Missing all optional conversations locks you into a strictly mechanical resolution path.
Choosing When to Lock In
The final prep decision is when you choose to deploy. You can launch immediately or spend extra time “double-checking” systems. Launching early preserves momentum and keeps command approval high, but it disables one last-minute adjustment opportunity.
Delaying the launch opens a short, time-gated interaction where a hidden issue can be discovered and either ignored or addressed. Addressing it costs resources but prevents a forced failure state later. Ignoring it accelerates the mission and flags a high-tension confrontation where that flaw becomes a narrative centerpiece.
Why the Workshop Is a Narrative Gate, Not a Menu
Moving Parts uses the workshop to disguise branching story logic as resource management. None of these choices are reversible, and most don’t pay off until well into the operation. By the time consequences surface, the game treats them as inevitabilities, not forks.
For players cataloging every possible outcome, this phase alone accounts for multiple unique dialogue scenes, at least two alternate failure resolutions, and several character-specific reactions that never overlap in a single run. If the briefing set your attitude, the workshop defines your version of the mission.
Mid-Episode Confrontation: Key Moral Choice That Splits the Episode in Two
Everything seeded in the workshop detonates here. Roughly halfway through Moving Parts, the mission grinds to a halt when the system flaw you either uncovered, ignored, or never noticed forces a live confrontation between command, your on-site lead, and the NPC most affected by the failure. This is the first time the game stops treating your choices as background math and makes you answer for them in real time.
This confrontation is not timed, but it is locked. Once the dialogue wheel appears, you cannot back out, reload checkpoints, or reopen prep options. From here on, Episode 6 commits to one of two structurally different paths.
Trigger Conditions: Why This Scene Plays Differently Every Run
The confrontation always occurs after the second system cascade, but who initiates it and how hostile it starts depends on silent flags from the workshop. If you addressed the hidden issue earlier, the tone is controlled and procedural, with command asking for confirmation before assigning blame. If you ignored it or launched early, the scene opens accusatory, with overlapping dialogue and reduced response options.
Optional workshop conversations directly affect which NPC speaks up for you. A technician you acknowledged earlier will interrupt to contextualize the failure, lowering tension and unlocking a de-escalation response. Without that flag, the game frames the failure as singularly yours, even if the root cause was systemic.
The Core Choice: Accept Responsibility or Shift the Blame
The pivotal decision presents as two main dialogue branches with slight phrasing variations based on prior flags, but functionally they boil down to ownership versus deflection. Accepting responsibility stabilizes the room immediately, cutting off one aggressive interruption and restoring full dialogue visibility. Shifting blame escalates the confrontation, adds a secondary argument layer, and permanently locks out one character-specific trust flag.
This is not a cosmetic choice. The game internally marks this as the episode’s moral axis, and everything that follows is built around it, from objective structure to character availability.
Path One: Owning the Failure and Containing the Damage
Choosing to accept responsibility leads to a slower, more controlled second half of the episode. You gain access to an emergency mitigation objective that replaces a later forced failure, but it costs time and resources, similar to a low-DPS, high-survivability build. Dialogue shifts toward problem-solving, and command approval stabilizes instead of spiking.
Long-term, this path preserves relationships. Characters who were on the fence remain interactable in Episode 7, and one late-game scene only triggers if you took the blame here. The tradeoff is operational: you will enter the finale of Moving Parts with fewer tools and no margin for sloppy execution.
Path Two: Deflecting Blame and Forcing the Mission Forward
Shifting blame keeps momentum high but turns the episode adversarial. The immediate payoff is speed: objectives compress, one mitigation step is skipped entirely, and you gain a temporary performance buff during the next sequence. Think of it as trading I-frames for raw aggression.
Narratively, this path burns bridges. One NPC disengages entirely for the rest of the episode, and future dialogue with command becomes conditional rather than collaborative. A later system failure becomes unavoidable, reframed as sabotage or incompetence depending on earlier workshop flags.
Hidden Variations Completionists Should Track
There are minor but meaningful permutations within each path. If you previously discovered the hidden issue but still shift blame, the game flags this as intentional negligence, unlocking harsher dialogue later. Conversely, accepting responsibility without having known about the issue frames you as principled but unprepared, altering how characters describe you behind your back.
For full completion, you need at least two runs here, plus a third if you want to see the rare variant where a technician intervenes unprompted and partially overrides your choice. That outcome only occurs if you spoke to them in the workshop and delayed launch long enough to acknowledge their concern without fixing it.
This confrontation is the spine of Moving Parts. Everything before it loads the gun, and everything after it fires based on how you pull the trigger.
Character-Specific Interventions: Who You Back, Who You Alienate, and Optional Scenes Unlocked
Once the blame is assigned and the mission state locks in, Episode 6 pivots into a quieter but more volatile phase. This is where Dispatch stops testing your leadership and starts tracking your loyalty. The game surfaces this through character-specific interventions, short dialogue forks that look optional but quietly rewrite who stands with you when Moving Parts hits its final beat.
These moments are easy to miss on a first run because they don’t announce themselves as “choices.” They trigger during downtime movement, comms checks, and transitional cutscenes, and each one acts like a soft aggro pull toward or away from a specific NPC.
Backing the Engineer: Stabilization Over Speed
If you side with the engineer during their post-confrontation breakdown, you slow the episode down even further. The immediate change is tonal: dialogue becomes technical and procedural, with fewer emotional spikes and more mechanical clarity. You also unlock an optional diagnostic scene where they walk you through a temporary workaround that slightly reduces failure RNG in the final sequence.
The cost is social. Command reads this as coddling, and their trust meter drops even if you previously took responsibility. In Episode 7, this flags you as reliable but hesitant, closing off a later command-driven shortcut unless you compensate with aggressive decisions elsewhere.
Backing Command: Authority at the Cost of Trust
Throwing your support behind command hard-locks the episode into a top-down structure. Dialogue tightens, interruptions are cut off, and one mid-mission debate is skipped entirely. Mechanically, this gives you cleaner objective markers and a small timing buffer during the next gameplay segment.
The fallout hits later. The engineer disengages from optional chatter for the rest of Moving Parts, and an optional repair scene never triggers. Long-term, this marks you as efficient but disposable, which changes how command speaks to you in Episode 7 and removes a late-game chance to challenge their decisions.
Supporting the Field Operative: Emotional Buy-In, Tactical Risk
If you back the field operative during their intervention, the episode takes on a more personal edge. You unlock an optional scene where they admit fault in a private exchange, reframing earlier failures as human error instead of systemic breakdown. This also grants a temporary morale buff that makes one high-pressure QTE more forgiving.
However, this path increases systemic risk. Without addressing the underlying issue, a later complication becomes more volatile, requiring faster inputs and tighter execution. Narratively, command flags this as favoritism, which can compound if you’ve already deflected blame earlier.
Staying Silent: The Ghost Path
Choosing not to intervene at all is the most passive option, and the game treats it as such. You avoid immediate relationship loss, but you also unlock nothing. One optional scene disappears entirely, replaced by a brief, colder transition that signals emotional distance across the board.
This path is deceptively punishing for completionists. Several flags remain unset, which blocks two rare dialogue variants in Episode 7 and prevents a late-game character from referencing your leadership directly. It’s safe in the moment but hollow in the long run.
Rare Cross-Flags and Missable Variants
There are a few edge cases worth tracking. If you previously accepted blame and then back the engineer, an extended version of their diagnostic scene plays, revealing foreshadowing for a future system failure. If you deflected blame but later support the field operative, the game marks this as contradictory leadership, unlocking a tense private reprimand from command.
The rarest variant requires you to stay silent here after having built high rapport with all three characters earlier in the episode. This unlocks a brief, easily missed scene where they intervene without you, resolving one conflict internally and subtly reducing your narrative presence. It’s a fascinating outcome, but one most players will never see without deliberate planning.
These interventions don’t change the destination of Moving Parts, but they absolutely change who arrives there with you, and who’s already decided you won’t survive the next mission.
Operational Call Under Pressure: Timed Choice Outcomes and Failure Variants
After the relational fallout settles, Episode 6 pivots hard into mechanics. The operational call drops mid-crisis, the UI desaturates, and the timer starts ticking before you’ve even finished reading the prompt. This is Dispatch at its most honest: your leadership stats, hidden flags, and raw reaction speed all collide here.
Unlike earlier dialogue trees, this decision is partially gated by performance. Hesitation isn’t neutral. It’s tracked, graded, and sometimes punished harder than an outright bad call.
Immediate Response: Commit Within the Timer
Locking in a choice before the countdown hits the final third triggers the “decisive command” modifier. The operator responds faster, QTE windows widen slightly, and one follow-up check becomes binary instead of multi-stage. You’re essentially trading narrative flexibility for mechanical stability.
Dialogue reflects this urgency. Characters acknowledge the snap call, even if they disagree, and later debriefs frame the outcome around execution rather than judgment. Long-term, this sets a hidden flag that slightly lowers failure RNG during timed events in Episode 7.
Delayed Input: Last-Second Decision
Waiting until the timer is nearly depleted creates a different branch entirely. The game treats this as reactive leadership, keeping the mission intact but stripping away the decisive modifier. QTEs retain their standard windows, and one interaction gains an extra failure state.
Narratively, characters comment on the hesitation. No one fully challenges you yet, but trust erosion begins here, especially if combined with earlier silence or blame deflection. This path is mechanically survivable but narratively brittle, making later high-stress calls far less forgiving.
Timeout Failure: No Choice Made
Letting the timer expire isn’t a game over, but it is a hard failure state. Control defaults to command protocol, removing player agency for the remainder of the sequence. You lose access to a mid-mission dialogue interrupt and one optional recovery QTE disappears entirely.
This variant carries weight. The episode continues, but the game logs this as an abdication of command, which compounds with the Ghost Path from earlier. In Episode 7, at least one character will explicitly reference this moment as proof you freeze under pressure.
System Stress Failure: Mechanical Misses After the Call
Even with a successful choice, poor execution can fracture the outcome. Missing two QTEs during the follow-through triggers a partial failure where the operation completes, but with collateral damage. You keep the main narrative path, but lose a resource flag that affects late-episode support options.
This is where earlier decisions quietly matter. Players who earned the morale buff from backing the engineer get extended I-frames on one critical input. Without it, the hitbox is tighter, and failure becomes far more likely on repeat attempts.
Hidden Variant: Overcorrection Path
There’s a rare outcome if you commit instantly and then perfectly execute every QTE. The game flags this as overcorrection, unlocking a short exchange where command questions your autonomy rather than your competence. It’s subtle, easy to miss, and purely narrative, but it reshapes how authority dynamics play out later.
Completionists should note this variant doesn’t alter the ending, but it does change who challenges you in Episode 8. It’s Dispatch rewarding mastery while still reminding you that flawless execution can be just as threatening as failure.
The operational call is where Episode 6 stops asking who you support and starts testing whether you can lead at all. Every second, every input, and every prior flag feeds into how this moment resolves, making it one of the most mechanically and narratively dense choices in Moving Parts.
Climax Resolution Paths: Success, Compromise, or Breakdown Endings Explained
Once the operational call locks in, Episode 6 stops branching quietly and starts resolving loudly. Every flag you’ve tripped so far funnels into one of three climax resolution paths, each with its own dialogue cadence, control behavior, and long-term narrative weight. This isn’t just about whether the mission “works,” but how Dispatch judges your leadership under stress.
The game calculates this outcome the moment the final system sync completes, checking your call choice, QTE performance, morale modifiers, and whether command protocol was ever forcibly engaged. From there, the episode commits to Success, Compromise, or Breakdown, and there’s no save scumming your way out without a full replay.
Full Success Ending: Command Holds, Authority Stabilized
The Success path triggers if you make a decisive operational call, avoid command override, and clear the follow-through sequence with zero mechanical failures. Dialogue remains fully player-driven through the final exchange, including a last optional interrupt that lets you frame the operation’s outcome on your own terms. This is the only route where Dispatch explicitly credits you with stabilizing the system rather than surviving it.
Mechanically, this path preserves all late-episode resources and unlocks a support asset for Episode 7 that reduces RNG during high-pressure dialogue checks. Narratively, characters defer to you more readily, and skepticism shifts from your competence to your intent. Completionists should note this is also the cleanest setup for the Authority Path in Episode 8.
Compromise Ending: Mission Complete, Trust Fractured
The Compromise path is the most common result and fires when the operation succeeds but with either collateral damage or partial loss of control. This can come from missed QTEs, losing the morale buff earlier, or triggering system stress without fully collapsing into override. You keep agency in the final scene, but dialogue options are narrowed and noticeably defensive.
Short-term, you lose one support flag that affects how aggressively allies back you in Episode 7 encounters. Long-term, Dispatch logs this as a “contained failure,” meaning characters acknowledge the save but question your decision-making process. It’s a playable, narratively rich outcome, but one that constantly reminds you the system doesn’t fully trust you anymore.
Breakdown Ending: Override Engaged, Agency Removed
The Breakdown ending is triggered by hard failure states, command protocol activation, or stacking enough negative flags that the system preempts your authority. Control is stripped during the climax, dialogue auto-plays, and one final scene is reframed entirely from Dispatch’s perspective. You’re present, but no longer the driver.
This outcome permanently tags your profile with an abdication marker that carries into Episode 7 and beyond. Certain characters will bypass persuasion checks entirely, assuming you’ll fold under pressure. From a completion standpoint, this ending locks out multiple future branches, making it essential viewing for players cataloging every narrative consequence.
Each resolution path isn’t just an ending, but a verdict on how you handled power when it mattered. Episode 6 uses this climax to crystallize your leadership identity, ensuring that every prior choice, clean input, or mechanical slip finally gets weighed and remembered.
Persistent Consequences: How Episode 6 Choices Alter Future Episodes and Character States
Episode 6 doesn’t just close a chapter; it writes backend variables that quietly reshape how Dispatch treats you going forward. Every major decision in Moving Parts feeds into persistent flags that alter dialogue logic, encounter pacing, and even who’s willing to take a risk on your call later. Think of this episode as setting your long-term aggro profile with the system itself.
Authority Score: The Hidden Variable That Follows You
Your Authority Score is finalized here, based on how often you asserted control versus deferred to protocol during the operation. Backing Dispatch during the mid-episode routing conflict boosts this stat, while hesitating or asking for consensus tanks it. The score isn’t shown, but you’ll feel it immediately in Episode 7 when dialogue options either open aggressively or auto-collapse into neutral responses.
A high Authority Score unlocks proactive commands in future encounters, letting you set objectives instead of reacting to them. A low score shifts you into a reactive role, where NPCs feed you limited options and expect compliance. Completionists should note that several Episode 8 scenes only trigger if this score crosses a hidden threshold.
Character Trust States: Who Backs You When Systems Fail
Episode 6 locks in individual trust states for three core characters based on your crisis handling during the control room sequence. Choosing to manually reroute systems earns respect from hands-on operators but alienates analysts who prefer clean data solutions. Letting Dispatch automate the fix flips those alignments entirely.
These trust states directly modify persuasion checks later, changing both success rates and available dialogue trees. In some cases, a trusted character will interrupt a hostile exchange on your behalf, effectively skipping a skill check. If trust is fractured, those same characters stay silent or actively side with Dispatch’s logic over yours.
System Stability Flags and Future Mission Difficulty
How cleanly you resolved the mechanical failures in Episode 6 determines your System Stability flag. Perfect execution keeps stability high, smoothing RNG in later missions with fewer surprise modifiers and tighter I-frame windows during QTE-heavy scenes. Partial success introduces instability, increasing encounter variance and stacking stress effects faster.
A Breakdown Ending permanently lowers this flag, which subtly increases failure chances in Episode 7 set-pieces. It’s not a raw difficulty spike, but you’ll notice narrower margins for error and less forgiving timing. Players aiming for full mastery runs should experience at least one low-stability path to see how drastically it reframes familiar encounters.
Dispatch Perception: Ally, Overseer, or Opponent
Episode 6 cements how Dispatch perceives your role in the hierarchy. Authority and Control endings push Dispatch into a reluctant ally state, where it challenges you but ultimately defers. Compromise positions Dispatch as an overseer, constantly auditing your calls and flagging risk.
The Breakdown Ending flips Dispatch into a soft antagonist role. It doesn’t attack you outright, but it withholds information, delays responses, and reframes objectives without your input. This perception shift alters mission briefings and can even change how scenes are framed visually, reinforcing the loss of agency through presentation alone.
Locked and Unlocked Narrative Branches
Several future branches are hard-gated by Episode 6 outcomes. The Authority Path in Episode 8 requires either a Control Ending or a Compromise Ending with high Authority carryover. Conversely, the Subservience Arc only opens if you hit the Breakdown Ending and fail at least one follow-up assertion check in Episode 7.
Some side scenes are mutually exclusive, meaning full completion requires multiple replays of Moving Parts. The game tracks these outcomes globally, so seeing every branch isn’t about perfection, but about intentional failure as much as success. Episode 6 makes it clear that Dispatch remembers everything, especially the moments where you let the system decide who you were.
Completionist Checklist: All Choices, Variants, and How to Unlock Every Scene
If you’re chasing 100 percent narrative completion, Episode 6 is where clean runs stop being enough. Moving Parts is dense with layered decisions, hidden thresholds, and conditional scenes that only fire if you deliberately push or break the system. Below is a scene-by-scene checklist of every meaningful choice, what it changes immediately, and how it ripples forward.
Opening Briefing: Framing the Crisis
The episode opens with Dispatch asking how you want the situation framed before any objectives are locked. Choosing “Operational Efficiency” shortens the briefing and removes optional dialogue prompts later, but grants a small stability buffer during the first QTE sequence.
Selecting “Human Impact” unlocks additional civilian callouts mid-mission and adds a stress tick if you hesitate during timed responses. The third option, “System Integrity,” is easy to miss and only appears if Authority was high at the end of Episode 5, triggering a colder tone and a unique Dispatch voice line that never repeats elsewhere.
Mid-Mission Override: Follow Protocol or Improvise
Roughly halfway through the episode, you’re forced to decide whether to follow Dispatch’s recommended routing or manually override it. Following protocol locks you into a safer path with tighter hitbox tolerances but fewer dialogue branches.
Improvise opens up a riskier sequence with wider mechanical variance and extra reaction checks. Fail even one of these and you’ll see the first signs of Dispatch’s patience eroding, including delayed UI prompts and altered subtitle timing that persists for the rest of the episode.
Critical Call: Who Takes the Blame
This is the episode’s most important branching decision and the one most players will need multiple replays to fully map. Accepting responsibility boosts Authority immediately but increases stress accumulation in the final act, making late QTEs less forgiving.
Deflecting blame to Dispatch preserves stability but permanently flags you as evasive, which disables one optional scene in Episode 7. Sharing responsibility is the hardest option to unlock, requiring high Control and zero failed checks so far, and leads to a rare neutral outcome that subtly reshapes how Dispatch addresses you going forward.
Optional Intervention Scene: Save or Sacrifice
This scene only triggers if you chose “Human Impact” earlier and successfully improvised during the mid-mission override. Intervening saves the NPC but causes a hidden stability drain that can push borderline runs into Breakdown territory.
Ignoring the intervention maintains system metrics but alters later dialogue, with Dispatch referencing the decision in a chillingly detached manner. For completionists, both outcomes count as distinct scene flags and are tracked separately in the global timeline.
Final Confrontation: Assert, Negotiate, or Submit
The closing exchange determines your ending state and Dispatch’s long-term perception of you. Asserting control requires high Authority and no more than one stress spike, leading to the Control Ending and unlocking future command-based dialogue trees.
Negotiation is more forgiving mechanically but caps Authority gains, funneling you into the Compromise Ending. Submission is only available if stability is already low, triggering the Breakdown Ending and permanently altering Dispatch’s behavior in all subsequent episodes.
Hidden Variant: Silent Dispatch
There is a rarely seen variant where Dispatch goes silent during the final sequence. To unlock it, you must improvise, fail exactly two reaction checks, and then attempt to assert control anyway.
The result is a stripped-down ending with no music cues and minimal UI, designed to make the absence feel intentional. It doesn’t change your ending label, but it unlocks a unique codex entry and is required for full narrative completion.
Completion Tips and Replay Strategy
For efficiency, don’t aim for perfection on your first replay. Intentionally tank stability early to access Breakdown-only scenes, then reload with optimized play to clean up Authority and Control variants.
Episode 6 is built to reward curiosity, not mastery alone. If Dispatch feels like it’s watching you more closely here, it’s because it is, and every choice you make in Moving Parts proves whether you’re shaping the system or being shaped by it.