[X] My Assistant

[Breech Loader]

The numbers are getting out of hand - especially among the novelties. I like a live dex and I like to keep them in number order in my dexes.

So when the new Rotom came along, because numbers were full up on both sides it had to be split up. The Aloan pokemon are also ending up in Novelties numbers even though they're not. It's all getting rather out of order.

I know it might be a lot of work, but as we get more pokemon it becomes more work.

So are they going to be re-numbered?

[Letan]

Every Pokémon has an assigned unique ID, which is typically by dex number. When we started making Novelties these were shoved into an arbitrary ID far from the rest of the dex (note that at the time this was when the dex went up to 493). Since Alolan forms occupy the same ID in-game, we can't just shove them into the same ID as their original counterparts so they also got arbitrary IDs far from everything else. You can probably tell the rough ranges of these IDs if you paid close attention to new releases, but just because the dex lists the site as having 1140 Pokémon doesn't mean the IDs are currently 0-1139.

It's not an issue that can easily be remedied by going right click -> refactor -> change ID X to Y, it's a ton of work we don't have time for especially being a low priority task. Organize your living dex by your own discretion, it's a solid "no" to ever being fixed.

[Breech Loader]

*is disappointed*

The irony is that the real problem only really starts from 1000 onwards.

The problem will only get worse with the Aloan variations going in Novelties.

There are other things to do first - like the new pokemon, and whatever happens this Christmas. But it's gonna show up, if it hasn't done already.

[Cycloneblaze]

We're on 800 or so Pokémon now, and this kind of raises the question of what happens when dex numbers collide with index IDs on the site? When we get beyond 1000 Pokémon or however many. Will the site ID simply become disconnected from the real dex number? That's the cost of leaving the system as is; I suppose it's not that high a cost, I know I wouldn't care too much about it and I'm not asking for it to be fixed for that reason, but maybe it would move this up the priority order a bit.