How to catch Aniimo

Choose the formula for the target’s state

The official page checked October 4 publishes the three branches below. For ordinary targets, Base Chance = Aniimo base × (1 + Pathfinder catch bonus from Branches or Regional Badges). Check the live encounter's capture prompt first: a probability calculation does not establish that a particular target accepts a tool.

Status factors do not all stack. If a debuff is present, the lowest status multiplier applies; otherwise the highest applies. Some story encounters can force success or failure. The current page no longer describes the earlier two-check Aniipod procedure, so this guide does not treat it as a verified current rule.

Use Alpha capture and reward decisions for that branch, or compare Aniipods while keeping the same ordinary encounter conditions.

References: Official Probability Details · capture, nurture and Sparkling

Base groups: area and growth stage

The current official table uses area progression and Lumin, Gamma or Nova stage. It does not map every species or habitat to an area row. Confirm the target's applicable group rather than assigning a percentage from its level or region name alone.

Alpha has a separate 6% base and formula. The current page does not publish the older alive/defeated eligibility table or an Omega rule. Check the live encounter restrictions; this omission does not establish that Omega can be caught.

References: Official Probability Details · capture, nurture and Sparkling

Pod strength and level difference

Level difference means target level minus character level. A target no more than 10 levels above you has ×1; being above the target grants no extra catch bonus. At differences +11/+12/+13/+14/+15 or more, the multiplier is ×0.8/×0.6/×0.4/×0.2/×0.1.

Read the tool description and live encounter prompt before using a guaranteed-success item. The published multiplier table alone does not resolve every quest restriction.

References: Official Probability Details · capture, nurture and Sparkling

HP, rear attacks and special states

HP appears in the ordinary in-battle branch. The published sample points below do not specify an interpolation rule. The outside-battle rear-attack factor is ×1.5 and does not apply to Tumblers.

The current page gives the status selection rule but no numeric table for individual statuses. Earlier Sleep, Break and other status values are not revalidated by this page. Use the current client for the applicable factor instead of borrowing a number from an older example.

Illustrative calculation, not a species prediction: assume a 42% ordinary base, zero Pathfinder bonus, regular Aniipod ×1, level difference within +10, rear attack ×1.5 and neutral status ×1. Outside battle the result is 63%. For the same hypothetical base in battle at the published 50%-HP point, use ×1.1 instead of rear attack: 46.2%.

References: Official Probability Details · capture, nurture and Sparkling

Make the target precise before spending resources

Write the creature and form together. ‘Emberpup’ and ‘Emberpup — Highland Form’ are related targets, but the official entries do not give them identical habitat lists. A species-only checklist can hide the reason a search is going nowhere.

Open the catalog, search the name or number, and select the form on the detail page. Read its habitat and take that page into the field. If no habitat is provided, choose another documented target for a planned expedition rather than inventing a location from the creature’s element.

References: Official Index · emberpupOfficial Index · highland

Three examples with different search scopes

The entries below support different kinds of trip. Susuta and Iris give a focused named region. Basic Emberpup provides several possible starting regions, so choose the one already convenient to your route. These are planning choices, not measured best spawn locations.

References: Official Index · susutaOfficial Index · irisOfficial Index · emberpup

Learn from a failed attempt

Separate an encounter problem from a capture problem. If you never see the target, investigate region coverage and conditions. If you see it but fail to catch it, investigate your execution and the tools available in that situation. More time in the wrong habitat cannot resolve a timing mistake, and repeating a capture tool cannot find an absent target.

For your own comparison, change one variable at a time. Record the tool, target form, visible state and outcome. Several attempts with different circumstances do not isolate the effect of a particular tool. Use the current in-game tool descriptions for their precise effects and restrictions.

A compact encounter log you can actually use

A short, repeatable log is more useful than a long impression written hours later. Record both encounters and unsuccessful visits; the latter show where you have already looked. Keep the same landmark names across visits so the notes remain comparable.

Common questions