Open jane0815 opened 8 years ago
Need to see logs to figure out what's going on. 80 min balls isn't very much.
The 80 balls min was only a suggestion for a new limit when bot could go into farm mode to get more balls before trying to catch more pokemons.
My bot is using a lot balls because i set it to miss a lot trows. It is not a bug that causes my bot to run out of balls it is the settings i made to make it looks more human.
Sorry if i did not explain it good enough.
Summary for devs:
This would probably also include settings for overwriting. For example, we see a VIP.
Considering we will still get balls from poke stops, maybe 80 is enough.
I know what has caused running out of balls. It is the social web sniping!
Now that it was fixed my bot ran out of balls again because it is not passing enough stops when sniping. I will try to bypass it and raise "skip_rounds": 6,
But it would still be nice if the bot would switch to farm mode when it has less then "minimum" and farm till is has "desired" number of balls again. Raising speed while farming is a good idea too.
Expected Behavior
If bot is out of pokeballs switch to farm mode for a while to stock up balls.
Actual Behavior
But runs out of balls but does not switch to farm mode. It will spin a fort if it passes one but will reach next pokemon with to few balls to catch it.
Your FULL config.json
I set my bot to miss a lot of throws, high speed and everything what will make it use/waste a lot balls.
I could change settings to save balls but this is not my intention. It is a test run to emulate bad ball throw rates.
Possible solution
Add "min_balls_keep" balls to keep and let bot farm until it has hacked "min_balls_farm".
How it would help others
Prevent the bot to run out of balls.