Skip to content

Direction Calls Are Tactical Intent

Core rule

A direction call is not always a literal walking instruction. It is usually an instruction to create a battlefield state.

"West" might mean:

  • take the west angle
  • cross the west choke
  • push through a spent enemy front
  • protect an allied front to the west
  • avoid the north bomb lane
  • get west of a bridge before the next engage
  • hold the enemy from escaping west

Why players fail this

Players often follow the word but miss the purpose.

Examples:

  • Caller says "walk in" and players drift sideways because red name tags look scary.
  • Caller says "spread" and players leave the fight instead of spreading into useful positions.
  • Caller says "come south" and tanks/supports abandon the danger lane instead of covering the movement.
  • Caller says "get west of bridge" and players stop at the bridge because another enemy front appears on screen, even if that front has spent cooldowns.

How to interpret a call

Ask quickly:

  1. What is the caller trying to create?
  2. Where should my role stand for that to work?
  3. Which enemy front is lethal?
  4. Which enemy front is spent?
  5. Where are my healers/supports/tanks relative to this movement?

Officer note

When possible, callers should attach intent:

  • "Walk west, get past the bridge."
  • "Spread southeast, keep Q/W north."
  • "Hold this choke; help the next wave through."
  • "Ignore the spent front; kill the west group."

Short intent can prevent many wrong-role interpretations.

VOD prompt

Review one failed call and ask:

  • Did the call itself lack information?
  • Did players ignore clear intent?
  • Did different roles need different lines?
  • Did someone follow the literal word while failing the actual job?