Aniimo catch rates: formulas, Aniipods and encounter conditions

Choose the formula for the target’s state

The official Probability Details page first tests whether the target can be caught. An ineligible target has 0% chance. For eligible targets, use the appropriate row below. Base Chance includes the character bonus: configured chance group × (1 + character base catch bonus).

Special statuses do not all stack. If any active multiplier is below 1, use the lowest one; otherwise use the highest. Story encounters can force success or failure. A calculated chance of at least 100% guarantees success once the applicable eligibility and override rules are satisfied.

A standard Aniipod used on one target performs two checks, each at the square root of the final probability; both must pass. Together they still give the calculated final chance, not its square. Other methods perform one check.

References: Official Probability Details · capture, nurture and Sparkling

Base groups: use the creature template, not its level

The official table selects the row from the Aniimo’s template configuration, not dynamically from level. These percentages precede the character base catch bonus. The source does not map every species/form to a row and tier here, so do not assign a creature a percentage from its habitat name alone.

Common Alpha targets have 0% chance while alive and a 6% defeated base chance. Common Omega targets have 0% and cannot be captured. Defeated targets use their own formula, not the in-combat 0%-HP multiplier.

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.

The pod guarantees below apply within the eligibility rules. For example, the official table still marks an owned or Umbral target as capture-prohibited.

References: Official Probability Details · capture, nurture and Sparkling

HP, rear attacks and special states

HP applies only in combat. The official sampled HP points are shown below; no interpolation rule is specified on the page. Outside combat, a server-confirmed rear attack with a standard Aniipod gives ×1.5 instead; otherwise ×1. Tumblers receive no rear-attack bonus.

Break gives ×1.5, or ×3 with the Break catch bonus active. Normal Sleep, Stun, Eating, Woozy and Lured give ×2. Special Stun gives ×4 or ×100; Deep Sleep and Collecting Nectar give ×100. The source does not explain how the two Special Stun cases are selected.

Cloak gives ×0.5; Wary/Watching ×0.9; Leaving ×0.8 or a forced 0. Rampaging, Bubble Barrier, Umbral, an existing owner and other prohibited states force 0. An Asleep target also under the source’s Alerted example uses ×0.9, not ×2 ×0.9.

Worked calculation, not a species prediction: assume a configured 42% base, no character bonus, standard Aniipod ×1, level difference within +10, an eligible out-of-combat rear attack ×1.5 and a single Sleep status ×2. The result is 0.42 ×1 ×1 ×1.5 ×2 = 1.26, so it reaches guaranteed success. Add an adverse ×0.9 status and that status replaces Sleep: the result becomes 56.7%, provided no forced override applies.

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