Use this page to identify a Pokémon before deciding what to do with it. A familiar name can belong to a public species entry, a selectable League partner, an evolution family, or a cosmetic appearance. Those categories overlap without being interchangeable. The filters help you narrow the list while preserving those distinctions, so a search result does not silently become an unlock recommendation or a combat ranking.
Find the right entry without losing context
Search accepts a name, the source identifier, or a Pokédex number. A short name fragment is useful when spelling is uncertain; the type filter then removes unrelated results. Type filtering includes a Pokémon when either of its listed types matches. The collection filter can isolate direct League entries, legendary species, mythical species, or Pokémon with a previous form in the raw database. These are independent questions, so combining filters deliberately is more useful than assuming every special species is a playable starting partner.
Sort by Pokédex number when checking family neighbors, by name when looking up a remembered entry, or by public base stat total when examining the reference dataset. The last option is a research convenience rather than a strength recommendation. If a filtered view is empty, shorten the search or remove a type condition. Reset returns to the complete current collection. Copy link preserves the selection and build identifier, making it possible to discuss the exact reference view with another player.
League listing and account unlocks are different
The League filter currently recognizes 79 direct partner entries from the same versioned snapshot. “Listed League partner” means the species identifier appears in that collection; it does not read your game save, complete a challenge, or verify that your account can select the partner. An evolved species can still appear in the public Pokédex without being an independent League starting choice. Treat the label as a route to further information, not as an account status indicator.
For the actual task you must complete, follow the League unlock checklist. Its conditions answer a different question from public species metadata. If you are deciding what to unlock next, compare those requirements with the tier methodology and available votes and your own play style. Neither a large base stat total nor a rare classification is evidence that a particular challenge will be easy or that a partner will outperform your existing options.
Read evolution levels as raw reference fields
A card may show a previous form, a raw level, a trigger, or an evolution item. For example, Ivysaur has a source evolution-level field of 16. That value is displayed because it is present in the public dataset, not because the wiki has validated the corresponding transition in a live run. Runtime evolution extraction is marked unextracted; its recorded reason is that branching has not been validated. A missing level is likewise not proof that a species cannot evolve.
Family membership is useful for finding related names, but the card’s family sequence is an index order rather than a prescribed evolution route. Branching families can contain alternatives that should not be read as a single chain. Before spending a scarce resource on an expected transformation, verify the current in-game offer and mode. The wiki deliberately keeps raw fields visible with this qualification instead of replacing uncertain behavior with the familiar rules from another Pokémon game.
Public stats help identification, not DPS prediction
The expanded card includes HP, Attack, Defense, Special Attack, Special Defense and Speed from the public species record, plus their total. These fields make it easier to distinguish related forms and understand which source record you are viewing. They are not a complete description of PokéBonk’s runtime starting stats. Damage also depends on the implemented move, its upgrades, source-group modifiers, type handling and the situation in which an attack lands. Adding the displayed base stats cannot recover those missing relationships.
This distinction matters especially when comparing starters. A player might value reliable movement, an accessible move pattern or an easier opening more than a large public stat. The starter comparison is organized around that decision rather than treating the Pokédex sort order as a recommendation. Use the card as supporting reference, then inspect the partner’s actual kit and passive before choosing a plan. This also avoids confusing a high reference Speed value with a verified attacks-per-second measurement.
Use types as a starting point for matchup research
Type chips reflect the species types stored in the snapshot. They support searching and identification, but they do not themselves calculate an attack’s effectiveness. Matchups depend on the attacking move type and the defender’s types, while same-type bonuses concern a different relationship between the attacker and its move. These distinctions are easy to blur when a Pokémon has multiple types or when the build uses a broad mix of moves.
Open the runtime type-effectiveness reference when the question is how a matchup is calculated. That tool remaps public matchup values through the extracted runtime rules before combining defender types and applying bounds. Cosmetic research-frame requirements are not a combat synergy threshold. Likewise, finding several same-type Pokémon in this directory does not establish a team-wide bonus. If you want a type-related item, the held-item database shows the extracted descriptions and static modifiers so you can inspect the effect separately.
Special species and appearances need their own evidence
Legendary and mythical filters use the corresponding public classification flags. Those labels are helpful for locating familiar species, but they do not promise a particular encounter rate, an unlock shortcut or a unique runtime mechanic. For a focused explanation of special partner availability, read the Mewtwo and legendary reference. It keeps unlock evidence and species identity in separate roles rather than deriving game requirements from a main-series label.
Appearance is another independent layer. A card portrait identifies the species and is not a preview of every unlocked skin, shiny variant or mastery look. The shiny and wardrobe guide explains the available evidence and the limits of probability claims. A visual difference seen in a screenshot should therefore lead you to the cosmetic information, not to an assumption that the Pokémon’s public stats or type have changed. This directory does not estimate drop odds from artwork or collection rarity.
Connect a species search to a practical run plan
Once you have identified the entry, decide which missing fact actually affects your next action. If the question concerns where a run takes place, use the map and region reference, which keeps regional information with its own source context. A type appearing on this page is not evidence that the Pokémon spawns on every region associated with that type. If the question concerns selection, a listed League partner card offers a direct planner link.
Carry a narrow question into that next tool. You might be checking whether an item supports the move type you intend to use, whether a partner is a direct unlock, or whether a family relationship explains an unfamiliar form name. That is more reliable than trying to infer an entire build from a database card. The directory is designed to make those follow-up steps faster while leaving uncertain encounter, evolution and combat behavior explicitly unresolved.
Versioned references and reproducible searches
This page uses public data from version 0.8.34, build mvlr7rzv. The build stamp identifies the snapshot behind every filter result. Saved filters live in your browser when storage is available, while a copied link carries its own build identifier. If an old link belongs to another snapshot, the tool asks you to reset rather than silently presenting old selections as current data. Corrupt local state also falls back to a usable default view.
When reporting a discrepancy, keep the species name, the field you checked and the game build together. A screenshot of a later patch may reflect a legitimate change rather than an error in the older source record. The sources and extraction notes explain how public files are collected and which mechanics remain incomplete. That audit trail is especially important for evolution claims, because a correct raw field can still be the wrong evidence for a runtime rule.