What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

need help with keep best CP and IV setup

grampabob

Member
Joined
Nov 14, 2016
Messages
31
I'm trying to to understand this logic IMO it's not working right. It's keeping very low level pokemons with higher IV then high level pokemons with higher CP but slightly lower IV. Low level guys with good IV are useless and goto candies right away. I think it should look at level and CP first, keep the higher one then compare IV and ditch the lower IV.

for example a level 30 pokemon with 78 IV and high CP is WAY better then a level 18 pokemon with lower CP and 80 IV. You save WAY more stardust powering up the iv78 guy with a few less points, you would't even notice the difference in power BUT you would on your stardust count. Law of diminishing returns kinda..?

So help me tune my settings. I have the logic -- catch, keep 3 of highest CP and IV. IN my picture, I dont understand why the level 3 rattata, 60IV cp38 is still kept over some of the other guys.....??? It's just not right.

I'd like to tune so it keeps high level or CP first, then cuts out the lower IV second. How do I accomplish this? Thanks ansd hopefully my attachments are included

. logic.webp View attachment 2017-01-07_T16_14_37.txt
 
I just want to add the logic of taking IV first makes perfect sense if I was a low level trainer maybe 1-20 building up the pokemon inventory, but as a power user near end game, I really am only searching for pokemons around my same high level first with corresponding high CP, then filtering the highest IV of those choices. Maybe the logic needs a simple toggle switch, preference to checking IV or CP first or visa versa.
 
We are currently looking into this issue with the way it calculates.
 
Back
Top