Files
nuzlocke-tracker/.beans/nuzlocke-tracker-knnc--add-staticlegendary-clause-rule.md
Julian Tabel e25d1cf24c
All checks were successful
CI / backend-lint (push) Successful in 9s
CI / actions-lint (push) Successful in 15s
CI / frontend-lint (push) Successful in 21s
Remove unused nuzlocke rules, reorganize into core and playstyle
Remove firstEncounterOnly, permadeath, nicknameRequired, and
postGameCompletion from the rules system — they are either implicit
(it's a nuzlocke tracker) or not enforced. Move levelCaps to core
(it's displayed in the sticky bar). Create a new "playstyle" category
for hardcoreMode and setModeOnly — informational rules useful for
stats but not enforced by the tracker. Remove the completion category
entirely. Add sub-task beans for the rules overhaul epic.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-20 21:20:23 +01:00

2.0 KiB

title, status, type, priority, created_at, updated_at, parent
title status type priority created_at updated_at parent
Add static/legendary clause rule todo feature normal 2026-02-20T19:56:27Z 2026-02-20T20:02:07Z nuzlocke-tracker-49xj

Control whether static/legendary encounters count against the area's encounter limit.

Design Decisions

Scope: This rule covers overworld Pokemon that are always available (legendaries, Snorlax blocking the road, Sudowoodo, Voltorb in the power plant, etc.). These are distinct from gifts (given by NPCs) which are covered by giftClause (sij8).

Encounter method: The existing encounter method list (walk, surf, gift, fossil, etc.) doesn't have a "static" method. Add static as a new encounter method in the seed data and METHOD_CONFIG. Static encounters are one-time overworld Pokemon the player walks up to and battles.

Rule behavior: staticClause: boolean (default: false). When enabled, encounters with method static bypass the route-lock check (same pattern as shinyClause and giftClause). This means static Pokemon are "free" and don't consume the area's encounter.

No legendary ban: Rather than banning legendaries outright, the community standard is to let the player choose. The tracker just needs to support logging static encounters correctly. Players who want to ban legendaries simply don't catch them.

Interaction with giftClause: These are separate rules. giftClause covers NPC gifts (method: gift). staticClause covers overworld statics (method: static). A player can enable both, one, or neither.

Checklist

  • Add static encounter method to seed data and METHOD_CONFIG / METHOD_ORDER
  • Add staticClause to NuzlockeRules interface and DEFAULT_RULES (default: false)
  • Add RuleDefinition entry under 'core' category
  • When enabled, encounters with method static bypass route-lock check in backend (add to skip_route_lock condition alongside shiny/egg/shed/transfer)
  • Update encounter creation frontend to show static as a selectable method where appropriate