pokemon/nuzlocke-tracker
1
1
Fork 0
Code Issues Pull Requests 10 Actions Packages Projects Releases Wiki Activity
387 Commits 12 Branches 0 Tags
d23e24b826c8803128b2c8e37c658294043287ed
Commit Graph
7 Commits
Author SHA1 Message Date
TheFuryaandClaude Opus 4.6 3412d6c6fd Add naming scheme support for genlockes with lineage-aware suggestions (#20)
CI / backend-lint (push) Successful in 8s
Details
CI / frontend-lint (push) Successful in 33s
Details 
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>

Reviewed-on: TheFurya/nuzlocke-tracker#20
Co-authored-by: Julian Tabel <juliantabel.jt@gmail.com>
Co-committed-by: Julian Tabel <juliantabel.jt@gmail.com>
 2026-02-14 10:00:36 +01:00
TheFurya b55a82117e fix format in backend
CI / backend-lint (pull_request) Successful in 8s
Details
CI / frontend-lint (pull_request) Successful in 30s
Details
2026-02-11 21:58:46 +01:00
TheFuryaandClaude Opus 4.6 2ac6c23577 Add name suggestion engine with API endpoint and tests 
Expand services/naming.py with suggest_names() that picks random words
from a category while excluding nicknames already used in the run. Add
GET /runs/{run_id}/name-suggestions?count=10 endpoint that reads the
run's naming_scheme and returns filtered suggestions. Includes 12 unit
tests covering selection, exclusion, exhaustion, and cross-category
independence.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
 2026-02-11 21:45:04 +01:00
TheFuryaandClaude Opus 4.6 e324559476 Add naming scheme selection to run configuration 
Add a nullable naming_scheme column to NuzlockeRun so users can pick a
themed word category for nickname suggestions. Includes Alembic migration,
updated Pydantic schemas, a GET /runs/naming-categories endpoint backed by
a cached dictionary loader, and frontend dropdowns in both the NewRun
creation flow and the RunDashboard for mid-run changes.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
 2026-02-11 21:36:50 +01:00
Julian TabelandClaude Opus 4.6 c5910ec75c Add genlocke transfer UI with transfer selection modal and backend support 
When advancing to the next genlocke leg, users can now select surviving
Pokemon to transfer. Transferred Pokemon are bred down to their base
evolutionary form and appear as level-1 egg encounters in the next leg.
A GenlockeTransfer record links source and target encounters for lineage tracking.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
 2026-02-09 11:20:49 +01:00
Julian TabelandClaude Opus 4.6 48b56f9360 Implement Retire HoF (Gauntlet) rule enforcement for genlockes 
When retireHoF is enabled, surviving HoF Pokemon and their evolutionary
families are retired at leg advancement and treated as duplicates in all
subsequent legs — both in the encounter modal and bulk randomize.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
 2026-02-09 10:05:03 +01:00
Julian Tabel 6ee53a0533 Initial setup of frontend and backend 2026-02-04 17:13:58 +01:00