Add naming scheme support for genlockes with lineage-aware suggestions #20

Merged
TheFurya merged 2 commits from feature/genlocke-naming-scheme into develop 2026-02-14 10:00:38 +01:00
Owner

Genlockes can now select a naming scheme at creation time, which is
automatically applied to every leg's run. When catching a pokemon whose
evolution family appeared in a previous leg, the system suggests the
original nickname with a roman numeral suffix (e.g., "Heracles II").

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

Genlockes can now select a naming scheme at creation time, which is automatically applied to every leg's run. When catching a pokemon whose evolution family appeared in a previous leg, the system suggests the original nickname with a roman numeral suffix (e.g., "Heracles II"). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
TheFurya added 1 commit 2026-02-14 09:58:48 +01:00
Add naming scheme support for genlockes with lineage-aware suggestions
Some checks failed
CI / backend-lint (pull_request) Failing after 8s
CI / frontend-lint (pull_request) Successful in 31s
57023fc52a
Genlockes can now select a naming scheme at creation time, which is
automatically applied to every leg's run. When catching a pokemon whose
evolution family appeared in a previous leg, the system suggests the
original nickname with a roman numeral suffix (e.g., "Heracles II").

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
TheFurya added 1 commit 2026-02-14 09:59:43 +01:00
Fix python formatting and linting.
All checks were successful
CI / backend-lint (pull_request) Successful in 8s
CI / frontend-lint (pull_request) Successful in 29s
0728d55f06
TheFurya merged commit 3412d6c6fd into develop 2026-02-14 10:00:38 +01:00
TheFurya deleted branch feature/genlocke-naming-scheme 2026-02-14 10:00:38 +01:00
Sign in to join this conversation.
No Reviewers
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: pokemon/nuzlocke-tracker#20