-
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- snipe_high_prio_threshold not working #5224
Comments
If you set eevee to 666 with a threshold of 799. you'll only walk towards the eevee, not teleport |
I have config set to only walk. Pokemon are sought out in descending order as intended just fine, the only issue is that Pokemon that should be disregarded are still walked to. Am I simply misunderstanding how the task actually works or is it a bug? |
For walking, all pokemon are hunted - I don't think ignore is applied, maybe wrong. |
It worked fine for me previously without this issue. I tested some more this evening and after a couple hours, commented-out pokemon were finally ignored. It actually happened with Eevee and there was nothing else around within the walk range. Weird. Maybe it's an intermittent glitch? It seems when it happens it keeps happening for awhile and then stops for a day or 2. I only play in the exact same area all the time so it's the same pokemon day in and day out. |
I'm closing this as it might have already been fixed. If it isn't, please reopen a new one. |
"snipe_high_prio_threshold": 799,
.... etc
Eevee: 666,
I've noticed for awhile now I have to either comment-out a Pokemon or delete them from config completely. Any ideas?
min_time also appears to have no effect. Sometimes bot will reroute to more desired pokemon when they only have a few seconds of spawn-time left.
The text was updated successfully, but these errors were encountered: