-
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 not always teleporting #3831
Comments
me too @fari-99 |
its dragonair btw |
@fari-99 From what I can tell it's working correctly based on your config "type": "MoveToMapPokemon", As your config stands, it is behaving as expected. If however you have pokemon in your VIP list they would be walked to as well, as they have not been given a "catch" priority for the sniping config |
@ocoot nothing indicates you even have the movetomap worker even in your configs |
this is my config @k4n30 please check it. and i still don't know what for this values "Aerodactyl": 1000 is CP {
} |
@k4n30 yes, thank you for your reply, it's worked know. it's because the config threshold, i think what threshold mean like more and same (>=) not like above (>). btw VIP the config is
|
@fari-99 can you share full json.config ? |
@ocoot here you go,
|
@fari-99 for the snipping i mean bro |
and i need some information about this "prioritize_vips": true, a few questions:
|
@ocoot opps, sorry already updated the comment.
|
so @fari-99 , prioritize_vips will catch all pokemon on list "vips" : {
??????
|
|
@fari-99 ok thankyou 🐙 |
Expected Behavior
using teleport for every pokemon encounter in map area.
Actual Behavior
many pokemon vip in one area, teleport to one pokemon (higher priority), catch, and move toward another pokemon (lower priority).
teleport behaviour
map area
Your config.json (remove your credentials and any other private info)
Steps to Reproduce
run the bot.
search location in pokesniper.com
put location in web interface pokemon go map
Other Information
OS: windows 10
Branch: dev
Git Commit: d4200e9
The text was updated successfully, but these errors were encountered: