Aniimo Team Composition: Roles, Elements and Mobility
A functional team-building guide built on published role, element and mobility fields, and not a tier list.
AniimoDex does not publish strength rankings. This page explains what each officially published role label covers, how element labels and mobility coverage shape a team, and how to choose a starting Aniimo from what you actually want to do.
Do not choose non-DPS Aniimo by displayed ATK alone
The October 13 developer explanation describes a low-ATK damage safeguard for non-DPS Aniimo, based on level or BREAK for BREAK Aniimo. Below the safeguard, adding displayed ATK may not immediately increase damage. Compare published roles, skills and BREAK information rather than ranking every role by ATK alone; the mobility-and-role guide explains the limits. The same post calls a damage refinement a version 1.1 plan. Despite earlier announcements also using 1.1, this specific change is not verified live here. No published threshold or full formula supports an exact allocation or best team.
Practical guidance added October 14, 2026 from the dated official sources listed below. Historical fixes and developer plans are not new patch releases or independently tested guarantees.
Does AniimoDex publish a tier list?
No. The official Wiki index publishes a role label and one or more element labels per Aniimo, and neither field identifies which Aniimo performs best. A ranking would be an opinion, so this page stays on team functions.
How many Aniimo carry each published role?
| Role | Indexed Aniimo |
|---|---|
| DPS | 31 |
| Break | 26 |
| Support | 18 |
| Regen | 10 |
| Heal | 7 |
What does each published role cover?
- DPS - the index label for damage-dealing Aniimo, and by far the largest group.
- Break - the index label tied to breaking a target. The official catch disclosure confirms a BREAK state adds a x1.5 catch coefficient and that the break catch bonus reaches x3.
- Support - the index label for supportive Aniimo that contribute team effects.
- Regen - the index label for sustain and recovery over time.
- Heal - the index label for healing Aniimo and the smallest group, with only 7 indexed entries.
These descriptions come from the published labels and, where noted, the official probability disclosure. The detail snapshot publishes skill names and descriptions, but not a complete set of cooldowns, damage values, progression costs or balance data.
How do element labels fit into a team?
Element labels are verified official data, and 8 of the 86 indexed Aniimo carry more than one element. The matchup multipliers in the type chart tool, however, are a community-compiled reference rather than official data, so use element labels to check that your team covers different elements rather than to assume a guaranteed counter.
| Element | Indexed Aniimo |
|---|---|
| Water | 19 |
| Grass | 16 |
| Earth | 16 |
| Wind | 14 |
| Dark | 12 |
| Lightning | 10 |
| Fire | 9 |
| Ice | 9 |
Why does mobility matter for a team?
Mobility is the field ability used for traversal or environmental interaction, and 50 of the 86 indexed Aniimo publish one, across 19 distinct ability names. These descriptions can help you compare field functions, but the source does not map them to specific required routes or locations.
What should a new player choose first?
Choose by what you want to do rather than by which Aniimo looks strongest.
- To explore: shortlist Aniimo that publish a mobility ability, because fewer than half of the index carries that field.
- To catch efficiently: consult the published status and backstrike coefficients, then verify which Aniimo can apply the relevant state in your current version. The source does not compare those teams with damage-focused teams.
- To play co-op: look at Support, Regen and Heal, which are the three smallest published groups at 18, 10 and 7 indexed Aniimo.
What can this page not tell you?
It cannot rank Aniimo or recommend one fixed team. The registered sources include published stats and skill descriptions, but they do not provide enough complete cooldown, damage, progression-cost and version-balance data for a defensible strength ranking.
Roles and elements describe what an Aniimo is for, not how strong it is. This page stays on the functional side of that line.
Official sources
- Official Aniimo Wiki - 86 Basic Form records ↗
Rendered English Basic Form pages checked for all 86 directory entries: identity, artwork, elements, roles, six attributes, skills and their Type/Cost/Power parameters, traits, published habitats and mobility. Alternate forms are linked, not imported. Evolution image identities are resolved only against indexed artwork; six unresolved trees are excluded from family comparisons. Existing local routes are preserved by exact English name, never by changed official number.
- Aniimo Official Probability Disclosure ↗
The official disclosure publishes the three catch scenarios (outside battle, in battle and defeated target), the region-stage base rate table for evolution stages 1-3, the level-difference, cube, HP, backstrike and special-status coefficients, the min/max status stacking rule, the two-square-root resolution for a standard cube on a normal target, and additional drop and sparkling-style tables. It also states that the base rate is decided by each Aniimo template and is not derived from level, which means per-species template rates are not published.
- Aniimo Dev Feedback | Oct 13 ↗
Developer explanation of Sanctum spawning and non-DPS damage safeguards; spawning, disengagement and aggro reports remain under investigation. Rescue improvements, collectible returns, Chaos changes and the version 1.1 damage refinement are plans, not delivered fixes. Seasonal and fortnightly updates describe intended cadence, not guaranteed release dates.
AniimoDex editorial notes
Sources, scope and corrections
This site organizes published Wiki records and formula disclosures into guides and lookup tools. Source links and dates describe the evidence used; they do not establish live-game testing. Missing or conflicting evidence remains labelled, and corrections can be reported through the contact page.