Skip to content

Caller Decision Framework

Core rule

A caller turns information into executable decisions.

Good calling is not only finding clumps. It is matching roster, terrain, enemy style, cooldown state, and objective pressure into the next safest useful action.

The caller's repeated questions

  1. What is our formation trying to do?
  2. What is the enemy trying to force?
  3. Which front is lethal next?
  4. Which side has spent cooldowns?
  5. Which terrain matters right now?
  6. Are we hitting, stabilizing, crossing, chasing, rotating, or resetting?
  7. What happens after our engage?

The next-step rule

Every engage should have a next idea:

  • push through
  • spread and Q/W
  • back out
  • hold the choke
  • cross the bridge
  • switch fronts
  • punish the counter
  • mount/chase

A good first call with no next step can still collapse.

Roster reality

Callers must call the roster they have, not the perfect roster in theory.

Ask:

  • Do we have enough healers connected?
  • Are supports reliable enough for this crossing?
  • Can DPS hit this timing?
  • Are tanks playing forward enough to create safety?
  • Is this strategy above the roster's current maturity?

Common caller mistakes

  • calling a ranged formation like a melee flood formation
  • taking terrain the roster cannot execute on
  • switching fronts before stabilizing
  • overcommitting because the enemy survived a bad risk once
  • reading total deaths but not role deaths
  • ignoring the next enemy counter path

Training prompt

Review caller macro separately from player execution:

  • Was the call reasonable with available information?
  • Did the roster have the tools and positioning to execute it?
  • Did players fail the call, or did the call ask for something impossible?
  • What should the next call have been?