Julian Tabel
4fb6d43305
Allows each sub-zone within a route group to have its own independent encounter when the Pinwheel Clause rule is enabled (default on), instead of the entire group sharing a single encounter. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
809 B
809 B
title, status, type, priority, created_at, updated_at
| title | status | type | priority | created_at | updated_at |
|---|---|---|---|---|---|
| Implement Pinwheel Clause support | completed | feature | normal | 2026-02-07T19:18:34Z | 2026-02-07T19:21:45Z |
Add pinwheel_zone column to routes, pinwheelClause toggle to NuzlockeRules, zone-aware encounter locking on frontend and backend.
Checklist
- Alembic migration for pinwheel_zone column
- SQLAlchemy model update
- Pydantic schema updates
- Route list API helper update
- Encounter creation API zone-aware sibling check
- Seed loader update
- Seed data for Pinwheel Forest zones
- NuzlockeRules per-run toggle
- Frontend types (game.ts, admin.ts)
- Admin route form pinwheelZone input
- Encounter page zone-aware locking, counts, and filtering
- getZoneEncounters helper