Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Pokemon show in command line but not on map #17

Open
JefVH opened this issue Jul 19, 2016 · 2 comments
Open

Pokemon show in command line but not on map #17

JefVH opened this issue Jul 19, 2016 · 2 comments

Comments

@JefVH
Copy link

JefVH commented Jul 19, 2016

When I watch the papertrail logs, it states:

Within one step of LatLng: LOCATION (298m NE from you):
(133) Eevee
(41) Zubat

This is the same result as I get in the Pokemon Go app.

But it doesn't shop up on the map.

Any ideas why?

@houseofcat
Copy link

It's my understanding of how the treesimulation was written, that it can you only give you a general location. One step = one pokestep. I can't speak on behalf of emeth, but as a user, you can walk to that location, 298m NE, and hit refresh on your mobile browser, and it should then be visible and populate for you on your map.

@emeth-
Copy link
Owner

emeth- commented Jul 19, 2016

@JefVH Good eye!

So what we know is this. The api returns both visible and invisible pokemon. You can see that in the code here:
https://github.com/emeth-/pokelocater/blob/master/api/pokelocator_api.py#L442-L473

Both get printed to the logs, but I only capture the visible ones to print them on the map.

Invisible ones will not show up when you walk over a location, and people are (to my knowledge) trying to figure out how to interact with them. I think I remember seeing a pokemongodev thread that suggested they were there in an attempt to catch cheaters, and another thread that said they were legit pokemon that would appear when you used a lure, but you couldn't see them until then.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants