Dispatch Guide

The strongest runs come from reading what kind of pressure a mission applies, choosing the right lead, and making sure the route still holds together after that first answer lands. This hub routes you to the page that matches the problem.

Every read below is built around failure modes, not fantasy tiers. The full wiki lives on the sub-site with the deep character, build, episode, and ending breakdowns.

Dispatch tracks five core attributes, and the useful way to read them is not as a power ranking but as five different categories of mission failure. A stat is only “good” when the mission is genuinely losing to the problem that stat solves. The table below is the diagnostic version of the roster page: find the failure you keep suffering, then look at which attribute is being ignored.

Most players do not need a tier list. They need to name the pattern that keeps ending their runs. Dispatch failures repeat in recognisable shapes, and each shape has a different fix. Use this as a triage table before you rebuild anything.

The campaign runs across eight chapters — Pivot, Onboard, Turnover, Restructure, Team Building, Moving Parts, Retrospective, and Synergy — and each one asks a slightly different question. The early chapters teach the dispatch loop and let blind-run anchors prove their value while small route mistakes quietly begin carrying forward. By the middle of the run, pressure types stop appearing one at a time and start stacking, which is the point where role clarity matters more than any individual hero’s ceiling.

The later chapters are where coverage mistakes ripple fastest. Split pressure punishes over-reliance on one favourite solution, social and operational costs begin colliding, and mid-campaign route drift becomes visible in a way it was not before. The finale does not hand out fresh identities; it cashes earlier habits into a legible outcome. That is why a run that spent six chapters wobbling between two tones rarely gets either of them cleanly.

The practical takeaway is simple. Treat the first third of the run as roster education, the middle third as commitment, and the final third as execution discipline. If your team assignments still feel vague at the midpoint, that is a roster-competence problem — not a reason to start chasing a harder ending.

Dispatch endings are best understood as campaign identities rather than final-scene formulas. The trust-first route is built by preserving relationships and keeping the team emotionally workable over time. The results-first route is harsher, organised around control, speed, and immediate outcomes even when those choices carry social cost. The steady professional route comes from deliberate moderation — avoiding both idealistic overreach and destructive severity. The mastery route is the hardest, because it asks you to preserve option space and reduce sloppy damage across the entire run rather than follow a hidden checklist.

Three rules keep those routes clean. Choose the ending you want before the midpoint, because late improvisation produces contradictory runs. Protect the roster before you protect the route, since a perfect ending plan still dies if you arrive at key scenes weakened. And use chapter-start saves rather than panic saves — a save taken after the drift already happened preserves the damage, not the decision point.