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

Request to change "evolvable" calculation #422

Open
Thunda88 opened this issue Sep 24, 2016 · 5 comments
Open

Request to change "evolvable" calculation #422

Thunda88 opened this issue Sep 24, 2016 · 5 comments
Milestone

Comments

@Thunda88
Copy link

Hello, can we change the algorithm to calculate how many pokemon can be evolved. Instead of calculating the number based on candy given AFTER evolve and transfer, use something like this:

  1. total_amount_of_candies / number_of_candies_needed_to_evolve = number_of_evolutions (the remainder can be pulled as leftover_candies)
  2. leftover_candies + (total_number_of_pokemon - number_of_evolutions) = var (this variable will give us a number of how many leftover candies we have AND how many unusable (extra) pokemon we have)
  3. var / number_of_candies_needed_to_evolve = more_evolutions (if the result is greater than one it means we have more than one evolution ready just by transferring pokemon to candy, pull the whole number in this case)
  4. number_of_evolutions_displayed = number_of_evolutions + more_evolutions
    Sorry for this horrible pseudocode, never coded anything myself except in MATLAB in university.
@Wolfsblvt
Copy link
Owner

The problem is... I don't understand what you mean, sorry xD

The column right now exactly shows you how many Pokémon are evolvable with your current candy and current Pokémon of that type.
Your formula sounds complicated.
What exactly do you want to achieve with that?

@Thunda88
Copy link
Author

Okay, I suspected you would not understand it. Here's an example: you have 5 pidgeys and 20 candies. Right now the "evolvable" column will show 1. There is going to be 4 leftover pidgeys. If the program could count those in as candies then it would show me "evolvable:2" right away, although I did not transfer any pidgeys yet. The problem shows itself when you have a lot of those and you want to make preparations for pidgey farming. Like when I have 80 or so pidgey and it says "evolvable:30",right? I then remove all 50 extra pidgeys and when I'm done the operation it changes to "evolvable:34". But I already got rid of all extra pidgeys, so in the end I'm sitting with 30 pidgeys, 34 of which could be evolvable. So right now I have to watch how many pidgeys I get rid off. First I transfer lets say 47, wait for the batch to complete and see how much can be evolved. Then I transfer another one. And so on until I have a perfect balance like "34pidgeys in storage, 34 pidgeys evolvable". If we use my formula people can just select all pidgeys, see how many are going to be evolvable and delete the remaining.

@Wolfsblvt
Copy link
Owner

Okay, understood now.

I don't think it's a good idea to replace the column with the "new" calculation. Not everyone wants to transfer all his Pokémon just for evolve. I keep good IV pidgeys for example :P

Maybe I'll go with another column.

@Wolfsblvt Wolfsblvt added this to the v0.2.0 milestone Sep 24, 2016
@Thunda88
Copy link
Author

Thunda88 commented Sep 24, 2016

I keep the good ones too, but a good 60% of all pidgeys are trash so they are disposable. Anyway, thanks for considering this "new©" (patent pending) formula®.

@Wolfsblvt Wolfsblvt reopened this Sep 24, 2016
@FernandoTBarros
Copy link
Collaborator

The next release will have in Evolvable column: "Evolvable without transfer / Evolvable transfering"

@FernandoTBarros FernandoTBarros modified the milestones: v0.1.8, v0.3.0 Apr 9, 2017
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

3 participants