-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Pokemon capture percentage inaccurate/confusing. #4836
Comments
You'd think so, but I'd guess there's still random chance of failure, even if it's 100%. A critical miss if you like. Basically, your stats say you have 100% but there's still always some chance you'll screw it up. |
Although... it looks like it's stacking berries and it shouldn't be. Once a berry is "used" (ie. after you throw berry followed by ball) it should reset, not keep increasing chance. |
Also a few more weird things:
|
Yes, the order of the used balls is weird. This is because the script finds the best ball to catch the pokemon. What happens is this: The reason the berry isn't used it because your chance of catching is above the ideal_catch_rate_before_throw. Because the incorrect repeated multiplier. I'll work on this. |
Merged to dev |
Expected Behavior
If the chance to capture a pokemon is over 100% then it should always capture.
Actual Behavior
It still misses sometimes.
Your FULL config.json (remove your username, password, gmapkey and any other private info)
Output when issue occurred
Steps to Reproduce
Wait until a wild Pokemon appears.
Other Information
OS: Debian 8.1
Branch: dev
Git Commit: 81384b3
Python Version: 2.7.12
Any other relevant files/configs (eg: path files)
The text was updated successfully, but these errors were encountered: