by, 15th April 2013 at 11:24 AM (167 Views)
In this blog I would like to talk about glitch pokemon. As you probably already know, Missingno. style glitch pokemon are formed when you force the game to encounter a pokemon that does not have a valid index number. This was very easy to do in Gen 1 for several reasons, not the least of which is the fact that the index numbers are seemingly arbitrary, with many unassigned values.
In gen 2 this problem was mostly fixed since they made each pokemon , though the values 000, 252, 254 and 255 are still unassigned. The reason they went up to 255 even though there were only 251 is probably because they just used 8 bit unsigned integers to store the data, and the maximum value for an 8 bit unsigned integer is 255 (This is probably also why EVs max out at 255 in case that seemed arbitrary to you).
In later generations the problem is all but solved, except they still have the index value 000 unassigned, and I do not understand why. As long as you have an unassigned index value you have the opportunity for a glitch pokemon, so why not just start the index numbering at 000 instead of 001? Alternatively if they are too OCD to shift the entire numbering system by 1 (so the index number would be one less than the pokedex number) they could just fill the 000 slot with a super weak pokemon like sunkern or magikarp in order to troll hackers (we know how much GF likes to troll people).
Anyway, that's the end of the rant that no one will read. If anyone knows more about programming than I do and can give a legit reason why 000 should remain unassigned please let me know.
Total Trackbacks 0