I think it'd be nice to actually document usecases. And if you did do it, I think it should be based on something like Metric 2 that takes into account the move stat and the damage formula. But that's a ton of work and I'd understand if you can't do it - lots of data to type/scrape and the OCR work to identify the moveset (especially when is also obscured). I'd be great if you could implement that. I'd really like something like a general score you did - but that'll need to include the movesets to be meaningful. So adding base stats just makes it annoying because you either lose that information because we round off the decimal places, or people have to start looking the decimal places (9.012 vs 9,1 - this is mentally more taxing). All the user wants to know in pokemon of the same species is that which one is better. What I mean by this is that, for a given species, the pokemon with the higher IV perfection is always going to be better than the one with the lower IV perfection. So, just looking at base stats is half way attempt and a misleading one (moveset could wipe out any benefit from IVs)Īnother problem with base stat is that for pokemon with same moveset, it's just making the difference between the IVs less visible without really helping the user make a different decision. Eg: Which of the different electric pokemon is more effective - so that you may transfer the weaker one or pick the stronger one for a battle. Which are way more important than even IV if you are trying to compare which one would be more effective. I was initially all for Metric 2 (as seem by my earlier comment in this issue).Īll the other metrics (other than the IV perfection we show today) are either attempting to allow the player to compare:īut the problem with all those metrics and attempts is that they try to include base stat but completely ignore the moveset stats. Tl dr: IVs should really be taken in the context of the 'mon's base stats to figure out how valuable one extra IV point would I was reading that reddit post earlier today too. I guess you'd have to average these displayed stats when there are multiple IV possibilities.
If the app had displayed "171 121 125" and "173 111 127" on the respective 'mons, my life would have been easier. But the app could easily display "Stats at lvl XX" on the screen it displays the CP, candy, and dust cost to get to XX. I had to futz with the stat and CP formulas for a while to work out the answer (I'm going with the high level, low IV% candidate). The Weepinbell has better IVs by far, but will take 30k more dust to level up. So I'm trying to compare these two pokemon and figure out which to evolve. It would have total stats on 173 111 127, for a CP of 2054. I've been saving up to evolve it to a Victrebel.īut yesterday I caught a Bellsprout with 62% IV perfection, 14 00 14, but once it's a Victrebel it will only take 56 candies and 64k dust to take it to level 30. After evolving to Victrebel, it will take 90 candies and 99.6k dust to get to level 30, when it will have total stats 171 121 125 or 170 121 125, for CP of 2104 or 2101. I have a Weepinbell with 80% IV perfection, either 12 13 11 or 11 14 11. Maybe I can help focus the discussion by giving an actual use case I went through yesterday, where a feature like this would have helped quite a lot. Im aware that you'll probably react to adding a weird proprietary value "general score", but I'd like to point out that there's no widely accepted comparison of power adopted by users, and this value has strong basis in how much power the pokemon actually has. I just made it because I think it can be worth discussing these values as an example. The above implementation is pure text, and is in no way an attempt to show how it could be designed visually. This stat is based on the "general score". This relates to what's requested in this issue, being able to compare how much difference the IVs actually do. The second thing shows how much better your pokemon is compared to if the pokemon had 0% ivs, and how much weaker it is compared to if it had 100% ivs. I created a proof of concept implementation that shows a new text box in the results, the information in the image is:įirst row "general score" - this is a score which can be used to compare different pokemon, it's simply the att * def * sta /10000
0 kommentar(er)
