1.5 KiB
1.5 KiB
title, status, type, created_at, updated_at
| title | status | type | created_at | updated_at |
|---|---|---|---|---|
| Pinwheel Clause support | draft | feature | 2026-02-07T13:39:46Z | 2026-02-07T13:39:46Z |
Some Nuzlocke games use the Pinwheel Clause (also called the Dupes Clause variant for multi-encounter areas). In certain areas, players are allowed multiple encounters instead of the standard one-per-route rule.
Context
The Pinwheel Clause is named after Pinwheel Forest in Black/White, where the inner and outer areas are considered separate encounter zones. Other examples include Safari Zones, large caves with distinct floors, and similar multi-zone areas.
Currently the tracker enforces strict one-encounter-per-route. This feature would allow toggling the Pinwheel Clause for a run, which would let players mark multiple encounters as valid on designated routes.
Design considerations
- Should this be a per-run toggle (enabled/disabled when creating a run)?
- Which areas qualify? Could be data-driven (flag on route data) or user-controlled (manually mark routes as multi-encounter)
- How does this interact with the UI? Maybe routes with the clause show multiple encounter slots
- Consider also supporting other common clauses (Dupes Clause, Shiny Clause) as a general "house rules" system
Checklist
- Decide on clause toggle mechanism (per-run setting vs per-route flag vs both)
- Design data model changes (run settings, route flags)
- Implement backend support
- Update frontend encounter UI to handle multi-encounter routes
- Add clause toggle to run creation/settings