IVs changed after stat rebalance? Or just a poor use of an IV calc before?
So after the stat rebalance I was updating my Pokemon IV and stat database just as needed (i.e. after getting a new 'mon to compare it to the ones I already have, or after powering up), and there was no major issue other than updating CP and Stats.
But now after the announcement of PVP mechanics, I decided to formally update my database for all 'mons over 1000 CP (a huge task if you want to know), but I've been encountering that some of my previous IVs don't match. For example, according to my database, pre-stat rebalance I had a 2601 CP LV32 86.7% Espeon with A15D12S12; after the rebalance it changed to 2747 CP and when I use the IV calculator it now gives me 4 possible combinations: two LV32 82.2%, one LV31.5 88.9%, and a LV31 91.1%, none of them matching the previous IVs.
Has anyone else noticed a change in your Pokemon's IVs after stat rebalance? Or it just might be that I picked the wrong calculator/wrong combination the previous time?
Answers
I've done this, so perhaps it's the same problem for you.
If the IV stat calculator gives multiple combinations and I don't plan to power up to refine it, I just write in the average.
In your case, that Flareon may have shown one of the 82.2% options and the 91.1% option, so you record the average of 86.7%. After the CP rebalance there are now even more options, but given your prior knowledge of this you'd know the 88.9% option is impossible.
I generally did this because there wasn't room to name pokemon + moveset + two IV options. So I always just used the average if multiple were possible.
Do you indicate in any way that you are writing one of many possible results? It could easily be that the previous set of formulas had one possible outcome that is not a possible outcome with the new set of formulas.
For example, when I previously wrote my IVs in hexadecimal, I would use capitals for known exact values like "FDC" for 15/13/12. I would use lower case for averaged imprecise values (usually choosing one possibility if able, but not always) like "Fdc" for a set where atk IV was known to be 15, but def and stm IVs had multiple combinations that averaged to 13 and 12. Values less than 10, if they were a rare enough pokemon for me to care about would require some other marker to indicate it was imprecise like "9B7~", but then I would not know whether the 9 or the 7 or both was imprecise, just that at least one was.
When I started I use the PokeKeys keyboard on iPhone, I could use the different colored number circles to encode this previous info better. I use white for known values and black for average or lowest between two values: ⑮⑬⑫, ⑮⓭⓬, ⑨⑪❼
