Repository navigation
[9/16] feat: follow the hero with directional camera lead - #131
Conversation
Ease toward a speed-based horizontal lead and the player feet vertically, while clamping to the complete chunk grid. Retain precise smoothing state but render the camera on whole pixels. Reuse grid bounds in the stage renderer and preserve the accepted export parallax values. Keep manual panning available in development inspection mode.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
@Vatsal2005 must be a member of the arudaev's projects team on Vercel to deploy. Learn more about collaboration on Vercel and other options here. |
Codex's player uses F2 for its debug readout (#131); the dev unlock for the pocket computer moves out of its way.
|
Next, after the animation fix – lane A's story work (#50, #51, #52, #54, #56, #58) needs two hooks from lane B, as contracts in
Plus |
Carry human-merged lane A changes upward without rewriting published commits.
Carry human-merged lane A changes upward without rewriting published commits.
Carry human-merged lane A changes upward without rewriting published commits.
What and why
The camera now follows the hero with up to 120px of directional look-ahead and smooth vertical follow. It clamps to the full four-direction chunk grid, retains fractional smoothing internally and sends only integer coordinates to Phaser. The renderer keeps the stage manifest's authored parallax factors and list order. Development inspection mode retains manual panning for annotation review.
Issue
Closes #32
Refs #29
Stack
Base:
feature/30-platforms-and-ladders. Human merges bottom up; retarget the next PR to main and merge origin/main into every open branch, never rebase.Acceptance criteria
Verification
npm run typecheck,npm test(81 tests),npm run build; includes main integration at e8577abpy -3.13 scripts/check_docs.py— 614 filesgit diff --cached --checkContract note
docs/13 and #110 require the exported list order and scroll values. The current Creek export uses distance 0.2, near rails 1.1 and foliage 1.15, whereas docs/04 gives general layer roles from 0.1 to 1.2. This change follows the actual export; changing those art values belongs in lane A's config.
Screenshots
Captured in ignored
tmp/verification/32-slope.png,32-seam.png,32-clean-end.pngand shown in chat. The full clean traversal also confirms both authored chunk boundaries in the running game.