Julian Tabel
fb0ad23c45
- nuzlocke-tracker-3el1: mark completed (run progression dividers) - nuzlocke-tracker-66hg: mark completed (auto-select boss variant) - nuzlocke-tracker-x8ol: mark completed (conditional boss teams) - nuzlocke-tracker-igl3: change type to epic - nuzlocke-tracker-jain: add new bean (Nincada split evolution) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
24 lines
1.4 KiB
Markdown
24 lines
1.4 KiB
Markdown
---
|
|
# 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 |