Resolve capture prohibitions first. For ordinary competing status factors, an adverse factor wins; otherwise use the largest favorable factor rather than multiplying all bonuses.
In this guide
Use a status decision table
A creature can show more than one state during the same attempt. The official formula does not let you multiply every visible bonus together. Treat selection of the status factor as its own calculation before returning to the encounter formula.
The current official page gives the selection rule but no numeric values for named statuses. The factors below are invented inputs demonstrating the arithmetic; they are not verified Sleep, Break or Stun multipliers.
| Illustrative inputs | Selected factor | Reason |
|---|---|---|
| Favorable factors 2 and 1.5 | 2 | Choose the highest when no debuff is active. |
| Favorable 2 and adverse 0.9 | 0.9 | The adverse factor takes priority. |
| Adverse factors 0.5 and 0.9 | 0.5 | Choose the lowest adverse factor. |
References: Official Probability Details
See the cost of an adverse state
Assume the applicable calculation excluding status yields 30%. With a selected factor of 2, the result is 60%. With 0.9, it is 27%. Multiplying both factors would incorrectly produce 54%. This hypothetical example isolates why identifying the adverse state can matter more than adding another favorable one.
If you are comparing two tactics, write down which state each tactic is meant to create and which unwanted state it might leave active. A plan described only as “apply more debuffs” is incomplete. You need to know the relevant capture state, not merely whether an ability deals damage or carries a combat effect name.
Troubleshoot an apparently good throw
First check the live capture prompt, choose the ordinary outside-battle, in-battle or Alpha branch, then determine the applicable status factor. Apply only factors present in that branch. Story overrides remain separate.
The current page does not provide the older Normal/Special Stun values. A stun animation alone cannot establish its current multiplier. Use the Alpha guide to see why the ordinary HP and status factors should not be added to the Alpha-specific row.
When logging a failed attempt, record the visible states and their timing rather than immediately declaring a published multiplier wrong. A screenshot before the throw and a result afterwards can support a useful report, but they may still miss a server-side transition between those moments.
References: Official Probability Details
Common questions
Can I combine every positive status?
The published selection rule uses the highest favorable factor when no adverse factor is present.
Does every stun provide the largest listed bonus?
The current official page does not list a numeric stun multiplier. Verify the present encounter and client description; do not assume an older value applies.
Sources & reference notes
Reviewed 2026-10-04. These references describe the scope of this record; details can change.
How we document information
