maniator / maniator/verticopolis
[Feature]: [P3] Metro ridership economy (per-rider model; needs its own spec + party)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
From the people-tracking priority ruling (2026-07-15) in
_bmad-output/implementation-artifacts/backlog.md(later tier) and the metro v1.34.0 review defers.
Priority P3 | Status: idea (needs spec) | Epic: SimTower parity | Type: feature-request
Problem / motivation
Metro commuters are visual-and-routing only; no income, congestion, or census coupling changed when they shipped. The catalog's transit bonuses (+60 arrival capacity, congestion relief) stay statistical.
Proposed solution
A per-rider ridership model is a separate design question: spec it with a party before building. Check the 1994 original's metro economics first (parity source of truth).
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
Start with _bmad-output/implementation-artifacts/backlog.md and the metro v1.34.0 review references mentioned in the issue. Research the 1994 original's metro economics as the parity source of truth, then define the per-rider model with the requested party. Done means an agreed standalone specification, not implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100