From dd277889fd6e43bbde49401a5b637a4cc713dbd0 Mon Sep 17 00:00:00 2001 From: Julian Tabel Date: Sun, 8 Feb 2026 21:56:07 +0100 Subject: [PATCH] Refine egg encounter logging bean Co-Authored-By: Claude Opus 4.6 --- ...counter-less-locations-for-egg-hatching.md | 25 +++++++++++-------- 1 file changed, 15 insertions(+), 10 deletions(-) diff --git a/.beans/nuzlocke-tracker-xa5k--display-encounter-less-locations-for-egg-hatching.md b/.beans/nuzlocke-tracker-xa5k--display-encounter-less-locations-for-egg-hatching.md index 9b01d07..0d84a85 100644 --- a/.beans/nuzlocke-tracker-xa5k--display-encounter-less-locations-for-egg-hatching.md +++ b/.beans/nuzlocke-tracker-xa5k--display-encounter-less-locations-for-egg-hatching.md @@ -1,20 +1,25 @@ --- # nuzlocke-tracker-xa5k -title: Display encounter-less locations for egg hatching -status: draft +title: Add egg encounter logging +status: todo type: feature +priority: normal created_at: 2026-02-08T14:49:50Z -updated_at: 2026-02-08T14:49:50Z +updated_at: 2026-02-08T20:55:33Z --- -Some routes/locations don't have wild encounters but are still relevant for gameplay — particularly for hatching eggs. Currently these locations are hidden or not useful in the run view since they have no encounters to log. +Allow players to log egg hatches at any location, similar to how shiny encounters work. A "Log Egg" button (next to "Log Shiny") opens a modal that shows all locations — including those without wild encounters — so the player can record where an egg hatched. -Add support for displaying locations that have no encounters in the run view, so players can track egg hatches or other location-based events there. +Egg encounters should: +- Bypass route-locking (same pattern as shiny clause / shed evolution) +- Be available at all locations, including those that have no wild encounter data +- Use a dedicated modal similar to ShinyEncounterModal +- Otherwise behave like normal caught encounters (appear in team, can evolve, can die, etc.) ## Checklist -- [ ] Determine how encounter-less routes should appear in the run view (e.g. different visual treatment, no encounter status dot) -- [ ] Update route filtering logic to include routes without encounters when relevant -- [ ] Add ability to log an egg hatch at a location (new encounter type or dedicated UI) -- [ ] Consider whether these locations need an admin-side flag (e.g. `show_without_encounters`) or if all routes should always be visible -- [ ] Allow a wildcard Pokemon on all routes for cases where the player hatches a Pokemon there or encounter data is incorrect \ No newline at end of file +- [ ] Data: Seed locations without wild encounters into the routes table via PokeAPI (so they appear in the route list) +- [ ] Backend: Bypass route-lock for egg encounters (extend `skip_route_lock` with an egg origin) +- [ ] Frontend: Add "Log Egg" button to the run encounters page header (next to "Log Shiny") +- [ ] Frontend: Create `EggEncounterModal` — similar to `ShinyEncounterModal` but shows all routes (including encounter-less ones) and uses `origin: "egg"` +- [ ] Frontend: Ensure egg encounters display normally in team view and route list \ No newline at end of file