Guides
ANIIMO Regional Forms Guide
A form is a documented variant nested under one canonical ANIIMO entity. The current ANIIMO Central import contains 206 form records across 86 entities; region, weather, time and Prismana labels help distinguish variants without creating a separate URL for every form.
- The current dataset contains 86 Basic Forms and 120 additional documented form records; 58 ANIIMO have more than one form.
- Form labels come from current imported records, not a taxonomy copied from another site.
- Forms do not receive separate canonical routes; one ANIIMO keeps one Aniidex profile.
Dataset snapshot checked October 4, 2026: 86 canonical ANIIMO and 206 nested form records.
What Are ANIIMO Forms?
Forms are named variants of the same ANIIMO identity. They can distinguish a Basic Form from a region-related variant, a weather or time variant, or a Prismana Form. In ANIIMO Central, a form has its own stable record and label but remains inside its parent ANIIMO entry.
That distinction matters when searching. “Scorchhowl” identifies the canonical ANIIMO; “Thunderstorm Form Scorchhowl” identifies one documented form of it. Both belong on the same Scorchhowl profile, where the reader can compare the available form records without fragmenting identity across multiple pages.
One ANIIMO, Multiple Forms
The current repository contains 86 canonical ANIIMO, 206 documented forms, and 58 entities with more than one form. Every entity has one Basic Form in the import, while the remaining 120 records use labels already present in the official-derived data.
The data model protects a simple rule: one entity, one stable slug, one canonical /aniidex/{slug}/ route. Form IDs and slugs remain nested data. This keeps skills, traits, stats, evolution relationships and aliases attached to the correct identity while still exposing the variants players need to recognize.
Forms are not evolutions. An evolution relationship connects separate canonical ANIIMO identities; a form changes the documented variant of the same identity. The Evolution guide and the /evolutions/ index therefore serve a different purpose.
Form Labels in the Current Dataset
The current import uses the following labels. Counts are a dated dataset snapshot, not a promised final roster. The groupings below organize ANIIMO Central’s documented form labels for easier browsing; they are not presented as an official in-game taxonomy.
| Group | Existing form types | Current records |
|---|---|---|
| Core identity | Basic | 86 |
| Region / terrain | Highland, Mountain Woods, Beach, Forest, Grassland, Plateau, Sea of Flowers, Mountain, Mudflat, Bay, Towerwood | 66 |
| Weather / time | Thunderstorm, Rainstorm, Snowfield, Cloudmist, Nighttime | 29 |
| Special | Prismana | 25 |
These groups are editorial navigation for the labels already in the data. They do not assert that every terrain word uses one universal unlock rule, that Snowfield is a live weather icon, or that every Prismana record shares base-form properties.
Regional Forms
Regional and terrain-oriented labels describe documented variants such as Highland Form, Beach Form, Forest Form, Sea of Flowers Form or Towerwood Form. For example, the current database gives Wisptis several nested variants, while Scorchhowl includes Basic, Highland, Thunderstorm, Prismana and Mountain Woods forms.
Treat the exact label as the useful identifier. A form named Sea of Flowers Form has stronger form-level evidence than merely noticing that the parent entity has Sea of Flowers in its habitat array. Habitat associations describe where the official profile lists an ANIIMO; they do not establish an exact spawn point, rate or independently verified condition for each nested form.
The locations index is still valuable for exploration. It connects each region to official habitat residents and highlights multi-form ANIIMO. Use that as a starting map, then check the entity’s form list rather than assuming every resident uses a region-named form.
Weather and Time Forms
Weather and time labels in the current data include Thunderstorm, Rainstorm, Snowfield, Cloudmist and Nighttime forms. Scorchhowl and Thornblade offer Thunderstorm examples; Nimbi has Rainstorm and Cloudmist forms; Flutternym and Bonesky have Nighttime forms.
These labels help identify a target but do not publish a complete encounter formula. The Weather & Time Spawn guide shows how to read the live time control and map weather indicators, including the verified Dawn, Noon, Dusk and Nighttime period names. It intentionally omits unverified clock ranges, weather odds, cooldowns and spawn-rate multipliers.
Prismana Forms
The dataset currently contains 25 Prismana form records. Prismana is a special form category, not a separate top-level ANIIMO, so each record links back to its base entity’s canonical profile. The Prismana guide provides the imported form reference.
Do not copy entity-level habitat, element or role fields into a Prismana form as if they were independently verified. ANIIMO Central keeps current Prismana form-specific element, role and habitat fields empty until a source confirms them. For live regional attraction mechanics, use the Prismana Flow & Nurture guide; its 14 region mappings are Nurture targets, not permanent fixed-coordinate spawns.
How Forms Affect Element, Data and Habitat
A form record confirms the form’s identity fields—its name, slug, type and provenance. It does not automatically replace every property on the parent profile. The current entity page may display shared stats, elements, role, habitats, skills, traits and evolution relationships because those are known for the canonical entity.
Read those shared facts as profile context unless the interface explicitly labels them form-specific. This prevents two common data errors: claiming that every form inherits an independently verified element, and claiming that a base habitat is an exact spawn location for every form. Unknown form-level facts remain unknown rather than being filled for completeness.
Examples From the Aniidex
| ANIIMO | What the nested forms demonstrate |
|---|---|
| Scorchhowl | Basic, Highland, Thunderstorm, Prismana and Mountain Woods labels can coexist under one profile. |
| Nimbi | One entity can include Basic, Rainstorm, Cloudmist and Plateau variants. |
| Flutternym | A Nighttime Form sits beside Basic, Sea of Flowers and Mountain Woods records. |
| Wisptis | Regional or terrain variants remain forms even when a specific form participates in an evolution criterion. |
The examples are chosen to explain the model, not to rank rarity or create a complete form checklist. Browse the full Aniidex for current entity records.
How to Find a Specific Form
Start with the canonical ANIIMO profile and copy the full form name. If it is region-related, review the relevant location page but keep its habitat boundary in mind. If it is weather- or time-related, check the live area’s weather icon and the current time period. If it is Prismana, use the dedicated Prismana sources rather than base habitat assumptions.
Keep evolution separate. A target evolution panel may require defeating an ANIIMO of the same form, which makes the exact variant important, but that does not turn the form into a separate species or route. Always match the wording shown by the panel.
How ANIIMO Central Organizes Forms
Each canonical entity owns its forms, a default form ID and its evolution relationships. The form slug is stable data, while the entity slug is the public route key. This architecture avoids hundreds of thin near-duplicate pages and gives search engines one authoritative profile per ANIIMO.
It also makes corrections safer. Updating a form label or provenance record does not require renaming the canonical entity, changing evolution links or breaking the public URL. Separate Prismana and location indexes can derive their views from the same records instead of maintaining competing copies.
Common Form Mistakes
- Calling every variant a regional form when the imported label is weather, time or Prismana.
- Treating a form as an evolution or creating a second ANIIMO identity for it.
- Assuming parent-profile habitats are exact, form-specific spawn coordinates.
- Copying base element or role data into Prismana records without independent evidence.
- Inventing a taxonomy, rarity ranking or encounter rate that the current data does not contain.
- Expecting one form per URL; canonical ANIIMO pages intentionally group them.
ANIIMO Forms FAQ
How many forms are documented?
The October 4, 2026 repository snapshot contains 206 forms across 86 canonical entities. Counts can change when verified records are updated.
Does every ANIIMO have multiple forms?
No. All 86 entities have a Basic Form, while 58 currently have more than one documented form.
Are forms separate ANIIMO?
No. A form remains nested under one canonical entity and shares its Aniidex route.
Are regional forms the same as Prismana forms?
No. Prismana is its own documented form type and has separate source boundaries and gameplay guides.
Does a habitat prove where every form spawns?
No. It is an entity-level official habitat association, not an exact form-specific coordinate or rate.
Why are there no separate form pages?
The one-entity/one-route model keeps identity, relationships and provenance coherent while still showing every documented nested form.
Tips & warnings
- Entity-level elements, roles and habitats do not automatically become independently verified form-specific facts.
- A regional or weather label does not establish exact coordinates, encounter rates or universal availability rules.
Related ANIIMO
What to do next
Sources & verification
- Officially confirmed: ANIIMO Central imported official Wiki entity, form and habitat records Checked Oct 4, 2026.
Last updated: Oct 4, 2026