diff --git a/.beans/nuzlocke-tracker-3el1--run-progression-dividers-main-story-endgame.md b/.beans/nuzlocke-tracker-3el1--run-progression-dividers-main-story-endgame.md index 7bfe635..647ee24 100644 --- a/.beans/nuzlocke-tracker-3el1--run-progression-dividers-main-story-endgame.md +++ b/.beans/nuzlocke-tracker-3el1--run-progression-dividers-main-story-endgame.md @@ -1,10 +1,11 @@ --- # nuzlocke-tracker-3el1 title: Run progression dividers (main story / endgame) -status: draft +status: completed type: feature +priority: normal created_at: 2026-02-08T13:40:14Z -updated_at: 2026-02-08T13:40:14Z +updated_at: 2026-02-08T20:25:59Z --- Add support for dividing a run's boss battle progression into sections like "Main Story" and "Endgame" (e.g., post-Elite Four content). This helps players visually distinguish where the main campaign ends and optional/endgame content begins. diff --git a/.beans/nuzlocke-tracker-66hg--auto-select-boss-team-variant-based-on-starter-cho.md b/.beans/nuzlocke-tracker-66hg--auto-select-boss-team-variant-based-on-starter-cho.md index ef6f2c0..c266abb 100644 --- a/.beans/nuzlocke-tracker-66hg--auto-select-boss-team-variant-based-on-starter-cho.md +++ b/.beans/nuzlocke-tracker-66hg--auto-select-boss-team-variant-based-on-starter-cho.md @@ -1,11 +1,11 @@ --- # nuzlocke-tracker-66hg title: Auto-select boss team variant based on starter choice -status: in-progress +status: completed type: feature priority: normal created_at: 2026-02-08T20:21:40Z -updated_at: 2026-02-08T20:22:47Z +updated_at: 2026-02-08T20:34:35Z --- When a run's starter Pokemon is known, automatically match it against boss battle condition labels (e.g., "Chose Bulbasaur") and pre-select the matching variant instead of showing the pill selector. diff --git a/.beans/nuzlocke-tracker-igl3--name-generation.md b/.beans/nuzlocke-tracker-igl3--name-generation.md index 315c8a5..3662c09 100644 --- a/.beans/nuzlocke-tracker-igl3--name-generation.md +++ b/.beans/nuzlocke-tracker-igl3--name-generation.md @@ -2,10 +2,10 @@ # nuzlocke-tracker-igl3 title: Name Generation status: draft -type: feature +type: epic priority: normal created_at: 2026-02-05T13:45:15Z -updated_at: 2026-02-05T13:46:30Z +updated_at: 2026-02-08T20:33:36Z --- For nuzlockes I want to implement name generation. The user should be able to provide a naming scheme or a list of nick names that can then be selected when a new encounter is registered. diff --git a/.beans/nuzlocke-tracker-jain--handle-nincada-split-evolution-ninjask-shedinja.md b/.beans/nuzlocke-tracker-jain--handle-nincada-split-evolution-ninjask-shedinja.md new file mode 100644 index 0000000..f910666 --- /dev/null +++ b/.beans/nuzlocke-tracker-jain--handle-nincada-split-evolution-ninjask-shedinja.md @@ -0,0 +1,24 @@ +--- +# nuzlocke-tracker-jain +title: Handle Nincada split evolution (Ninjask + Shedinja) +status: draft +type: feature +created_at: 2026-02-08T19:38:55Z +updated_at: 2026-02-08T19:38:55Z +--- + +Nincada is a special case in Pokemon: when it evolves at level 20, the player gets both Ninjask (the normal evolution) AND Shedinja (if there's an empty party slot and a spare Poke Ball). This creates a unique situation for Nuzlocke tracking since one encounter effectively produces two usable Pokemon. + +## Problem + +The current evolution system assumes 1:1 evolution (one Pokemon evolves into one Pokemon). The Nincada line breaks this — a single caught Nincada can yield two team members. Nuzlocke rules vary on how to handle this: +- Some players treat Shedinja as a free bonus (allowed to use both) +- Some players must choose one and box/release the other +- Some rulesets ban Shedinja entirely since it wasn't "encountered" + +## Considerations + +- The evolution data already has a `shed` trigger type for the Nincada → Shedinja evolution, separate from the `level-up` trigger for Nincada → Ninjask +- This may need a rule option in run settings (e.g., "Allow Shedinja from Nincada evolution") +- The encounter tracking may need to support creating a second encounter entry from the same route when a Nincada evolves +- Consider whether this is purely a rules/UI concern or if the data model needs changes \ No newline at end of file diff --git a/.beans/nuzlocke-tracker-x8ol--starter-dependent-boss-battle-teams.md b/.beans/nuzlocke-tracker-x8ol--starter-dependent-boss-battle-teams.md index 9fe6fd3..8e3ac9b 100644 --- a/.beans/nuzlocke-tracker-x8ol--starter-dependent-boss-battle-teams.md +++ b/.beans/nuzlocke-tracker-x8ol--starter-dependent-boss-battle-teams.md @@ -1,11 +1,11 @@ --- # nuzlocke-tracker-x8ol title: Conditional boss battle teams -status: in-progress +status: completed type: feature priority: normal created_at: 2026-02-08T13:23:00Z -updated_at: 2026-02-08T19:34:27Z +updated_at: 2026-02-08T20:21:50Z --- Some boss battles have teams that vary based on conditions in the player's run. The most common case is starter choice (e.g., Blue's team in Gen 1 depends on whether you picked Bulbasaur, Charmander, or Squirtle), but other conditions exist too — in Pokemon Yellow, the rival's team changes based on the outcomes of two early-game fights, not the starter. This feature adds support for defining multiple team variants per boss battle, each associated with a named condition.