Track species and forms separately. Choose a small number of documented targets per trip, group them by habitat, and distinguish seen, obtained and still-unverified information in your own checklist.
In this guide
Choose what completion means for this session
A species collection, a form collection and a useful combat roster are different projects. Decide which one you are advancing before selecting a destination. Otherwise a successful trip can feel incomplete simply because the goal changed while you were playing.
Use the Index number as the stable species identifier and the form name as a second field. Scorchhowl’s multiple named forms demonstrate why a single checkbox is too coarse for a form collector. A species entry in the public Index also does not establish the final number of collectable creatures in every future version.
References: Official Aniimo IndexOfficial Index · scorchhowl
A checklist with enough context to be useful
You can keep this in a personal note or spreadsheet. Atlas provides the source records and shareable filters; this worksheet does not claim an account-synced collection feature exists on the site.
| Column | Purpose |
|---|---|
| Species number + name | Stable identity, including unusual Index numbers |
| Form | Prevents a Basic sighting from completing every variant |
| Seen / obtained | Separates an encounter from collection progress |
| Habitat and landmark | Makes another expedition actionable |
| Next action | One specific task, such as revisit a region or inspect a condition |
| Source / date | Explains where a claim came from |
Reduce the next trip to a few clear decisions
Choose one main target and a small number of secondary targets whose documented habitats overlap. For example, Susuta and Basic Emberpup both list Echoback Landing. The overlap supports a shared investigation, while the main target keeps the trip from expanding into an unfocused tour.
After returning, mark only what happened. A sighting without a capture stays ‘seen’. An alternate form remains incomplete until that form is obtained. If a source field was missing, keep it unresolved rather than filling it from a guess made during travel.
References: Official Index · emberpupOfficial Index · susuta
Review the plan when progress stalls
Repeatedly failing to find one target is a reason to review the form, region coverage and conditions, not a reason to multiply an unsupported spawn percentage. Switch to another documented objective if the missing information prevents a meaningful next action.
Keep a separate ‘needs evidence’ list for acquisition rules that are not yet clear. That lets you continue collecting without disguising uncertainty as a completed guide. When the source updates, you can revisit the exact unresolved question.
Sources & reference notes
Reviewed 2026-09-14. These references describe the scope of this record; details can change.
How we document information
