This wiki is built from public data shipped by the original game. Public availability makes the values inspectable, but it does not turn every field into a verified description of PokéBonk's survivor mechanics.
A reference is not a simulation
A Pokémon entry contains six base stats, types, abilities and evolution-family information. A move entry contains power, accuracy, category and other reference fields. Those values are helpful for lookup and comparison.
A survivor game can transform them. It can use different type multipliers, derive health from a formula, give a partner a custom passive or change how a move attacks. This site does not calculate in-run damage from the mainline type chart and present the result as a tested PokéBonk number.
That distinction is why pages say “base stats” and “reference effects.” The labels describe the evidence precisely rather than promising behaviour that has not been tested.
Why only Kanto?
The official homepage describes a game with the 151 Pokémon of Kanto. However, the public Pokémon and learning-table files each include 1,025 entries. Copying every record into a PokéBonk wiki would imply a scope the game's own introduction does not establish.
The first release therefore includes Pokémon IDs 1 through 151. Move coverage comes from the union of those entries' learning tables, which produces 381 referenced moves. The related regular and hidden abilities produce 114 ability references.
This is a transparent editorial scope, not proof that every included record can be selected, caught or obtained in each mode.
Abilities and evolution
Hidden abilities and canonical evolution triggers can exist in the source without being exposed as gameplay systems. A reference description mentioning a turn-based battle action can be another sign that it is upstream data.
Use family links to explore related Pokémon, and ability pages to read the shipped description. For actionable decisions about a run, check the current game interface and version.
The same applies to items. The item library contains 151 source records, not a verified loot table. It does not attach invented rarity, drop chance or acquisition routes to those records.
How we check sources
The synchronization script downloads the original JSON and English localization layer, normalizes names, and validates links between entries. The data manifest records capture time, source URLs and the checked build.
Release summaries point back to the original game's news panel. Map pages report the currently configured regions without filling gaps with older assumptions. The sources page records the limitations and image provenance, and the repository includes a reproducible data synchronization command.