From be6c8e75bede037cb14250783f4a61cccf6a8748 Mon Sep 17 00:00:00 2001 From: Julian Tabel Date: Sun, 8 Feb 2026 13:17:43 +0100 Subject: [PATCH] Add genlocke tracking epic bean Co-Authored-By: Claude Opus 4.6 --- ...uzlocke-tracker-25mh--genlocke-tracking.md | 36 +++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 .beans/nuzlocke-tracker-25mh--genlocke-tracking.md diff --git a/.beans/nuzlocke-tracker-25mh--genlocke-tracking.md b/.beans/nuzlocke-tracker-25mh--genlocke-tracking.md new file mode 100644 index 0000000..d2da309 --- /dev/null +++ b/.beans/nuzlocke-tracker-25mh--genlocke-tracking.md @@ -0,0 +1,36 @@ +--- +# nuzlocke-tracker-25mh +title: Genlocke tracking +status: draft +type: epic +priority: normal +created_at: 2026-02-08T12:17:19Z +updated_at: 2026-02-08T12:17:19Z +--- + +Track a **genlocke** — a series of linked nuzlocke runs, typically one per generation or region. The player picks one game per generation (e.g. FireRed instead of Red) and surviving Pokemon carry over between legs. + +## Context + +A genlocke connects multiple nuzlocke runs into a single overarching challenge. Key aspects: + +- **Leg ordering**: Each run is a "leg" in a defined sequence (usually Gen 1 → Gen 2 → ... or by region). The user chooses which game represents each leg. +- **Pokemon transfer**: Pokemon that survive one leg can be bred/traded into the next leg as eggs (typically hatch at level 1). This is the core mechanic that ties legs together. +- **Cumulative graveyard**: Deaths across all legs are tracked together — a Pokemon that dies in Gen 3 stays dead for the whole genlocke. +- **Overall progress**: Dashboard showing completion status across all legs, total deaths, surviving lineage, etc. +- **Flexible structure**: Some players do one game per generation, others do one per region, or even custom orderings. The system should be flexible. + +## Possible data model + +- A `Genlocke` entity that groups multiple `NuzlockeRun` records in a defined order (leg number) +- Each run gets a `genlocke_id` + `leg_order` to place it in the sequence +- A `GenlockeTransfer` or similar to track which Pokemon carry over between legs (linking an encounter from leg N to a starter/gift encounter in leg N+1) + +## Potential child features + +- Create/manage a genlocke (pick games for each leg, reorder) +- Genlocke dashboard (overall progress, cumulative stats) +- Transfer UI: after completing a leg, select surviving Pokemon to carry forward +- Lineage tracking: show a Pokemon's journey across multiple legs +- Genlocke-aware graveyard (deaths across all legs) +- Templates for common genlocke formats ("one per gen", "one per region") \ No newline at end of file