[Vatsal2005]

What and why

Ground contacts now interpolate the authored polylines instead of treating each segment as flat. Walkable slopes through 40 degrees keep feet attached across uphill, crest, downhill and flat joins; steeper contacts accelerate downhill and allow jumping away. Slide visuals use the supplied stepped fall poses without scaling the sprite.

Issue

Closes #29

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
• [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 ← this PR
• [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/28-controlled-jump. Human merges bottom up; retarget the next PR to main and merge origin/main into every open branch, never rebase.

Acceptance criteria

• Walks continuous authored slopes through 40 degrees
• Steeper contacts slide downhill and permit jumping away
• Continuous contact over slope joins, with no staircase boxes

Verification

• Node 22: npm run typecheck, npm test (71 tests), npm run build; includes main integration at e8577ab
• py -3.13 scripts/check_docs.py
• git diff --cached --check
• Tests traverse uphill/crest/downhill/flat joins at walk and run speeds, exact 40-degree boundary, slide acceleration in both directions, jumping away and every real Creek walk segment
• Browser regression: walk/run and grounded feet in the Garden, F2 reports slope; no console errors
• Route-wide browser slope traversal follows [M1-S4] Drop through one-way platforms and climb ladders #30, which supplies the ladders needed to reach the slope
• Physical gamepad and Vercel preview: Vatsal2005 needs access to the Vercel project

Seam contact

The actual first seam rises from y=461 to y=456. A six-pixel endpoint tolerance applies only when a grounded body crosses a polyline endpoint. Real-file tests cover both seams, states, directions and movement speeds; falling bodies never snap upward.

Screenshots

F2 overlay evidence is in #120 and movement screenshots in #122. The current authored Creek data has no brown slide segments; steep-slide behavior is exercised by geometry fixtures in the tests. Full animation switching follows in #31.

[vercel]

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

Project	Deployment	Actions	Updated
wincs	Error		Oct 24, 2026 12:29am 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.