Add boss team match playstyle rule
When enabled, the sticky boss banner shows the next boss's team size as a hint for players who voluntarily match the boss's party count. Handles variant boss teams by using the auto-detected starter variant. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -1,33 +1,29 @@
|
||||
---
|
||||
# nuzlocke-tracker-fv7w
|
||||
title: Add team size limit rule
|
||||
status: todo
|
||||
title: Add boss team match rule
|
||||
status: in-progress
|
||||
type: feature
|
||||
priority: normal
|
||||
created_at: 2026-02-20T19:56:22Z
|
||||
updated_at: 2026-02-20T20:01:53Z
|
||||
updated_at: 2026-02-20T21:01:36Z
|
||||
parent: nuzlocke-tracker-49xj
|
||||
---
|
||||
|
||||
Cap the active party size with warnings when the limit is exceeded.
|
||||
When enabled, hint to the player that they should limit their active party to the same number of Pokemon as the next boss fight. This is a self-imposed difficulty rule — the tracker cannot enforce it since it doesn't track the active party, but it can surface the information.
|
||||
|
||||
## Design Decisions
|
||||
## Design
|
||||
|
||||
**Configurable limit:** Add `teamSizeLimit: number | null` to `NuzlockeRules`. `null` means no limit (disabled). Default Pokemon party size is 6, but variants like "trio-locke" use 3.
|
||||
**Rule:** Add `bossTeamMatch: boolean` to `NuzlockeRules` (default: `false`, category: `playstyle`).
|
||||
|
||||
**What counts:** "Active team" = encounters with status `caught` and not fainted. The tracker already tracks this — alive Pokemon are shown in the team section on RunEncounters.
|
||||
**Display:** When enabled and the sticky boss banner is shown, add a hint next to the boss name showing their team size, e.g. "Next: Brock (2 Pokemon — match their team)". This reuses the existing `nextBoss` and its `pokemon` array.
|
||||
|
||||
**No PC box tracking:** The tracker doesn't model a PC box. Excess catches beyond the team limit are still logged normally. The tracker just warns that the team is over capacity.
|
||||
**Variant bosses:** Some bosses have conditional teams (e.g. rival starter choice). Use the same logic as `BossTeamPreview`: count pokemon without a `conditionLabel` plus those matching the auto-detected variant (via `matchVariant`). Falls back to first variant if no match is detected.
|
||||
|
||||
**Enforcement:** Soft enforcement. Show a warning banner on the encounters page when alive count exceeds the limit. Highlight the count in the team section header. Don't block new catches.
|
||||
|
||||
**UI:** Add a numeric input to `RulesConfiguration` (shown when team size toggle is on, min 1, max 6). Display the limit in the sticky bar alongside level caps if enabled.
|
||||
**Scope:** Frontend-only. No backend or data model changes needed.
|
||||
|
||||
## Checklist
|
||||
|
||||
- [ ] Add `teamSizeLimit: number | null` to `NuzlockeRules` interface (default: `null`)
|
||||
- [ ] Add `RuleDefinition` entry under `'difficulty'` category
|
||||
- [ ] Add numeric input to `RulesConfiguration` (shown when enabled, min 1, max 6)
|
||||
- [ ] Show warning banner on RunEncounters when alive team count exceeds limit
|
||||
- [ ] Display team size limit in sticky bar alongside level caps
|
||||
- [ ] Show count in team section header (e.g., "Team (4/3)" in red when over)
|
||||
- [x] Add `bossTeamMatch: boolean` to `NuzlockeRules` interface and `DEFAULT_RULES` (default: false)
|
||||
- [x] Add `RuleDefinition` entry (category: `playstyle`)
|
||||
- [x] Show boss team size hint in the sticky level cap banner when the rule is enabled
|
||||
- [x] Handle variant boss teams (use auto-matched variant count when available)
|
||||
@@ -1,11 +1,11 @@
|
||||
---
|
||||
# nuzlocke-tracker-sij8
|
||||
title: Add gift clause rule
|
||||
status: in-progress
|
||||
status: completed
|
||||
type: feature
|
||||
priority: normal
|
||||
created_at: 2026-02-20T19:56:10Z
|
||||
updated_at: 2026-02-20T20:53:15Z
|
||||
updated_at: 2026-02-20T20:55:23Z
|
||||
parent: nuzlocke-tracker-49xj
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user