Wiki first
Character pages, move inputs, mechanics, supported strategy, counterplay and drills. Sources stay one click away.
STORM GENERATIONS · PRODUCT & IMPLEMENTATION ROADMAP
A competitive wiki that helps players make better decisions.
Build readable character guides, tested counterplay and repeatable practice. Connect them to match review and community results as reliable data becomes available.
Planning artifact · proposed features are not live capabilities.
Choose a character → understand an action → study the matchup → practice → review a match.
Measured combat
Validate health units, simulation timing, actor identity and conditions before publishing damage or frame values.
Connected competition
Reviewed results first. Trace-driven analytics, player development and defensible rankings follow their evidence gates.
Learn from LuckyStats
The public site connects players, events, ratings and analyzed sets. Apply that connected navigation to Generations, with a dedicated wiki for practical learning. Some advanced analytics were login-gated and were not assessed.
Implementation started: The local player wiki now has character navigation, move pages, search and practice setup. Open the player wiki → · Completed work and remaining checks
Ten milestones, each with a release gate
M0 Publication foundation
Dependencies: Start here · Planned
- Preserve source exports and hashes
- Define publication schema and evidence statuses
- Create stable identity adapters and URL migration map
- Test null, zero, not-applicable and build isolation
Release gate: Rebuild retains all source records; null/zero/not-applicable are tested; current links still work
M1 Player-first wiki shell
Dependencies: M0 · Planned
- Build player homepage and typed global search
- Create character directory and move-page template
- Add glossary, input notation and practice entry points
- Test mobile, keyboard navigation and source discovery
Release gate: Find character → move → evidence without internal IDs; no unmeasured claim is promoted
M2 Roster and action reconciliation
Dependencies: M0 · Planned
- Reconcile selection screen with internal groups
- Map variants, forms and unresolved aliases
- Inventory basic actions absent from command text
- Publish a coverage denominator with explicit gaps
Release gate: Every observed selection has an identity record; unresolved entries remain separate
M3 Validated combat pilot
Dependencies: M2 · Planned
- Calibrate fresh-run health fields and actor mapping
- Establish authoritative units and simulation clock
- Record guard, spacing, resources and build settings
- Repeat representative attacks and independently corroborate results
Release gate: Representative damage and timing claims pass independent checks and retain raw evidence
M4 Character and counterplay release
Dependencies: M1, M3 · Planned
- Populate supported character game plans
- Publish validated move facts with conditions
- Write interaction and counterplay cards
- Create reproducible drills including failure cases
Release gate: Each released guide has useful supported advice, known limits and reproducible practice
M5 Community evidence workflow
Dependencies: M1 · Planned
- Define contribution templates and evidence requirements
- Build review and dispute states
- Preserve revision history and rollback
- Test portable submissions and reviewed exports
Release gate: A contributor can submit evidence; a reviewer can accept/reject; rollback preserves history
M6 Match-results foundation
Dependencies: M0 · Planned
- Define player, event, set and game identities
- Import a small reviewed results corpus
- Handle duplicates, forfeits and corrections
- Reconcile every pilot result against its source
Release gate: Results reconcile against their sources; game/set/forfeit distinctions are preserved
M7 Trace and match review
Dependencies: M3 · Planned
- Validate recorder feasibility and overhead
- Version trace schema and parser
- Render real event timelines with missing-data states
- Align video evidence and label playback fidelity
Release gate: A real match can be inspected reproducibly; missing data and capture overhead are reported
M8 Competitive analytics
Dependencies: M6, M7 · Planned
- Implement eligibility and event definitions
- Recompute statistics from retained events
- Add comparable-cohort filters and uncertainty
- Validate player review and matchup summaries
Release gate: Every statistic can be recomputed from exported eligible events; uncertainty and sample counts visible
M9 Rankings and community launch
Dependencies: M5, M6, M8 · Planned
- Evaluate rating method on held-out results
- Publish rating and editorial tier policies
- Test moderation, backups and restore
- Launch only supported competition features
Release gate: Rating policy reviewed; unsupported rankings suppressed; backup/restore and moderation tested
The first release should solve four player tasks
- Find the right character and form without knowing an internal ID.
- Understand an action’s input, supported use and known limitations.
- Find a useful practice setup and record attempts, including failures.
- Inspect the build, conditions and evidence behind a claim.
The current 48,762 raw attributes are a research resource. They are not 48,762 verified combat facts. Real move damage and frame timings still need validation.