Combat and Unique Character Animations

Creating Combat and Unique Character Animations

Combat animations are the most labor-intensive part of the pipeline. Not because technically complex, but because requirements are vague until game prototype runs. "Make good sword strike" becomes five iterations when game designer finally sees how animation interacts with hitbox, hitlag, cancel window and combo system.

Combat Animation Structure as Game Asset

Combat strike in game consists of three phases: anticipation (wind-up), active (active phase with hitbox), recovery (animation exit). Animator must know each phase length in frames—not artistic decision, this is game design specification. Without it animation is beautiful but non-functional: hitbox activates before weapon visually reaches target, or player gets stuck in recovery unable to cancel attack.

In Unity these phases are managed through Animation Events. At needed frames events are placed: OnAttackStart, OnAttackEnd, OnHitboxEnable, OnHitboxDisable. Combat Controller script subscribes to these events and manages weapon colliders. This is standard scheme; without it hit detection either hangs on timers in C# breaking on animation change or on physics triggers causing false positives.

Cancel window is the moment when player can interrupt current attack and start next one. In Animator Controller this is implemented through Transition with condition canCancel == true, set through Animation Event at needed frame. If cancel window doesn't match gameplay feel—return to animator, not programmer.

Unique Animations: Motion Capture vs Hand-keyed

For unique animations (death, finishing move, cutscene) tool stack depends on budget and style. Motion Capture gives organicity extremely hard to reproduce manually—inertia, minor weight shifts, hand micromovement. Downside—raw mocap data requires retargeting and cleanup: jitter, joint artifacts, proportion mismatch with game character.

Hand-keyed animation in Maya or Blender is slower but gives full timing and spacing control. For stylized games with exaggerated movement—often preferable. Workflow: blockout by Bezier curves, then refinement with breakdown keys, final Euler Rotation fix for gimbal lock elimination.

Gimbal lock in Maya is common problem during rotations over 180°. Fixed by: switching Rotation Order to ZXY or XZY depending on main rotation direction. For wrists during pronation—mandatory, otherwise Euler curves flip.

Combo System and Animator Controller

Three-hit combo in Animator Controller is implemented differently. Cleanest variant—Sub-State Machine with sequential transitions: Attack1 → Attack2 → Attack3. Transition allowed only in cancel window through Animation Event + Trigger parameter NextAttack. After third strike—return to Idle or Run through Exit.

Alternative—Animation Layer with Override and own State Machine for attacks above locomotion layer. Convenient if attacks work while moving, but requires proper Avatar Mask: upper body only plus weapon, lower limbs continue locomotion.

Blend tree for attacks with weight interpolation used rarely—only for direction-dependent animations (left/right attack) where Blend Tree 2D lets interpolate between four strike directions.

Typical Combat Animation Errors

Animation without Export Root Transform. If strike contains forward lunge, Root Motion must be explicitly configured, otherwise character teleports to start on return to Idle.

Missing Additive Layer for hit reaction. Hit Reaction overlays above any state through Additive Layer—doesn't interrupt attack but gives visual response. Without this layer must make separate versions of each animation with reaction.

Ignoring Secondary Motion. Cape, hair, loose clothing elements—without secondary movement animation looks "wooden" regardless of main keyframing quality. In Unity this is Physics Bone through Animation Rigging or Spring Bone from VRM pipeline.

Process and Timeline

Work in Maya (primary) or Blender, FBX export with proper Take settings. Animation Events integration and transition setup in Animator Controller—part of work if specified in technical specification.

Cost formed after discussing animation count, combo system complexity and Secondary Motion requirements.