Can 0.00% Still Catch? What Palworld 1.0 Actually Checks

A Palworld capture chance of 0.00% does not tell you everything the game knows. It is a two-decimal display, not a published copy of the internal capture calculation. But that does not mean every target showing 0.00% is secretly catchable either.

The safe answer is conditional: a displayed 0.00% can hide precision below the display, while an ineligible target can be blocked outright. The HUD alone does not prove which case you are seeing.

Verified on ✓ v1.0.

Why 0.00% does not automatically mean zero#

Any percentage formatted to two decimal places loses information. A tiny positive internal value can occupy the same display bucket as mathematical zero. Palworld does not publish the complete native formula or every intermediate value, so the aim percentage should be treated as a rounded estimate of the current throw.

That distinction matters because a widely shared capture test began with a 0.00% front-facing estimate, but the successful throw landed from behind and displayed 0.07%. The test demonstrates that position can move an apparently hopeless target into a visible nonzero chance. It does not prove that the final roll succeeded while the screen still read 0.00%.

What Palworld 1.0 actually checks#

Pocketpair confirmed that Palworld 1.0 changed the capture-rate calculation and made capture easier overall. The full formula remains unpublished, but current game data and native behavior confirm several pieces of the process.

Formula status

Changed in Palworld 1.0

Aim display

Rounded to two decimals

Maximum Sphere bounces

2

Critical capture effect

2× capture bonus

Exact critical proc chance

Not publicly confirmed

The practical capture check includes more than the number beside your reticle:

1. Target eligibility: Some encounters or states cannot be captured. The game can reject the attempt before ordinary odds matter.
2. Sphere strength: Higher-tier Pal Spheres contribute more capture power. A basic Sphere against an extreme level gap can leave almost no usable chance.
3. Capture Power rank: Each rank adds effective Sphere power in the current data, making permanent upgrades valuable across every tier.
4. Target condition: Remaining health and applicable status or situational modifiers affect the attempt.
5. Throw position: A hit from behind receives a capture bonus and can change the displayed rate.
6. Critical capture: When it triggers, the current native data applies a two-times bonus. The exact trigger probability is not published.
7. Bounce resolution: The capture animation can bounce a Sphere up to two times before the final outcome.

The PalMods capture calculator is useful for comparing health, level, Sphere, effigy rank, and situational choices. It is a fitted planning model, not a claim that the complete internal Palworld 1.0 formula has been recovered.

Critical capture is not the same as display rounding#

A critical capture is a separate favorable event. It can improve the capture attempt when it procs, but it does not retroactively turn an immune target into a legal one. It also should not be used as proof that every 0.00% display contains a live roll.

The aim percentage answers, approximately, “how strong is this throw before hidden resolution?” The critical system answers “did an extra capture bonus trigger during resolution?” Those are different questions, and the current data does not publish the exact critical-trigger chance needed to convert one into the other.

This is why the most reliable strategy is to improve the visible throw first. Treat a critical capture as upside, not a plan.

How to catch a Pal showing 0.00%#

1. 1Check for an immunity message

   If capture is explicitly blocked, save the Sphere and change the encounter state.

2. 2Lower the Pal's health safely

   Move it into the smallest health range you can control without defeating it.

3. 3Upgrade the Sphere tier

   Use the strongest Sphere you can afford for the target's level and rarity.

4. 4Improve permanent Capture Power

   Rank upgrades strengthen every future capture attempt.

5. 5Reposition behind the target

   A back throw can raise a rounded 0.00% into a visible positive chance.

6. 6Apply a useful status effect

   If the encounter allows it, a controlled status can improve the attempt.

7. 7Recheck the displayed rate

   Throw only after the new position and condition have updated the reticle.

Start with the Pal Sphere item guide if you are unsure whether your Sphere tier is the bottleneck. For a broader summary of the systems that changed at launch, see everything added in Palworld 1.0.

When you should stop throwing#

Do not burn a stack of rare Spheres just because 0.00% might be rounded. Stop when the game explicitly says the target cannot be captured, when your best available Sphere cannot produce a visible rate after a back throw, or when the resource cost is larger than the value of returning with better gear.

The difference between 0.00% and 0.07% is not cosmetic. At 0.07%, the display confirms a positive visible estimate. At 0.00%, you are operating inside an unresolved display bucket. Stronger preparation moves the attempt out of that ambiguity.

Do not ask whether 0.00% is secretly enough. Ask what will make the next throw visibly better.

Sources#

• Official Palworld 1.0 changelog
• PalMods capture calculator and methodology
• Player capture experiment showing the winning 0.07% back throw