FireRed Nuzlocke tracker for a Kanto run

A FireRed Nuzlocke becomes easier to manage when every area has one clear record. Log the first encounter that counts for your rules, then mark that route as resolved instead of trying to remember it later. The Kanto tracker is designed around route-by-route progress, so catches, boxed Pokémon and losses do not live in separate notes. Choose the Dupes settings in the run and keep any special static-encounter policy on a separate rule sheet rather than assuming a default.

The interactive Kanto map provides routes, locations and encounter information for the region. It is useful for checking where an unclaimed encounter opportunity belongs before entering a new area. The map is planning support, not a promise about what your first encounter will be. Your run log should record the actual result, including failed catches or clauses your rules allow, so the record reflects the playthrough rather than a hypothetical route plan.

FireRed runs often change quickly after a difficult trainer battle. Update the team and loss log when a Pokémon leaves the run, then use the remaining team for the next decision. Keeping fallen partners visible prevents accidental reuse and gives the run a clear history. The tracker does not calculate a safe battle outcome or prescribe a replacement. It gives the player a current team, a route record and the surrounding map data for informed planning.

The familiar Nuzlocke baseline is only a starting point. Before Route 1, decide how to treat starter Pokémon, gifts, duplicate Pokémon, shinies and accidental fainting. Set the supported Dupes, Shiny, nickname and level-cap options in the run. Keep starter, gift and accidental-fainting policies on a separate rule sheet and apply them consistently. This matters more than copying someone else’s format: a clear written rule lets a FireRed run stay fair after a surprise encounter or a difficult loss, and makes a restart or completion record understandable later.