REFERENCE SCOPE

Beta 0.6.3 · secondary reference snapshot

A completed condition is a milestone

The retained League reference describes a sequence: satisfy the challenge, encounter the target, then capture it and confirm its League entry. The tracker keeps those stages separate. Only mark the final stage when the original game confirms ownership.

Read the condition like a specification

Look for words that change how a counter works: total, during rain, different Pokémon, or in one run. For example, the recorded Gastly condition is a single-run reaction target. Adding several separate runs does not satisfy that wording.

For a condition with two requirements, use separate checkboxes. This prevents a familiar half-completed objective from feeling finished when the other half has not been checked.

Keep notes that survive a break

Before ending a planning session, note which objective you intend to pursue next and which evidence is still missing. Unknown is a valid state. It is better than guessing that a capture counted or treating a temporary companion as confirmed collection progress.

The tracker is a local checklist, not a connection to your account. Use its export when moving your plan between browsers. A planning export cannot restore Pokémon or progress inside the original game.

Quick questions

Why does my unlocked counter not match the tracker?

The tracker includes eight selected targets and only records your manual choices. It is not a complete Pokédex or an account sync.

What if I already chose this starter?

The first choice is already available. Mark its completed stages to match your actual ownership; the two-run route is for an unchosen starter.

Sources & scope

How we use sources ↗

Game rules can change. Check your current in-game description when a detail differs. Numerical references are a dated snapshot, not a claim of current balance or a completed playtest.

PUT IT INTO PRACTICE

A little planning goes a long way.

Open your toolkit