Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't capture PM with low capture rate #1214

Open
Unknown-Tokyo opened this issue Oct 6, 2024 · 0 comments
Open

Can't capture PM with low capture rate #1214

Unknown-Tokyo opened this issue Oct 6, 2024 · 0 comments
Labels
Unconfirmed Not been checked if this bug actually occurs yet

Comments

@Unknown-Tokyo
Copy link
Contributor

Issue Description:

Yes I know they are with low capture rate... but it is not common in statistics.
those pm just can't be catch normally.

What happens:

I have used up hundreds of ultra balls on a 1HP slept PM with 3 capture rate, while it should enough for capture them many times in pokemon.

Normally, the ball shakes most 4.5 times with 4 checks. If any check failed, the PM broke out before corresponding shake. otherwise, the PM got catched after last 0.5 round of shaking
But in such 3-capture-rate PMs, they may shake 4 times, but always broke out before last half round of shaking
And, a sleeping 1HP PM with 3 capture rate have about 11.9% chance to be catch if using G7 rules and parameter, without any other buff or critical capture count. 11.9% success with 100+ times failure, it seems impossible in statistics.
I wonder if there is a flooring bug cause it, or the

What you expected to happen:

can normally catch them anyhow...

Steps to reproduce:

  1. find any wild pm with capture rate 3, in my case I tried Type: Null and Beldum
  2. try catch them, for example, making them have only 1HP left and sleeping, and use tons of pokecubes
  3. but them won't be capture, even after the cube shaked 4 times, and with 100+ try
    ...

Affected Versions (Do not use "latest"): Replace with a list of all mods you have in.

Pokecube AIO: 3.24.0.k
Minecraft: 1.19.2
Forge: 43.4.4

@Unknown-Tokyo Unknown-Tokyo added the Unconfirmed Not been checked if this bug actually occurs yet label Oct 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Unconfirmed Not been checked if this bug actually occurs yet
Projects
None yet
Development

No branches or pull requests

1 participant