Skip to content

Caller / Officers

Callers and officers turn information into risk-managed decisions. The caller chooses the plan; the zerg and officers make the plan survivable.

Core job

The caller creates a battlefield state the zerg can execute.

The caller is not there to micromanage every step. The caller chooses direction, tempo, target logic, terrain objective, risk, and the next step. Officers and role leads help players understand how to execute those decisions.

What good calling uses

Good calling uses real information, not emotion.

Important inputs include:

  • enemy position and movement
  • kill feed and actual deaths
  • cooldown state
  • map and terrain
  • enemy style and likely next action
  • friendly health, spread, role losses, and support state
  • whether the zerg is close enough to act
  • whether a front is lethal now or spent
  • objective state, if relevant

Caller style must match formation

A formation that wants ranged pressure, arcs, and repeated front-to-back pressure cannot be called exactly like a melee flood. A bomb squad cannot be judged like a territory-hold force. A kite-control group cannot endlessly kite away from a fixed objective without an objective plan.

Callers should know:

  • what their own roster can actually execute
  • whether the comp wants to enter, hold, kite, flood, bomb, or pressure
  • what support density is required for the call
  • whether the next call has an exit or follow-up
  • which terrain makes the call possible

Direction calls are tactical intent

A call like "west," "walk in," or "spread" is not just a movement input. It usually means something like:

  • take an angle
  • cross a choke
  • protect an allied front
  • punish spent cooldowns
  • escape a danger lane
  • create a front
  • hold space so the next wave can cross

Good callers make intent clear when time allows. Good players learn to infer intent when time does not.

Officer responsibility

Officers should convert doctrine into simple operational checks:

  • Are healers present and mixed correctly?
  • Are critical supports covered?
  • Are tanks front enough to protect the zerg?
  • Are DPS close enough to hit the next turn?
  • Are scouts reporting useful direction and timing?
  • Is the review focused on repeated habits instead of every mistake?
  • Is the strategy realistic for this roster's current skill level?

Secondary caller / scout protocol

Secondary information should help the caller, not compete with the caller.

Useful officer/scout reports are:

  • concise
  • directional
  • timely
  • relevant to a decision
  • stopped once the caller has enough information

Bad support calling floods comms, repeats panic, or starts issuing separate commands to the main zerg.

Common failures

Failure Result
Calling based on hype reports The zerg commits on false confidence.
No next step after engage Players clump, drift, or panic.
Ignoring terrain The call looks good but cannot be executed.
Calling against roster reality Players fail even if the plan is theoretically correct.
Reading only total deaths Losing key roles may matter more than raw numbers.
Over-reviewing everything Players leave with no clear habit to fix.
Letting officers over-call Comms become noisy and the main plan weakens.

Caller VOD prompt

After a fight, pick one call that worked and one call that failed. For each, identify:

  • what information the caller used
  • what terrain or angle the call depended on
  • what the enemy could do next
  • what the zerg needed to do to mitigate risk
  • whether the next step was clear
  • whether failure came from call quality, roster execution, role losses, or comp mismatch