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

Keep # Pokemon based on Candy on hand #1973

Closed
k4n30 opened this issue Jul 31, 2016 · 8 comments
Closed

Keep # Pokemon based on Candy on hand #1973

k4n30 opened this issue Jul 31, 2016 · 8 comments

Comments

@k4n30
Copy link
Contributor

k4n30 commented Jul 31, 2016

#1395 brought the functionality of keeping Pokemon based on CP or IV
#1472 brought the ability to release based on BOTH

New feature requested:

Add an additional check based on candy amount (global on/off - configurable in config) that allows you to keep Pokemon based on the number of candy.

eg.

  1. Pidgey requires 12 candy to evolve and you currently have 118 pidgey candy, and 9 pidgey's in your Pokemon bag
  2. You capture a new pidgey (taking candy to 121, and pidgeys in your bag to 10)
  3. The release config has something like
    "Pidgey": {"keep_best_cp": 2, "keep_best_iv": 3, "keep_candy_evolution_ratio" : true}
  4. The config would also have a "keep Pokemon for lucky egg mass evolve spree" true/false field set to true
  5. The new pidgey is NOT released due to keeping the candy to evolution ratio

This would be useful for when it came time to drop a lucky egg and do the mass evolving, but if you didn't actually have the right ratio of Pokemon to candy on hand, the lucky egg would be wasted (or run out before finding enough to evolve)

@k4n30
Copy link
Contributor Author

k4n30 commented Jul 31, 2016

#1972 - Seems we both had the same idea at the same time :p

@HecticSeptic
Copy link

Indeed, uncanny. It's the same suggestion.

@slatspie
Copy link

This would be a handy feature. I mentioned it in #1528 a couple days ago too.

@TheSavior
Copy link
Contributor

I think this is a great feature. New workers are appreciated

@nanogirl21
Copy link

I would love this

@k4n30
Copy link
Contributor Author

k4n30 commented Jul 31, 2016

@MFizz - any chance?

@k4n30
Copy link
Contributor Author

k4n30 commented Aug 1, 2016

#394 another issue with the same request.

All the issues need to be cleaned up and consolidated

@TheSavior
Copy link
Contributor

@k4n30 Thanks for pointing that out. Closing this as a duplicate of #394.

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

No branches or pull requests

6 participants