-
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
MoveToMapPokemon has higher priority than CatchVisiblePokemon #3710
Comments
please put the MoveToMapPokemon task before CatchVisiblePokemon and CatchLuredPokemon task. |
have same issue, changing task order didnt help |
@fari-99 like @Arcasss said changing the order didn't help
|
@fari-99 Changing the order makes the bot ignore all pokemons until the [MoveToMapPokemon] is done. |
Hmm, the task move to map pokemon seems in higher priority. Btw in what do want this config fo? Sniping? Because the config in move to map pokemon the snipe parameter is false. |
I'm not using sniping, but having same issue. Tried replacing Catch task before and after didn't change anything for me as well. |
I checked codes on this, and It seems it is occuring because I am using different account for PokemonGo-Map (at least for me.) |
I think what is happening is the MoveToMap saves the coords for the priority pokemon and begins moving. If you are walking, you will encounter pokemon along the way and possibly be delayed enough that the pokemon has despawned, however your bot doesn't know this and continues moving toward the coords. The bot can also encounter a pokemon 400 meters away and you can see this same behavior that even though the pokemon has been caught, MoveToMap still moves toward the original coords. |
This one @fari-99 ?? @chuparCh0pper does the above comment fix your problem? |
@k4n30 yes. |
Doesn't for me:
Running 1651d1a with config:
|
@Vvkmnn |
Fair enough, I'll try that order and see how it runs. |
The only config that works for me is putting the catchVisible before and after moveToMap. Ive tried both ordering: (catch before moveToMap): it does not capture the pokemon encountered. (catch after moveToMap): it does capture the encountered pokemon but wont pickup any pokemon along its way until the moveToMap task is done. |
Without multithreading, unfortunately, it's going to be a catch 22 argument. I'm not sure what issues putting the task twice is going to cause, though. It's almost as if MoveToMap needs to be broken out into its own thread |
Expected Behavior
Catch encountered pokémon
Actual Behavior
Your config.json (remove your credentials and any other private info)
The text was updated successfully, but these errors were encountered: