Designing Action Combat
Principle
Combat quality comes from readable intent, responsive control, meaningful commitment, and clear feedback.
Define the contract
For each player action specify startup, active frames, recovery, movement allowance, cancel windows, stamina/resource cost, hitbox, damage/stagger, and audiovisual feedback.
For each enemy attack specify tell, wind-up, tracking rule, active window, recovery, safe response, and punish window.
Workflow
- Build a minimal duel before adding combo breadth.
- Tune input responsiveness and locomotion around combat distances.
- Ensure telegraphs are distinguishable by silhouette and timing, not only color.
- Align hitboxes to animation intent rather than sprite/mesh bounds.
- Use hit-stop, camera impulse, sound, VFX, and animation reaction proportionally to impact.
- Add cancel rules deliberately; never let accidental animation interruption define the system.
- Test edge cases: repeated input, direction change, simultaneous hits, wall proximity, low frame rate, off-camera enemies.
Avoid
- attacks that visually connect before hit registration;
- identical timing for every enemy;
- excessive particle effects hiding danger;
- long uninterruptible animations without corresponding payoff;
- camera shake strong enough to damage targeting readability.
1---2name: designing-action-combat3description: Use when creating or tuning real-time game combat involving attacks, hit reactions, dodge or guard behavior, enemy telegraphs, combos, animation timing, or moment-to-moment combat readability.4---56# Designing Action Combat78## Principle9Combat quality comes from readable intent, responsive control, meaningful commitment, and clear feedback.1011## Define the contract12For each player action specify startup, active frames, recovery, movement allowance, cancel windows, stamina/resource cost, hitbox, damage/stagger, and audiovisual feedback.1314For each enemy attack specify tell, wind-up, tracking rule, active window, recovery, safe response, and punish window.1516## Workflow171. Build a minimal duel before adding combo breadth.182. Tune input responsiveness and locomotion around combat distances.193. Ensure telegraphs are distinguishable by silhouette and timing, not only color.204. Align hitboxes to animation intent rather than sprite/mesh bounds.215. Use hit-stop, camera impulse, sound, VFX, and animation reaction proportionally to impact.226. Add cancel rules deliberately; never let accidental animation interruption define the system.237. Test edge cases: repeated input, direction change, simultaneous hits, wall proximity, low frame rate, off-camera enemies.2425## Avoid26- attacks that visually connect before hit registration;27- identical timing for every enemy;28- excessive particle effects hiding danger;29- long uninterruptible animations without corresponding payoff;30- camera shake strong enough to damage targeting readability.
jhonatan-oliveiradev