[Vatsal2005]

What and why

Locomotion now uses the exported animation tables: idle-to-walk, walk-to-run and run-start bridges lead into the movement loops, with reverse bridges on stopping or slowing. Moving loops switch at contact frames 00/04, as defined by the contact/down/passing/up rows in boards.json. Idle's feet stay planted. Playback is stepped at 12fps, retaining slower authored idle/ladder timing and short anticipation/impact holds. A random idle variant starts after five seconds still. F2 exposes clip and frame names for inspection.

Issue

Closes #31

Stack

• [16/16] feat: block frontal hits with the chair guard #149 [16/16] feat: block frontal hits with the chair guard
• [15/16] feat: add up attacks and pogo slams #146 [15/16] feat: add up attacks and pogo slams
• [14/16] feat: patrol and charge with autonomous rovers #145 [14/16] feat: patrol and charge with autonomous rovers
• [13/16] feat: save and refill at coffee machines #144 [13/16] feat: save and refill at coffee machines
• [12/16] feat: add alternating chair sweeps and contact hits #137 [12/16] feat: add alternating chair sweeps and contact hits
• [11/16] feat: add health damage and checkpoint respawn #135 [11/16] feat: add health damage and checkpoint respawn
• [10/16] feat: switch locomotion through authored bridge clips #132 [10/16] feat: switch locomotion through authored bridge clips ← this PR
• [9/16] feat: follow the hero with directional camera lead #131 [9/16] feat: follow the hero with directional camera lead
• [8/16] feat: add one-way decks and ladder climbing #126 [8/16] feat: add one-way decks and ladder climbing
• [7/16] feat: follow ground slopes and slide downhill #125 [7/16] feat: follow ground slopes and slide downhill
• [6/16] feat: add variable jumps and landing poses #123 [6/16] feat: add variable jumps and landing poses
• [5/16] feat: add weighted walking and running #122 [5/16] feat: add weighted walking and running
• [4/16] feat: load authored collision with a debug overlay #120 [4/16] feat: load authored collision with a debug overlay
• [3/16] feat: load exported stages and sprite atlases #116 [3/16] feat: load exported stages and sprite atlases
• [2/16] ci: check the game with node 22 on pull requests #111 [2/16] ci: check the game with node 22 on pull requests
• [1/4] chore(shared): scaffold the phaser game runtime #94 [1/16] chore(shared): scaffold the phaser game runtime — merged

Base: feature/32-camera-follow. Human merges bottom up; retarget the next PR to main and merge origin/main into every open branch, never rebase.

Acceptance criteria

• Idle/walk/run use authored bridges; moving loops change only on contact poses
• Stepped playback and anticipation/impact holds, without sprite scaling or blending
• Random idle variant after five seconds still

Verification

• Node 22: npm run typecheck, npm test (88 tests), npm run build; includes main integration at e8577ab
• py -3.13 scripts/check_docs.py — 616 files
• git diff --cached --check
• Tests use real exported tables; verify exact contact transitions, reverse bridges, run-start, stepped timing, anticipation hold, idle delay, air/climb interruption and placeholder fallback completion
• Browser: visible walk-run bridge and run loop, jump/fall/landing, 96px held rise, and check-tablet idle variant; feet remain anchored, no console errors
• Local GIF recordings and original timestamped browser frames; captures sample the rendered game, while unit tests check every 12fps state transition
• Vercel preview: GitHub states Vatsal2005 needs project access on Vercel to create deployments. A project owner must grant access; local checks pass.

Screenshots

Local evidence, shown in chat: ignored tmp/verification/31-walk-run.gif, 31-walk-run-jump.gif, 31-frames.json, 31-garden-frames.json and their original PNG frames. GitHub's browser is signed out, so uploading through that UI is unavailable.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
wincs	Error		Oct 24, 2026 12:31am UTC

[vercel]

@Vatsal2005 must be a member of the arudaev's projects team on Vercel to deploy.
- Click here to add @Vatsal2005 to the team.
- If you initiated this build, request access.
- If you're already a member of the arudaev's projects team, make sure that your Vercel account is connected to your GitHub account.

Learn more about collaboration on Vercel and other options here.