Scan radius now 70m and scan delay is 10s

[schawsk]

In the last few days and hours, Niantic has changed how the client receives info about pokemon from the server.
First of all the sight radius decreased to 70m from 100m. From the readme I see that you still use the old 100m sight radius. Will you fix that soon? Can I adjust some options to use your algorithm already until then?

Secondly, A few days ago Niantic changed the scan delay from 1s to 5s. This morning it was increased once again to 10s (see, for example here). Can you adjust that as well please, or tell me again what options might account for this?
Thanks!

[rubenmak]

Seem to be quite some changes to keep up with, thanks for adding these!

You can search in a wider range by setting the step parameter -st to higher
than 1, 2 or 3 for example. This is using the old pokemap script and pings
around on the map.

However, it could be the case that now the range has changed, the steps are
too far. If you find this, please let me know then we can find a fix :)

Second, the minimum time between calls is also a good one. The time between
calls is also set in the old script, both between steps and refreshing the
whole map. Did you already try running the script and find a way to print
the api output whenever the following request is too fast? (Less than 10
seconds) if so, could you share your code? Might help with making a fix :)

On Aug 3, 2016 1:27 PM, "schawsk" notifications@github.com wrote:

In the last few days and hours, Niantic has changed how the client
receives info about pokemon from the server.
First of all the sight radius decreased to 70m from 100m. From the readme
I see that you still use the old 100m sight radius. Will you fix that soon?
Can I adjust some options to use your algorithm already until then?

Secondly, A few days ago Niantic changed the scan delay from 1s to 5s.
This morning it was increased once again to 10s (see, for example here
https://www.reddit.com/r/pokemongodev/comments/4vuijn/psa_minimum_scan_refresh_now_10s/).
Can you adjust that as well please, or tell me again what options might
account for this?
Thanks!

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#26, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AC8fS9YOX-yEq0fkx9JN9cV2e6h9WL-Oks5qcHnIgaJpZM4Jbj2q
.

[schawsk]

Sorry I cannot help you much there. I am a mathematician but quite the bad programmer. I think the old AHAAAAA script uses an approximation of a hilbert path to walk around covering the map right? this path need to be adjusted to account for the 70m radius. changing -st is no fix for this unfortunately. You scan in a wider area but are missing bits inbetween.

When it comes to the refresh rate, I do not know what the precise api output is, but you fail to see pokemon for sure. newer versions of the AHAAAA map do have an -sd flag (scan delay), to fix this though. I.E -sd 10 is what currently should be used for the map to not miss any pokemon. I was quite sad when I realised your script does not accept this yet. I really like your version as I do not have the time to stare at the map all day, so your slack notification are the reason for at least a dozen new pokemon.

However, 3 days ago your script returned about one notification in 30 minutes (I set it up to only notify me about starters and pokemon i do not yet have) Today I had three messages in 20h. So clearly your algorithm's efficiency is hurting through niantic changes!

[rubenmak]

To fix the above shouldn't be too hard, however, I received issues that apparently Niantic is taking measures and changed the API so every API tool seems to be down at the moment.