twentytwentytwenty

The Arc Follows the Swing

Oct 5–6, 2026 · animation, VFX · Strangedeep

Before

The arc animation was moving clockwise while the actual character animation was moving counterclockwise. It's an obvious mistake that was overlooked by the agent. Just always have to keep an eye out for little disjointed things like this in AI Dev.

Cleave. Left: the arc turns clockwise against the sword's swing. Right: the hero turns so the slash sweeps the struck cells, and the hit lands as the sword passes.

The prompts

  1. we need to make sure animations like sweep and cleave follow the movement of animation. if the swing is going counter clockwise, the animation should also

  2. ok, well, now the arc shader doesn't actually follow the attack area

  3. i also think the character animation needs to orient itself correctly to perform the attack, let's not assume the character must be facing forward for these attacks. orient the character so the character has best alignment with the animation itself.

  4. one handed cleave is still a little wrong, the character focuses too much on the target within the arc, the character should perform the arc more than focus on the target, the character should still reposition to perform the arc.

  5. i do think the character needs to resume facing in his starting position after an arc style attack

Four passes

  1. The arc copies the body's measured swing: same turn direction, start and end angles and timing, peaking on the contact frame.
  2. The arc spans the cells the ability hits, and its leading edge follows the weapon. Each hit lands as the weapon passes its cell.
  3. The area decides which way the fighter faces, not the target. The fighter turns to perform the arc even if the cells are empty.
  4. After the swing, the fighter eases back to the facing it started with. Enemies follow the same rules.
Sweeping Kick: the arc fills the part of the ring the foot does not reach, then the fighter turns back.

What AI did, what I decided

AI

  • Measured each swing from the game's own animation clips.
  • Rebuilt the arc in four passes, one per correction.
  • Wrote the checks and recorded the before and after clips.

Adam

I did actually watch the GIFs, i always watch the gifs. The animations still need work but they are good enough for this stage of dev

Stack

RoleModel or toolReasoningTime
Lead: plans, writes briefs, reviewsClaude Code, Opus 5.5xhigh, then highwhole session
Pass 1Opus 5.5 subagentxhigh11.8 h (3.1 h active)
Passes 2–4Opus 5.5 subagents (sd-fixer, sd-builder)medium, high16–39 min each
ClipsSonnet 5.5 subagent (sd-runner)low22 min
AnimationMixamo clips (Adobe), retargeted at true size
GameGodot 4.7.2 .NET, C#, GDShader
Checks and footageNode.js verify scripts, Godot movie maker, ffmpeg

Pass 1 used 31.2M weighted tokens. Passes 2 to 4 together used about 16M.

Proof

verify:ability-vfx (swing)
918 checks passed
Arc's leading edge within 9.0° of the weapon in game (3.4° mean)
Broken versions caught, e.g. a reversed arc
Checks say the numbers hold. Whether it looks right is Adam's eye.

What's next

The animations still need work. The grappling hook got its own rebuild the same week; that's the next entry.