Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Short Description:
Adds a new task called "CatchLimiter" which enables users to automatically disable all catching tasks when balls reach a given threshold, and for a specified duration.
While each task already has a min_balls parameter (excluding Sniper), this is generally very low and often does not permit sufficient recovery time. Eg. if min_balls = 5, and you spend all 5 balls trying to catch a pokemon, you can end up stuck in an "insufficient balls" loop.
This new task basically switches off catch mode for a while so the bot can loot for a while to allow it to recover its ball collection.
I am very interested in feedback on this, and I realise it may not be useful for everyone (hence why it's disabled by default) but feedback I've had so far in slack has been positive. Users report that they often have to stop and disable catching tasks for a while when balls get low, so this should alleviate the problem.