Skip to content
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

Add simple nearby pokemon hunter cellworker (+ radar output feature) #2453

Closed
wants to merge 5 commits into from

Conversation

z4ppy
Copy link
Contributor

@z4ppy z4ppy commented Aug 3, 2016

Generate simple search path and run it when pokemons are nearby bot (config : vips, count).
Can output the game radar (option)

TODO

  • better search path
  • an algorithm to approximate Pokemon vips
  • handle vip or better place to hunt meanwhile started search (reinit)
  • more options (start when no move, lures camping, bag full, ...)
  • PokemonMap Synergie : vips position deduction (encounter_id)

@z4ppy z4ppy changed the title Add simple nearby pokemon hunter cellworker Add simple nearby pokemon hunter cellworker (+ radar output feature) Aug 3, 2016
@douglascamata
Copy link
Member

There's already a task to snipe pokemons based on PokemonMap.

This PRs has too much output, please only log as little as possible and only actions that are really necessary to be logged.

@Tych0n
Copy link

Tych0n commented Aug 3, 2016

@z4ppy, in #1992 script loads data from https://github.com/AHAAAAAAA/PokemonGo-Map and tries to catch pokemons by simple logic and some hacks. But if you will add your path ideas or may be some sort of "best route", that helps to visit maximum amount of visible pokemons before they vanish using "Traveling Salesman Problem" algorythms - that would be great.

@z4ppy
Copy link
Contributor Author

z4ppy commented Aug 3, 2016

Fixed: log & snail speed

@elicwhite
Copy link
Contributor

I'm not sure why this task looks like it does so many things. Catching pokemon should be separate from movement. What does this do that the other tasks don't do?

@k4n30
Copy link
Contributor

k4n30 commented Aug 14, 2016

@z4ppy this merge is severly outdated. How do you want to proceed?

@solderzzc
Copy link
Contributor

Outdate, need close. Thanks for PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants