89f46e2b12
The current retireHoF logic retires all alive Pokemon instead of just the HoF team. Add beans to track the fix: a general HoF team selection feature for all runs, and a follow-up task to integrate it into genlocke retirement logic. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
40 lines
2.5 KiB
Markdown
40 lines
2.5 KiB
Markdown
---
|
|
# nuzlocke-tracker-8w9s
|
|
title: Gauntlet rule option for genlockes
|
|
status: completed
|
|
type: feature
|
|
priority: normal
|
|
created_at: 2026-02-08T19:15:43Z
|
|
updated_at: 2026-02-09T09:05:12Z
|
|
parent: 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
|
|
- [x] Add a `retireHoF` boolean (or equivalent) to the genlocke rules JSONB schema
|
|
- [x] On leg completion with Retire HoF enabled: resolve the full evolutionary families of all surviving HoF Pokemon
|
|
- [x] Store the cumulative retired families list (could be a JSONB field on the Genlocke, or derived from completed legs)
|
|
- [x] Implement `GET /api/v1/genlockes/{id}/retired-families` — return the list of retired evolutionary families with which leg they were retired in
|
|
- [x] 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
|
|
- [x] Ensure the creation wizard's genlocke rules step correctly toggles between Keep HoF and Retire HoF |