This Evomon rarity guide explains how to label rarity carefully: use confirmed, reported, partial, or unknown until exact spawn odds and availability are supported by evidence.
Rarity is useful, but fragile
Players want to know which creatures are common, rare, legendary, or event-limited. That makes an Evomon rarity guide useful. The problem is that rarity claims can become wrong quickly if they are copied from old updates or single sightings.
This Evomon rarity guide uses confidence labels instead of fake odds. If a rare creature is observed once, the page can say reported. If it is observed repeatedly with a clear source, the confidence improves. If exact percentages are unknown, the site should not invent them.
Rarity labels
| Label | Use it when |
|---|---|
| Confirmed rarity | A reliable source or repeated testing supports the label. |
| Reported rarity | The label appears in a source, but has not been verified by the site. |
| Partial rarity | Some evidence exists, but conditions are unclear. |
| Unknown rarity | The creature exists, but the rarity is not proven. |
The Evomon rarity guide should help players decide what to investigate next, not guarantee impossible captures. A cautious label is more useful than a confident mistake.
Spawn odds and route claims
Exact odds require many observations or official data. A player seeing one rare creature does not prove a percentage. A video showing one route does not prove that the route is always best. The Evomon rarity guide holds those claims until the evidence is stronger.
How rarity connects to the database
Every database row should include a rarity confidence note. If the row has no proof, mark it unknown. If a future update changes availability, move old rarity notes into the update log. That keeps the Evomon rarity guide useful after patches.
Rarity FAQ
Does the Evomon rarity guide include exact odds?
No. Exact odds need repeatable testing or a reliable source before they are published.
What should a rare Evomon entry include?
A rare entry should include the creature name, source, location confidence, variant status, and checked date.