3a1aedda32
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>
2.5 KiB
2.5 KiB
title, status, type, priority, created_at, updated_at, parent
| title | status | type | priority | created_at | updated_at | parent |
|---|---|---|---|---|---|---|
| Gauntlet rule option for genlockes | todo | feature | normal | 2026-02-08T19:15:43Z | 2026-02-09T07:46:32Z | nuzlocke-tracker-25mh |
Add the Retire HoF (aka Gauntlet) rule as a genlocke-specific rule option. When enabled, Pokemon that enter the Hall of Fame at the end of a leg are NOT transferred to the next game — instead, they and their entire evolutionary families are added to a cumulative dupe list for all subsequent legs.
Behavior
- Toggled as a genlocke-specific rule during genlocke creation (step 3 of the wizard)
- Mutually exclusive with "Keep HoF" — you pick one or the other
- When a leg is completed:
- Surviving HoF Pokemon are marked as "retired" rather than being available for transfer
- Their evolutionary families (full chain: e.g., Charmander/Charmeleon/Charizard) are added to a cumulative dupe list
- In subsequent legs, the duplicates clause treats these families as already caught/dead
- The cumulative dupe list grows with each completed leg, making later legs increasingly restrictive
- The genlocke overview page should display the cumulative retired/duped families
Dependencies
- Requires the genlocke creation wizard (to set the rule)
- Requires the leg progression system (to trigger retirement on leg completion)
- Should integrate with the existing duplicates clause enforcement in the encounter system
Notes
- This is a popular variant that increases difficulty by forcing entirely new Pokemon each generation
- The dupe list should be visible somewhere in the genlocke dashboard so the player knows which families are off-limits
Checklist
- Add a
retireHoFboolean (or equivalent) to the genlocke rules JSONB schema - On leg completion with Retire HoF enabled: resolve the full evolutionary families of all surviving HoF Pokemon
- Store the cumulative retired families list (could be a JSONB field on the Genlocke, or derived from completed legs)
- Implement
GET /api/v1/genlockes/{id}/retired-families— return the list of retired evolutionary families with which leg they were retired in - Integrate with the encounter system's duplicates clause: when logging an encounter in a genlocke leg, check the cumulative retired list and flag duplicates
- Build a "Retired Families" display on the genlocke overview page showing all off-limits Pokemon with their sprites
- Ensure the creation wizard's genlocke rules step correctly toggles between Keep HoF and Retire HoF