MoveToMapPokemon will not run if total amount of balls is too low #3155
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
User can set the minimum amount of balls to run the task.
Default min_ball = 1
Merged
|
I found it not catching VIP pokemons when the amount of balls is low but usable. Will fix it in another PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Sometimes, MoveToMapPokemon task will eat your balls very quickly without enough spin_fort. With this setting, MoveToMapPokemon will not run unless you have total amount of balls (combination of Pokeballs, Greatballs and Ultraballs) higher than your desired number. Otherwise, It will run the MoveToFort task.