Conceptually the ExtCPTier is a great idea, but the values change too much from patch to patch. Whenever there is a new Max CP Pokemon, every single Pokemon needs to be rescanned and to sort them would require rescanning your entire pokemon storage, which is slow and labor intensive. The max CP feature would sortof address this problem, but it takes up too many characters(4) and manually removing characters from the middle can be painful.
Suggested changes:
Reimplement ExtMaxCPTier to be based off of a new max value that had some headroom over the max Pokemon such that these recalibration/resorting events would be less common. No way around rescanning Pokemon that have their base stats changed, but it would at least minimize the number of wholesale changes.
(Alternative) Add a new zero padded 2 character Max CP that drops trailing two digits.
Conceptually the ExtCPTier is a great idea, but the values change too much from patch to patch. Whenever there is a new Max CP Pokemon, every single Pokemon needs to be rescanned and to sort them would require rescanning your entire pokemon storage, which is slow and labor intensive. The max CP feature would sortof address this problem, but it takes up too many characters(4) and manually removing characters from the middle can be painful.
Suggested changes: