Cluster 1: evolution methods
Level, item, trade, friendship, time, move, location, and form-based triggers should be documented as separate methods.
Why evolution routes get misread
Simple three-stage lines are easy to remember, but many Pokemon use special triggers: evolution stones, trades, friendship, time of day, known moves, gender, weather, location, regional forms, or game-specific conditions. A reference that only lists "base evolves into next stage" loses the most useful part of the rule.
Start with the local method guide, stone and item notes, or Eevee family guide, then record the exact evolution requirement.
Minimum fields for evolution notes
| Field | Why it matters | Example |
|---|---|---|
| Base species | The starting point of the route. | Eevee |
| Evolution target | The exact next species or final species being reached. | Vaporeon |
| Trigger | The action or condition needed for the evolution. | Water Stone |
| Context | Game, generation, form, time, location, or other caveat. | Item evolution |
| Reference URL | Keeps the route verifiable and easy to revisit. | Local route note plus canonical source |
Cluster 2: stones, items, and branches
Item evolutions and branching families like Eevee need especially clear notes because the same base species can lead to many outcomes.
FAQ for Pokemon evolution research
Is level always enough to describe an evolution?
No. Many Pokemon evolve through items, trades, friendship, moves, forms, time, or location.
Why record generation or game context?
Some methods and availability details change across games. Context prevents a correct note in one game from becoming misleading in another.
Should evolution pages link back to type pages?
Yes. Evolution can change typing, which affects matchup, collection, and guide-writing notes.