Bad Egg: Difference between revisions
Jump to navigation
Jump to search
Content added Content deleted
>Torchickens No edit summary |
>Torchickens No edit summary |
||
| Line 23: | Line 23: | ||
Unlike in the third generation of Pokémon games, as well as appearing when a Pokémon's checksum is found to be invalid, for unknown reasons Bad Eggs actually have their own defined identifier of 495 (1EF) in the species byte. Such a 'Pokémon' if encountered in the wild by the use of a [[game-altering device]] will have Splash as its only move but it has no defined data for its cry, hence it uses the cry of a Bulbasaur (the first valid Pokémon in the species byte). |
Unlike in the third generation of Pokémon games, as well as appearing when a Pokémon's checksum is found to be invalid, for unknown reasons Bad Eggs actually have their own defined identifier of 495 (1EF) in the species byte. Such a 'Pokémon' if encountered in the wild by the use of a [[game-altering device]] will have Splash as its only move but it has no defined data for its cry, hence it uses the cry of a Bulbasaur (the first valid Pokémon in the species byte). |
||
==Rumours of Nintendo using Bad Eggs to punish cheaters== |
|||
''Main article: [[Glitch Myths]]'' |
|||
It is notable that error handlers such as "Bad Egg" are sometimes misinterpretated as punishments from Nintendo for when players illegitimately (through the use of a [[game-altering device]]) change the stats of Pokémon. Whilst Nintendo have not responded on such matters and such claims have not fully been proved to be false, it would be more likely (considering quality assurance) that these messages were simply used as error handlers when the original Pokémon Ruby and Sapphire were in development. |
|||