Check whether the target is catchable before spending a rarer item. The official probability reference starts with an eligibility check; a prohibited target is not rescued by multiplying a displayed chance.
September 19: a result-processing bug is not a catch-rate formula
Patch 1.0.3551601.0 lists a fix for catch results not being processed correctly. It does not give an affected species list, a new base probability or a compensation guarantee.
When a result message and the creature shown in Aniimo Management disagree, update and keep a screenshot of both. This is our evidence-gathering recommendation, not proof that your target was successfully caught. An ordinary escaped target is not automatically this bug; a displayed 0% can still be a capture-eligibility question.
If the creature never appeared after nurturing, use the separate offering-refresh guide. If it appeared but could not be caught, continue with the eligibility and probability checks below.
Start here when a catch is impossible
The official table lists Common Alpha at 0% while alive and a 6% base after defeat; Common Omega cannot be captured. Umbral, an existing owner and other capture-prohibited states also block capture.
These are the reference’s specific labels, not a promise that every boss follows one universal rule. Check the exact target and state. Story encounters may have forced outcomes.
Do not combine incompatible bonuses
The official formulas separate outside combat, combat and defeated targets. The back-attack term belongs outside combat; the HP term belongs in combat. Special-status bonuses do not all multiply together: a penalty takes precedence, otherwise the highest active bonus is used.
Practical approach: record whether combat is active, the target’s current state and the item used. Changing several things at once makes a failed attempt harder to explain.
Why this is not a species-specific calculator
Base chance depends on the target’s configured template, not simply its level. The reference does not map every field-guide entry to that template, and its HP table does not specify every intermediate value. We do not invent either input.
A hypothetical worked example can explain multiplication, but it is not an estimate for your target. Likewise, a preparation checklist measures completed steps, not probability. Keep the two separate when using the catch planner.
Two checks do not square the final displayed probability
The reference says a standard single-target Aniipod uses two square-root checks. Their combined probability remains the final chance.
Mathematical example only: a final chance of 64% means two 80% checks, because 0.8 × 0.8 = 0.64. It does not become 40.96%. This example is not measured game data.
Use the reference, then record the missing evidence
Open the official probability reference for the full table. It is undated; we checked it September 16, 2026, rather than assuming it was published that day.
For Umbral encounters, distinguish direct capture from the egg route. For Prismana, distinguish triggering a Flow from the later capture. If the game disagrees with the reference, record the build, target form and state, and report the discrepancy instead of guessing an explanation.
Good questions.
Can a better Aniipod bypass a capture-prohibited state?
Do not assume so. The official reference checks eligibility first and sets prohibited captures to zero.
Is an Alpha’s 6% defeated base its final catch chance?
No. It is a base for the reference’s Common Alpha case, not a final probability after all applicable factors and overrides.
Is the catch planner a catch probability calculator?
No. Its completion count tracks preparation steps and notes, not the probability of catching a target.
Check the source
- Patch 1.0.3551601.0 — capture, nurturing and Sanctum fixes
- Patch 1.0.3551601.0 — Simplified Chinese counterpart
- Official probability details