pgoapi
pgoapi copied to clipboard
Opening Pokestop?
? function FORT_SEARCH is supported
@tejado so I guess the rough logic behind this would be:
- To retrieve all locations using
api.get_map_objects
- Filter the JSON response to find pokestops
- Use the
api.set_position
call to update the players location to the pokestop - Call
api.fort_search
which should open up the pokestop?
Please correct me if I am wrong.
yea, correctly.
Thank you very much.!!
@tejado thank you
The Pokemon that are caught by the program have a high probability of fleeing how to stop that from happening?
the command that i use is api.catch_pokemon(encounter_id=pokemon['encounter_id'], pokeball=1, normalized_reticle_size=1.950, spawn_point_guid=pokemon['spawnpoint_id'], hit_pokemon=True, spin_modifier=1, NormalizedHitPosition=1)
@manojprithvee @mikeres0 would it be possible guys to share the catch logic, maybe in a PR with an example file ?
Hi @ahmadassaf , I suggest to you go into slack channel :smile
If you use 1.950 for normalized_reticle_size you will be an easy future ban target.... no one gets "excellent" throws 100% of the time.
pokeball=1 means use standard pokeball, you might want to use 2,3,4 (for great, ultra, master) based on CP of pokemon you are catching.
If the pokemon are FLEEING with every attempt, that means you have been banned for cheating (ban will be lifted in 2-8 hrs time-frame)
Also, if you "teleport" to a Pokestop and do a straight "search fort" call you are also probably going to be banned in the future as the actual game client does a "get fort details" call before a "fort search". The details gets you the name and the image URL of that picture in the middle (plus other stuff)
Thank you and will follow !!
On Fri 22 Jul, 2016 11:52 pm Nostrademous, [email protected] wrote:
Also, if you "teleport" to a Pokestop and do a straight "search fort" call you are also probably going to be banned in the future as the actual game client does a "get fort details" call before a "fort search". The details gets you the name and the image URL of that picture in the middle (plus other stuff)
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/tejado/pgoapi/issues/61#issuecomment-234618551, or mute the thread https://github.com/notifications/unsubscribe-auth/AIE7VXxYVnlA1VLDtIztOKAnBQ5Nor55ks5qYQpfgaJpZM4JRXSY .
@Nostrademous can you tell me what normalized_reticle_size
used for? and what is that value mean?
the normalized_reticle_size range is 1 - 1.950 right? spin_modifier 1 = true 0 = false normalized hit position = ??? 1 - x?