-
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
Ignored pokemon list not applied in move_to_map_pokemon or catch_pokemon #4887
Comments
same here. Ignored, moving to it, and capture... wtf man
|
For the devs: MoveToMapPokemon doesn't account for the ignore list at all either (I realize it passes the work on). Do we know the pokemon stats when we see one in this file or do we need to go closer? I'd love if this task and move to fort set our closest target, then we move to next target in our stepper. Would solve the issue folks have when very near a pokemon and very near a fort - getting stuck in an endless loop moving back and forth. This is also part of what I'm talking about in #4754 |
Update :
|
@dummyaja I think that is a separate issue. What is your config (please use 3rd party posting site and give link). |
Expected Behavior
Just skip them, and track skipped pokemon number in stats, without showing log. Is this possible?
[FEATURE] Would it be possible to limit
Moving towards pokestop XXX
log to a distance multiple of 10? If I'm walking slow (eg. min:2, max: 4), I get 2-3 logs every 10 metersActual Behavior
Other Information
OS:
Branch:
Git Commit:
Python Version:
Any other relevant files/configs (eg: path files)
Short Description
Possible solution
How it would help others
The text was updated successfully, but these errors were encountered: