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

[Feature Request]Minimum Pokemon based on candy #1289

Closed
wants to merge 1 commit into from
Closed

Conversation

Shibby7986
Copy link

Is it possible to add a feature that updates the minimum number of a Pokemon to keep based on the possible evolutions calculated by the amount of candy and the candy required per evolution.

The idea being that when lucky egg is active there is the correct ratio of Pokemon to candy for maximum evolution spam.

this spreadsheet may be helpful to explain further or pull data from.

Logic:
additionalCandy = currentCandy/candyToEvolve
posibleCandy = currentCandy+additionalCandy
PosibleCandy/candyForEvolve = Pokemon required
minimumPokemon += Pokemon required

@MiaoMFoo
Copy link

if the bot can add a function : move to a designated place!That will be even more perfect!
That is,if a location has a boss ,type the latitude and longitude spot to move there ,click the boss in to the fight but donnt catch it(throw the ball) right now,
back to the farm place, and then start capturing, because it will not be banned.

@Shibby7986
Copy link
Author

Shibby7986 commented Jul 28, 2016

Hey Maio,
That sounds useful however best if you create a separate request.

Also: checkout the snipe feature being worked on it may do what you are after

@MiaoMFoo
Copy link

the snipe feature is really cool!~~unfortunately I do not know programming,so ,only i can do is just await and thank for your jobs!

@maximegmd maximegmd closed this Jul 28, 2016
@NecronomiconCoding NecronomiconCoding deleted the develop branch July 30, 2016 15:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants