Files
nuzlocke-tracker/.beans/nuzlocke-tracker-glh8--gather-generation-metadata-games-regions.md
Julian Tabel 3a1aedda32 Refine genlocke epic with user flow, child features, and action items
Break down the genlocke tracking epic into 8 child beans with
checklists, dependency chains, and success criteria. Add CLAUDE.md
instruction for updating parent checklists on child completion.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-09 08:47:49 +01:00

2.2 KiB
Raw Blame History

title, status, type, priority, created_at, updated_at, parent, blocking
title status type priority created_at updated_at parent blocking
Gather generation metadata (games, regions) todo task normal 2026-02-08T19:20:49Z 2026-02-09T07:45:21Z nuzlocke-tracker-25mh
nuzlocke-tracker-kz5g

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 (19)
  • 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 generation and region fields, 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.json already exists or if this needs to be created from scratch

Checklist

  • Define the generation-to-region mapping (Gen 1 = Kanto, Gen 2 = Johto, ..., Gen 9 = Paldea)
  • Determine how to group games by region (use region field on existing Game model, or create a dedicated lookup)
  • Create a generations.json seed file (or equivalent) with: generation number, region name, region order, and which games belong to each region
  • Categorize each game as "original", "remake", or "enhanced" so presets can filter appropriately
  • Define which game is the "default" pick per region for the Normal Genlocke preset (e.g., FireRed for Kanto, HeartGold for Johto)
  • Add an API endpoint or extend the games endpoint to return games grouped by region with generation metadata
  • Verify all seeded games are correctly tagged with their region