How two players divide labour, cover gaps, and maintain recoverable state when individual performance diverges.
The four archetypes we use to classify player function in cooperative systems. Every campaign demands a different mix.
The vanguard's primary function is to occupy enemy attention and create operational room for the partner. This is not simply "tanking." It is spatial control. A good vanguard understands aggro radius, line-of-sight manipulation, and the timing of retreat to force enemies into chokepoints where the partner's area abilities become effective.
Controllers manage the geometry of the battlefield. Crowd control, slow fields, wall placement, and suppression fire all serve the same purpose: to reduce the number of variables the team must process simultaneously. The best controllers do not merely stun enemies; they shape the flow of combat so that the striker's shots matter more.
Support is the team's insurance policy. Healing, shielding, revive mechanics, and buffs all extend the margin for error. In high-difficulty campaigns, support is not a luxury but a requirement: without it, a single positional mistake ends the run. The support player's communication load is typically highest because they must track two health bars, two cooldown states, and the spatial relationship between both players.
The striker converts setup into damage. They require protection and positioning assistance to reach their output ceiling. A striker operating without vanguard or controller support is mathematically inefficient: they spend more time evading than attacking. The striker's communication load is lowest but their dependency on partner performance is highest.
Each archetype covers specific threat categories. No single role covers all four.
Not all roles speak equally. We measure callout density, information type, and decision authority per archetype.
| Role | Callouts / Min | Info Type | Decision Weight |
|---|---|---|---|
| Vanguard | 8–12 | Position, threat direction | High |
| Controller | 6–10 | Timing, zone status | Medium |
| Support | 12–18 | Status, cooldowns, retreats | Critical |
| Striker | 4–7 | Target priority, ammo | Low |
When a player goes down, the remaining agent must decide: revive immediately, clear threats first, or retreat to checkpoint. Recovery tools — revive beacons, self-revive charges, teleport pads — change this calculus. We catalogue which campaigns provide generous recovery options and which punish the first mistake with a full restart.
Support players carry the heaviest communication burden because they must translate internal state (cooldowns, resource levels) into actionable verbal instructions for a partner who cannot see those values.
In campaigns with shared health pools, this burden shifts toward the vanguard, who must now communicate positional risk in terms of collective rather than individual survival.