1.4 KiB
1.4 KiB
title, status, type, created_at, updated_at, parent
| title | status | type | created_at | updated_at | parent |
|---|---|---|---|---|---|
| Gather generation metadata (games, regions) | todo | task | 2026-02-08T19:20:49Z | 2026-02-08T19:20:49Z | nuzlocke-tracker-25mh |
Collect and store metadata about each Pokemon generation to support genlocke features. This data is needed so the app can present generation-aware options when setting up a genlocke (e.g. "pick one game per generation").
Data to gather per generation
- Generation number (1–9)
- Main region (e.g. Gen 1 → Kanto, Gen 2 → Johto, etc.)
- Games in the generation — including remakes and enhanced versions:
- Original titles (e.g. Red, Blue, Yellow)
- Remakes that belong to the generation's region (e.g. FireRed/LeafGreen are Gen 1 region but Gen 3 era)
- Consider whether remakes should be listed under their original generation (by region) or their release generation (by engine/dex) — genlocke players typically organize by region
Notes
- This could be stored as seed data (JSON) or as a database table
- The existing Game model already has
generationandregionfields, so some of this data may already be derivable from existing games in the DB - However, a dedicated generations reference would be useful for UI purposes (showing all generations even if not all games are seeded yet)
- Check if
backend/src/app/seeds/data/generations.jsonalready exists or if this needs to be created from scratch