Skip to content

fix: bind DRIVE passenger shots and replay rewards to runs - #202

Draft
BrandDead wants to merge 1 commit into
main-tL2525from
fix/201-driveby-participant
Draft

BrandDead wants to merge 1 commit into
main-tL2525from
fix/201-driveby-participant

Conversation

@BrandDead

Copy link
Copy Markdown
Owner

Scope — partial #201, not a launch gate closure

Pass a snapshot of the confirmed car crew into the existing legacy DRIVE mini-game. Revalidate the active driver and unique shooter passengers at mission start and at firing time; a shooter-trained driver never appears as an in-car firing member. A selected passenger can be switched explicitly without silently changing to another member when a roster entry becomes unavailable. Tag player bullets with the selected passenger; lethal gang-target hits tally against that bullet's shooter ID. Parent reward booking credits only the actually credited passenger, preserving current experience and kill totals. Each run carries an ID so a retry/play-again books once, and a late callback from the preceding run cannot book the next run; post-shot member status changes do not erase prior credit.

The passenger control bar is positioned below the existing tactical HUD rail and has tested phone-sized hit targets. No new combat engine, world-result writer, backend or database change.

Validation

  • Regression-first: shooter driver/passenger, injured/stale passenger, duplicate and forged seat positions, explicit switching, selected-killer XP, duplicate completion, retry/replay and post-shot roster changes.
  • Full Node 24 preflight on reviewed source: 93 files; 1,041 passing, 4 intentional skips, TypeScript/lint, asset audit, package validation; production build. Backend: 95 passing (local, unchanged backend). Exact GitHub CI remains required on the pushed head.
  • Actual demo player path at 375×812, 390×844, 1440×900: age gate → DRIVE → dealer driver + shooter passenger → mission start. Verified the single current shooter is the passenger, not the driver, no page errors, and no shooter-bar/status-rail overlap. This is local/demo only.

Still open on #201 (do not close issue)

Manus owns integration, reviews any new assistant PR independently, and will keep #201 open. No production data, deployment, or user likeness files are in this PR.

@vercel

vercel Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated
slide Ready Ready Preview Oct 1, 2026 3:58pm UTC

Request Review

This branch was successfully deployed

1 active deployment
Preview — b798d6e7 Deployed Oct 1, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant