maniator / maniator/verticopolis
[Feature]: [P3] Benched traffic-chip softening blend max(avg, 0.7*peak), playtest-gated
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Imported from the engineering backlog (
_bmad-output/implementation-artifacts/backlog.md, storytraffic-soften-blend).
Priority P3 (do-first order) | Status: open work (see row) | Type: design-decision | Recorded: 2026-07-15
Problem / motivation
Gated: fires only if playtesting shows the straight-peak chip too twitchy on a single hot floor. From spec-traffic-indicator-fix (benched by the numbers party: blend reserved as documented modern softening). Input seam is updateTraffic in src/main.ts. Record kept so the bench trigger is not lost; may never fire.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read _bmad-output/implementation-artifacts/backlog.md for the traffic-soften-blend story, then inspect updateTraffic in src/main.ts and the existing traffic-chip behavior. Use playtesting to determine whether the straight-peak chip is too twitchy on a single hot floor; only if that trigger is confirmed, implement the documented max(avg, 0.7*peak) softening and verify the chip behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100