The Evomon data checklist defines the minimum fields needed before this site treats a creature, code, map, item, evolution, or dungeon note as verified.
Minimum verification fields
The Evomon data checklist exists because database sites can accidentally turn guesses into facts. A page may look complete because it has tables, but the useful part is the evidence behind each row.
Use this Evomon data checklist before publishing any new database entry. If a field is missing, label it unknown instead of filling it with a guess.
Entry checklist
| Data type | Minimum fields |
|---|---|
| Creature | Name, source, type if visible, role note, checked date. |
| Code | Exact text, status, reward if verified, source, checked date. |
| Map note | Area name, route note, source, repeatability, checked date. |
| Evolution | Before form, after form, method, material if any, proof level. |
| Item | Name, source, use, confidence, checked date. |
| Dungeon | Name, access note, observed enemies, reward confidence, date. |
The Evomon data checklist should be used before adding new pages to the wiki navigation. It is better to publish one reliable table than five impressive-looking guesses.
Confidence labels
Use confirmed, reported, partial, unknown, or held. Confirmed means the site has strong evidence. Reported means a source says it but the site has not checked it. Held means the topic is popular but unsafe to publish as fact.
Why players should care
Players use guide pages while making decisions. Bad data wastes time. The Evomon data checklist keeps the site honest and makes future corrections easier.
Data FAQ
Why does the Evomon data checklist matter?
It prevents partial notes from turning into fake database facts.
What is the strongest data proof?
Current in-game evidence, official listing text, screenshots, or reliable source notes with a checked date.