Game attack telegraphing explained

What telegraphing is (and is not)

A telegraph is any perceptual signal that precedes an attack's active frames — the window where hit detection runs and damage applies. Good telegraphing does not make combat easy; it makes failure attributable. Players should think “I saw the red ring and dodged late,” not “the game cheated.”

Telegraphing versus difficulty

Hard games telegraph clearly and punish precisely. Dark Souls bosses are famous for long windups on heavy swings, not for hiding them. Difficulty comes from pattern complexity, stamina pressure, and positioning — not from shortening tells until reaction becomes impossible. As a rule of thumb: if your median human reaction time is ~250 ms and your input buffer is ~100 ms, an unavoidable attack needs at least 350–450 ms of readable windup before active frames on a first encounter. Expert players can handle less; new players need more. Scale tells per difficulty mode or via adaptive assists.

Telegraphing versus RNG

Random attack selection without distinct tells feels like RNG death. If three moves share the same startup animation, players cannot learn. Either unique windups per move or explicit phase transitions (boss roars before leap) are required. Mix-up design — feints, delayed active frames — is advanced; ship readable base patterns first.

Telegraph channels: visual, audio, and UI

Layer channels so color-blind players, audio-off players, and sighted players all receive the same information through different senses.

Animation tells

The primary channel. Windup poses should exaggerate direction and reach: a horizontal sweep pulls the torso sideways; a thrust coils the rear foot. Keep silhouettes readable at combat camera distance — small wrist flicks do not read on mobile screens. Loop idle-to-windup transitions should not blend so smoothly that the windup start frame is ambiguous; a one-frame pose hold or anticipation squash helps.

VFX and material cues

Weapon trails, emissive glow on charging limbs, ground cracks, and particle charge effects reinforce timing. Use consistent color language: orange glow for fire, cyan for frost, red for unblockable — and never reuse the same color for benign and lethal effects. Screen-edge vignettes for off-screen boss attacks are controversial; prefer a directional arrow or a brief camera nudge toward the threat.

Audio stings

Distinct SFX per attack family: grunt + whoosh for light, roar + rumble for heavy, metallic scrape for grab attempts. Pitch and reverb can signal range. Audio telegraphs help when the attacker is off-screen — but provide a visual backup for deaf and hard-of-hearing players (subtitle captions with attack names are underrated).

Ground AoE markers

Circles, cones, and lines painted on the floor are the standard for MMO raids, action RPGs, and moba skill shots. Best practices:

• Fill versus outline: outline during windup, solid fill in the last 200 ms before impact — or progressive fill that “counts down” visually.
• Height and occlusion: decals should render on terrain, not float; raise slightly on uneven mesh to avoid z-fighting.
• Shape honesty: the damage volume must match the marker within a few pixels; players learn geometry once and trust it forever.
• Follow versus static: chasing markers need lower tick rates smoothed visually; static markers can appear instantly at target point.

Attack phases: windup, active, recovery

Telegraphing maps directly onto the three-phase attack structure used in fighting games and action titles:

Windup (startup)

Frames before hit detection activates. This is where telegraphs live. Longer windups signal higher damage or wider range. Document windup length per move in data tables alongside damage and hitbox size — designers tune fairness in spreadsheets, not only in animation curves.

Active

Hitboxes enabled. Telegraphing ends here; players who failed to react now take damage or must block/parry. Multi-hit active windows need per-hit tells or clearly separated visual beats so players know which swing in a combo is lethal.

Recovery

Vulnerable frames after the attack. Generous recovery rewards players who correctly read the windup and punish the attacker. Bosses often use long recovery on whiffed heavies to create player counter windows — the telegraph's payoff.

See frame data for how to author and display these phases; pairing numeric frames with animation tells keeps combat debuggable.

Boss pattern design and attack vocabulary

Bosses need a limited vocabulary of attacks, each with a unique tell, composed into phases that escalate:

• Tier 1 basics: fast jab (short tell), blockable slash (medium tell).
• Tier 2 threats: unblockable slam (long tell + ground ring), gap-closer leap (audio + shadow).
• Tier 3 phase shifts: at 70% HP, add a delayed AoE nova with double windup — teach once, repeat with variation.

Introduce one new pattern per phase; reuse earlier patterns with faster recovery or combined sequences. “Telegraph debt” accumulates when you add attacks without tutorial encounters — use training dummies, story NPCs, or a first boss that only uses two tells.

Feints and mix-ups (advanced)

A feint shares the early windup of a heavy but cancels into a light. Only add feints after base patterns are learned; the feint must diverge before the player must commit to dodge. Delayed active frames (animation holds at the top of a swing) punish panic rolls — use sparingly and only on patterns with an unmistakable initial tell.

Player attacks need telegraphs too

PvE telegraphing is one-sided if player heavies connect instantly. Enemies (and PvP opponents) need tells on player windups for fairness:

• Enemy AI reacts to player animation state, not button press — gives human opponents time to respond in PvP.
• Player charged attacks show glow intensity scaling with charge level.
• Multiplayer hit validation uses windup timestamps so lag does not erase tells.

In PvP, extreme tell reduction defines fighting-game subgenres; in co-op PvE, generous enemy tells and moderate player tells keep the power fantasy without hiding information.

Harbor Ruins frost knight refactor (worked example)

Before refactor, the frost knight used one blend tree for all melee attacks; only damage and hitbox radius differed in data. After:

1. Three distinct windup poses: overhead (both hands raised), horizontal (torso coil), thrust (rear foot back).
2. Ground rings: overhead spawns a 4 m circle; horizontal a 120° cone decal; thrust uses a narrow line with no floor marker.
3. Audio: ice-crack SFX at windup start; impact boom on active frame.
4. Timing budget: overhead 36f windup / 8f active / 28f recovery at 60 FPS; thrust 14f / 6f / 18f.
5. Phase 2 addition: at 50% HP, overhead leaves a frost puddle — new tell (ground mist) introduced in a cutscene beat before first use.

Telemetry: average deaths per attempt dropped from 4.1 to 2.3; “unfair boss” survey tags fell 62%. Players who died still retry — they blame timing, not opacity.

Technique decision table

Genre patterns

Accessibility and difficulty options

• Extended telegraph mode: +20–40% windup duration or slower ground fill.
• High-contrast markers: thicker outlines, patterns beyond color alone.
• Attack name captions: subtitle-style callouts on boss patterns.
• Reduce screen shake: shake during windup obscures tells.
• Audio visualization: directional icons for off-screen windup sounds.

Accessibility options should extend information, not remove challenge entirely — unless a separate Story mode explicitly promises reduced combat demand.

Common pitfalls

• Same windup, different speed — players cannot learn timing.
• Marker smaller than hitbox — destroys trust permanently.
• Telegraph shorter than human reaction budget — feels input-ignored.
• Camera zoom during windup — hides the pose you need to read.
• Too many simultaneous floor effects — visual noise hides real threats.
• Off-screen instant grabs — no tell possible; add warning arrow or clamp range.
• Feints before base patterns learned — reads as random.
• Inconsistent color language — red means fire in one fight, physical in another.

Implementation checklist

• Define windup / active / recovery frame counts per attack in data.
• Author unique startup poses or VFX per attack family.
• Match ground decals to collision volumes; verify on slopes and stairs.
• Assign distinct audio stings; add caption strings for accessibility.
• Document reaction budget per attack tier (ms from tell start to active).
• Playtest at combat camera distance on min-spec resolution.
• Introduce boss patterns one at a time per phase; log first-death cause.
• Wire enemy AI to react to player windup states in PvE/PvP.
• Ship extended-telegraph and high-contrast toggles where feasible.
• Telemetry: track deaths per attack ID, dodge success rate, “unfair” reports.

Key takeaways

• Telegraphing is information design — fairness comes from readable tells, not weak enemies.
• Layer visual, audio, and UI channels so no single sense is required.
• Windup frames are the teachable moment; active frames are the test.
• Unique tells per attack beat faster RNG pattern selection.
• Ground markers must lie honestly about shape and timing.
• Recovery frames reward players who read windups correctly.

Related reading

• Game frame data explained — startup, active, and recovery frames in combat
• Game melee combat systems explained — hit detection, poise, and weapon arcs
• Game parry and block systems explained — counterplay after reading a tell
• Game boss fight design explained — phase pacing and pattern vocabulary