Choose a damage plan, identify what interrupts it, then add a companion that addresses that specific problem.
The groups below are illustrative cores based on published Basic Form skills. They are not tested best-in-slot teams, a claim about party size, or a promise of early availability.
Start with the encounter, not four attractive portraits
Write down what the group needs to accomplish. An exploration trip may need a movement ability and a way to recover from mistakes; a combat encounter may expose a resource shortage or demand a different elemental action. Choose the activity before you choose the names.
Then name the failure you want to prevent. If your damage dealer cannot stay active because health runs out, consider healing and positioning. If skills stop because energy is empty, inspect resource recovery. If a condition requires a particular family or terrain, decide whether the rest of the group can actually support it.
Use the five role labels as reading prompts
Role labels organize the roster, but the skill text determines the effect, its recipient and its restrictions. BREAK and REGEN are distinct from attack and healing. Do not read the REGEN attribute or role as a promise of automatic party-wide health recovery.
The following examples show what to inspect. They are not a requirement to bring one creature from every role, nor proof that each creature in a role offers the same benefit.
| Role | Question to answer | Example to inspect |
|---|---|---|
| DPS | What action or condition creates the damage opportunity? | Emberpup: Fire Kick rewards a successful dodge. |
| BREAK | What improves BREAK, and when does that bonus activate? | Helmwhelp: Counter Strike activates after being attacked. |
| Heal | Who receives health, and what resource does healing cost? | Glacy: Healing Water distinguishes ally recovery from the caster’s recovery. |
| Support | Which actions or elements benefit from the effect? | Tromber: Zephyr’s Breath specifically boosts party Wind damage. |
| REGEN | What resource is restored, and to whom? | Besauce: read Charged Geyser and Power Surge rather than assuming an HP heal. |
An example core for learning dodge-based damage
Consider Emberpup for damage, Helmwhelp for a BREAK-oriented option and Glacy for healing. This is a way to divide responsibilities while learning an encounter. It is not a recommendation to acquire a later-stage creature immediately; substitute what you actually have by matching the needed skill effect.
The key tradeoff is that their useful conditions do not all reward the same behavior. Emberpup’s Fire Kick rewards dodging, while Helmwhelp’s Counter Strike activates after being attacked. You should not deliberately absorb avoidable damage just to make every passive active. Decide which creature and condition make sense for the current moment.
EmberpupBasic Form · Fire · DPSFire Kick
Quickly leaps up with brief Invincible to dodge attacks, then wraps itself in flame and dives down to attack, dealing damage to targets around the landing point. When successfully dodging a target’s attack, deals 120% damage and increases damage by 20% for 20s.
Damage responsibility: learn the dodge condition first. If you cannot trigger it reliably, simplify the action sequence rather than assuming another companion will make it automatic.
HelmwhelpBasic Form · Wind · BREAKCounter Strike
After being attacked, increases BREAK efficiency by 25% for 10s.
BREAK responsibility: recognize when the condition is active. Its trigger is situational, so do not treat the listed percentage as a permanent bonus.
GlacyBasic Form · Water / Ice · HealHealing Water
Restores HP to all allies equal to 8% of the caster’s max HP, and restores HP to the caster equal to 12% of their max HP over 5s.
Recovery responsibility: reserve the listed skill resource for the heal when needed. Use the wording about allies and the caster to understand which health bars should change.
When a repeated element or family can make sense
Repeated elements are not automatically a mistake. A specific support effect may reward them. Tromber’s Zephyr’s Breath increases party Wind damage, which gives you a concrete reason to compare Wind actions elsewhere in the group. That reason becomes less useful when the planned attacks do not deal Wind damage.
Chirpi and Tromber also share the Band Member trait. Its text restricts the energy benefit to the next Chirpi family member switched in and includes a trigger interval. This is a conditional family interaction, not a generic energy engine for any lineup. Inspect both the family requirement and your intended switching pattern before relying on it.
An illustrative alternative core is Tromber with another Chirpi-family companion, plus a recovery option suited to your encounter. You gain a focused interaction to practise, but may give up some elemental variety. Compare that tradeoff with the enemy you are actually facing instead of treating family membership as sufficient evidence of a strong team.
TromberBasic Form · Wind · SupportZephyr's Breath
Deals Wind damage over a large area and increases all party members' Wind damage by 25% for 30s.
A reason to build around Wind damage. Read the attacks you plan to use rather than relying only on the element badge beside a creature’s name.
ChirpiBasic Form · Wind · SupportBand Member
When switching Aniimo in battle, restores 20 EP to the next Chirpi family member switched in. Triggers once every 20s at most.
A reason to inspect a family pairing. Make sure the receiving creature meets the stated condition; do not extend the effect to unrelated companions.
Replace the missing function, not the portrait
If an example companion is unavailable, filter the Aniimos by the role you need, then read the exact form’s skill. Two Heal entries can have different recipients or costs; two Support entries can favor different elements. The useful replacement is the one that fixes your problem with conditions you can satisfy.
Energy recovery deserves its own check. Besauce’s Charged Geyser and Power Surge provide concrete resource mechanics to read. Their descriptions are not evidence that Besauce can replace an ally-targeting heal or replenish every teammate. A lineup that loses because of HP pressure still needs an answer to that pressure.
BesauceBasic Form · Lightning · REGENCharged Geyser
Restores 15 Energy and restores 0.8 Energy per second for 12s.
Consider the resource pattern described here when energy is the problem. Verify who receives the recovery in game before building a party-wide plan around it.
Compare one change at a time
Use a repeatable encounter and keep as much as possible unchanged. Record the group, exact forms, planned action and the point at which it fails. Then replace one option. Changing the whole group, upgrades and route together makes the result difficult to interpret.
Look for a result connected to the original goal: fewer resource interruptions, a more reliable BREAK opportunity or enough recovery to finish the encounter. A larger stat total is not a useful success measure if the same failure still ends the attempt. Check elemental coverage with the chart, but keep skill conditions and positioning in the decision.
| Record | Useful detail |
|---|---|
| Objective | The same encounter or route you want to improve. |
| Exact forms | Basic or named regional form; do not mix their records. |
| Failure | The action that stopped working and the resource or condition involved. |
| One replacement | What function it should add and what you give up. |
| Result | Whether that specific failure improved on a comparable attempt. |
Common questions
Do I need five different roles?
No. The labels are a way to inspect available functions, not a mandatory composition. Prioritize the encounter and the effects you can actually use.
Does a high REGEN value mean a creature heals the team?
Do not infer that. Read its skill and trait descriptions for the resource, recipient and condition. Health recovery and energy recovery solve different problems.
Are these teams tested rankings?
No. They are examples of reasoning from published abilities. Availability, progression, the encounter and your execution can change their usefulness.