Add end-of-run condition rule bean, mark genlocke wizard completed
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -1,11 +1,11 @@
|
|||||||
---
|
---
|
||||||
# nuzlocke-tracker-kz5g
|
# nuzlocke-tracker-kz5g
|
||||||
title: Genlocke creation wizard
|
title: Genlocke creation wizard
|
||||||
status: in-progress
|
status: completed
|
||||||
type: feature
|
type: feature
|
||||||
priority: normal
|
priority: normal
|
||||||
created_at: 2026-02-09T07:42:10Z
|
created_at: 2026-02-09T07:42:10Z
|
||||||
updated_at: 2026-02-09T08:10:10Z
|
updated_at: 2026-02-09T08:23:53Z
|
||||||
parent: nuzlocke-tracker-25mh
|
parent: nuzlocke-tracker-25mh
|
||||||
blocking:
|
blocking:
|
||||||
- nuzlocke-tracker-x4p6
|
- nuzlocke-tracker-x4p6
|
||||||
|
|||||||
@@ -0,0 +1,21 @@
|
|||||||
|
---
|
||||||
|
# nuzlocke-tracker-tyvc
|
||||||
|
title: Add end-of-run condition rule
|
||||||
|
status: todo
|
||||||
|
type: feature
|
||||||
|
created_at: 2026-02-09T08:35:39Z
|
||||||
|
updated_at: 2026-02-09T08:35:39Z
|
||||||
|
---
|
||||||
|
|
||||||
|
Add a new nuzlocke rule: **End of Run Condition**. This is a toggle/switch that lets the player decide when a run is considered complete:
|
||||||
|
|
||||||
|
- **Main Story** (default) — The run ends after beating the Champion / completing the main storyline
|
||||||
|
- **Post Game** — The run continues into the post-game content (Battle Frontier, rematches, etc.)
|
||||||
|
|
||||||
|
This affects when the player is expected to mark a run as "completed" and could influence level caps and boss tracking in the future.
|
||||||
|
|
||||||
|
## Checklist
|
||||||
|
- [ ] Add `postGameCompletion` (boolean, default false) to the `NuzlockeRules` TypeScript interface and `DEFAULT_RULES`
|
||||||
|
- [ ] Add a rule definition to `RULE_DEFINITIONS` in `frontend/src/types/rules.ts`
|
||||||
|
- [ ] Verify the rule appears in the `RulesConfiguration` component (should work automatically via RULE_DEFINITIONS)
|
||||||
|
- [ ] Verify the rule is stored correctly via the existing run/genlocke creation flows (JSONB, no backend schema change needed)
|
||||||
Reference in New Issue
Block a user