Skip to content

Community funded. No paid power. Never pay-to-win.

Our promise
AshRun
About the Pokédex

Where our Pokémon information comes from

Locations and evolution requirements come from AshRun’s installed ATMons files. Our guides explain what those rules mean when you play.

Last verified 2026-10-16 · ATMons 1.3.0 · Minecraft 1.21.1 · NeoForge 21.1.249

Which version does this guide cover?

This snapshot covers ATMons 1.3.0 on AshRun, checked on . Other servers may change spawns, progression or encounter rules. Look for an AshRun-specific label before applying a custom route elsewhere.

The updates and sources page lists the pack and content versions. Source files are checked at a particular date; the website is not a live map of Pokémon currently near you.

How to read a Pokémon page

  1. Start with “How to get.” It identifies a supported wild, evolution, fossil, raid or special-encounter route.
  2. Check the conditions. Biome names are only part of the answer. Time, dimension, weather, height and other restrictions can matter.
  3. Check the catching rules. The catching guide explains party order and regional Pika Star progression.
  4. Follow the links. A biome links to other Pokémon found there; evolution links lead to the previous or next Pokémon and the requirements.

The index contains 1,027 species records, including 1,025 National Pokédex entries and 2 pack-defined additions. A record is not a promise that the Pokémon has a wild spawn. Missing acquisition evidence is marked rather than replaced with a guess.

Our methodology: what we check

The data combines installed Cobblemon and ATMons mods, enabled raid datapacks, the pack’s KubeJS overrides, AshRun’s legendary quests, special encounter mods and biome definitions. Capture restrictions are reviewed separately because a spawn file cannot tell you whether a ball will be accepted.

The October 2026 correction accounts for spawn pools disabled by the pack, replacement spawn rules and shared spawn conditions. This matters most for special Pokémon: a mod can include a spawn that ATMons deliberately turns off.

  • 3,017 grouped wild and fishing location records.
  • 1,050 raid definitions.
  • 89 legendary quest entries and 24 structure encounters.

Why some routes have a warning

Mods often name groups such as “forest biomes” instead of individual biomes. We resolve those groups against the installed pack and show usable biome names where possible. An unresolved rule is not treated as proof that a Pokémon can spawn anywhere.

Some encounters are created by code or rituals instead of ordinary spawn files. Their quest or structure instructions remain separate from the natural-spawn list. Technical records are available in expandable sections when you need to investigate a mismatch.

What the numbers mean

Spawn weight is relative, not a percentage. The other eligible Pokémon and the game’s spawn checks affect an encounter. Likewise, a species’ base catch rate and a ball’s multiplier are inputs to catching, not a guaranteed success chance. Neither gives a reliable waiting time.

Use PokéNav to compare the guide with conditions at your actual location. We do not publish player Pokémon, inventories, claims or private world coordinates.

Help us correct a page

Report a mismatch with the Pokémon name and form, page URL, pack version, and the relevant in-game message or missing condition. That gives us something specific to check against the source. You do not need to share your base coordinates or account details.

Public index and attribution

The public search index is available for browsing. The underlying Pokémon names, game data and artwork belong to their respective owners. Publishing this guide does not grant ownership of those assets.

Continue with locations, evolutions, types, or legendary routes.

PRIVACY CONTROLS

Analytics settings

Optional analytics use first-party cookies to recognize this browser for up to 180 days and group activity into 30-minute visits. Event-level data is deleted after 90 days.

Complete privacy and analytics notice