· 5 min read
The attack starts before the hit
Startup, contact, and recovery form one readable action; animation, sound, and effects should tell the player what is coming before damage asks for an answer.
Take an enemy overhead swing that feels fair and shave a little time off the front. The damage is unchanged, the hitbox is unchanged, and the animation may still look better because it feels snappier. From the player's chair, though, you removed part of the interface. The missing frames were where the attack said what it was.
Give the enemy one job treated an enemy's role as something the player should be able to read. Keep the threat where you left it followed that readability outside the camera. The same problem exists in time. A threat can be perfectly visible and still become unreadable if its meaning arrives after the player needed to choose a response.
An attack is not the instant where damage happens. It starts earlier and ends later, and those quieter parts are doing gameplay work.
The hitbox is the middle of the move#
Capcom's official Street Fighter V seminar on attack composition splits an attack into startup, active frames, and recovery. Startup is the time before the attack can hit. Active frames are when its hitbox is live. Recovery is the period after that where the attacker cannot act normally yet. Fighting games name these pieces because a few frames can change which action wins, but the structure exists in a monster swing or a shooter melee attack too.
The useful part is that only one of those phases deals damage. Startup gives the opponent something to notice. Recovery gives them something to earn. If a move is dangerous immediately and then snaps straight back to safety, most of the decision has been compressed into the contact frame.
Announce
Pose, motion, sound, or VFX identifies the attack family before it can hurt the player.
Commit
The startup motion narrows what the attacker can still do and gives the player a response window.
Contact
The hitbox, projectile, or hazard becomes dangerous and cashes in the earlier warning.
Recover
Follow-through leaves an opening, returns the attacker toward neutral, or makes the cost of the action visible.
Capcom describes almost the same thing from the other side of the screen in its interview with the animation team for Monster Hunter Rise: Sunbreak. Monster animations begin from a gameplay design document, then temporary animations are tested and adjusted alongside game design and VFX. The animator interviewed says familiarity with a monster means recognizing most attacks from their startup animation and knowing when the monster will be open to a counterattack.
That workflow matters. The tell is not polish applied after the attack has already been balanced. The motion is part of how the balance becomes playable.
The tell can carry the rule#
Guerrilla describes enemy animation in Horizon Forbidden West in similarly practical terms. Its combat breakdown says classes and machines communicate their gameplay function through actions, posture, motion, and readable silhouettes. The team adjusts timing to create windows to strike, block, or run. Audio does parallel work: melee sounds build toward impact while ranged weapons have charge-up or projectile cues that can pull attention toward the most immediate threat.
A tell becomes especially important when similar attacks demand different answers. Santa Monica Studio's account of the Valkyries in God of War describes two ranged attacks that deliberately punish opposite defensive habits. One begins with the Valkyrie's arms held horizontally and is best blocked. The other begins with her arms raised vertically and must be dodged. The pose is not an animation flourish around the rule. It is where the rule becomes available to the player.
This suggests a better review question than “is the tell obvious enough?” Ask whether the tell distinguishes the decisions that actually differ. Two attacks can share color, size, and dramatic energy if the same response beats both. If one must be blocked and the other dodged, hiding that branch until the weapon is already moving at full speed asks for memorization of a failure rather than recognition of a choice.
Noise can still have a beginning#
Returnal is useful because it has no interest in keeping the screen quiet. Housemarque's article on creating its enemies describes bright emissive tentacles that telegraph incoming attacks and an “energy signature” carried from enemies into their projectiles. In a later VFX breakdown, the team says tentacle behavior could be forced into a particular motion while an enemy prepared an attack, with timings iterated together with designers.
The screen can therefore contain hundreds of projectiles without every attack becoming anonymous. Visual noise and readable timing are not opposites. The important thing is that the player can learn when an object changes from scenery or motion into a commitment they need to answer. In a crowded game that transition may be a glow, a sound, a pose, a trail, or several of them at once.
This also connects back to off-screen combat. A directional arrow can tell you where an attack is coming from; a charge sound can tell you when it is becoming dangerous. Position and timing are separate questions, and a good encounter often needs both answered before the impact frame.
Fast is not the same as hidden#
None of this requires every enemy to wind up like a stage actor. Capcom's frame-data lesson is explicit that shorter startup is generally stronger. Fast attacks are useful. They make spacing matter, punish slow decisions, and give a roster different tempos. A game can also ask players to predict rather than react once they understand the surrounding rules.
The problem begins when speed erases the information that makes the decision intelligible. If two attacks need different defenses, the distinguishing cue has to arrive before that defensive choice is effectively locked in. If an attack has tiny startup, its range, context, sound, posture, or previous state may need to carry more of the warning. If the player avoids it correctly, recovery can make the read matter by providing an opening instead of immediately starting another equally ambiguous attack.
I would review one troublesome attack frame by frame and mark four moments: when the player can first identify the attack family, when the attacker becomes committed, when contact becomes dangerous, and when the attacker is free again. Then play it at speed and listen with the picture hidden. If the important branch only becomes clear after the response had to begin, make the startup say more or make the possible answers less different.
The clockwork ship in the header stores its motion before it moves. A game attack does not need to show its machinery, but the player should be able to see some sign of the stored action before it is released. The hit is the loud part. The design started a few frames earlier.