PGO-mapscan-opt
PGO-mapscan-opt copied to clipboard
Show more information about spawned pokemon
See https://pokemonkiel.de/map/ - I think they're running PokemonGo-Map which displays IV and attacks for spawned pokemon, this would be pretty useful.
wauw, that is indeed very handy... my only concern is how would this do on api calls towards Nia?? the more calls the more you are under their radar to get busted for scanning.. for the rest i DO like that map a lot, specially because of the information about gyms as well.
This was previously requested and @seikur0 has no plan to implement it for a couple reasons. It requires starting an encounter with every pokemon, which would require far more API calls and an increased number of scanning accounts.
thats what i was saying, not only more scanning accounts, but most likely also indeed more api calls and therefor risk of being banned.. but furthermore the gym information would be nice ^^
Gyms and pokestops are saved in the learn files after the learning phase is completed. It probably wouldn't be much effort to add the gyms to the database and update the color each time one of the scanning threads "sees" it.
Gyms and pokestops could be written into the webres data file and used for the website. Maybe another button to toggle it, if somebody wants to implement it :) I'm not a fan, of updating their information, when they're randomly scanned, so I'd rather don't show these at all.
What about loading these values on-demand rather than constantly scanning?
I.e., you see a monster on the map, click info and get IV, attacks, etc
The sight range of gyms and pokestops is extremely far. These would be seen several times an hour just from normal scanning. It wouldn't necessarily be up to date always but I think it might still useful.
I wouldn't mind seeing gym status on the maps either. I can try and see if I can figure out enough Python to get that working.
You can do IV and moveset scanning with only 1! account for each spawned Pokemon. To do so, use a queue without concurrency and you'll be fine because there are no rate limits for the necessary API functions (set location and encounter)
It's not about the efficiency, it's more about morals and keeping the game enjoyable.
You've got a point there.