Nuzlocke
Track a Pokémon Nuzlocke run end to end, every encounter, your living team, and the graveyard, all in one place.
A Nuzlocke run lives and dies by its own rules: one encounter per route, and a Pokémon that faints is dead for good. That makes the whole thing a bookkeeping problem as much as a game. Halfway through a run you're tracking which routes you've already caught on, who's actually in your party right now, who died and where, which badges you've earned, and what the next gym leader is going to throw at you. Doing all of that on a sticky note or a phone notepad falls apart fast, and forgetting that one route is already spent is exactly the kind of slip that ends a run.
Nuzlocke is the tool I wanted while playing: a single screen that holds the entire state of a run and stays honest about it. You log an encounter as it happens, the catch joins your active team, and a faint moves it straight to the graveyard so the count is never off. Everything is structured around the rules instead of fighting them, so the app does the remembering and you get to focus on the next decision.
How it works
- Encounters by route: log the one Pokémon you're allowed to catch on each route, so it's always clear which routes are still open and which are already burned.
- Living team and graveyard: catches flow into your active party, and a faint sends a Pokémon to the graveyard for good, keeping a permanent record of who you lost and when.
- Badges and boss prep: track gym badges as you earn them and stage what's coming, so you can plan a team before walking into the next major fight instead of guessing.
- Search and move autocomplete: find any Pokémon fast, fill in moves without typos, and read type badges at a glance while you're building or reworking the team.
- Run analysis and themes: step back and review how the run is going across encounters, deaths, and badges, with a shiny-encounter log and a theme picker to set the mood.
Stack
React · TypeScript · Vite. The whole thing runs client-side and ships as a static build, so a run is fast to open and there's no server sitting between you and your own data.