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 examples below assume the named states are actually active at the server decision point. They illustrate the published selection rule, not a claim that every listed combination can be deliberately produced on every creature. A transition between animations can make your apparent timing different from the resolved state.
| Illustrative active states | Candidate factors | Selected result |
|---|---|---|
| Sleep + ordinary Break | 2 and 1.5 | 2 |
| Sleep + Wary | 2 and 0.9 | 0.9 |
| Cloak + Wary | 0.5 and 0.9 | 0.5 |
| Capture-prohibited state | Forced failure | 0 |
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
Use a short sequence: confirm that capture is permitted; identify combat or defeated state; identify any adverse status; select the applicable favorable status only if no adverse factor wins; then apply the rest of the formula. Story overrides remain separate. A final result at or above 100% is meaningful only after those checks.
The source lists two Special Stun outcomes without explaining their selection. Do not assume any ordinary stun activates the larger one. Likewise, a low-HP target and a defeated target use different formula branches. The Alpha guide provides a case where choosing the wrong branch gives the wrong strategy.
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?
No. The source distinguishes Normal and Special Stun and does not explain the two Special Stun cases.
Sources & reference notes
Reviewed 2026-09-14. These references describe the scope of this record; details can change.
How we document information
