Bad Egg: Difference between revisions

{{Error traps}}

[[Image:Badegg_battlegeniii.png|270px|thumb|right|A [[glitch Pokémon]] with an invalid checksum after being labelled as a "Bad EGG" on Pokémon Ruby and Sapphire.]]

[[Image:Bad Egg.png|270px|thumb|right|A [[glitch Pokémon]] with a hexadecimal identifier of 1EF (495) using the error handler "Bad Egg" as its name, encountered in battle within Pokémon Diamond and Pearl.]]

 

The term "'''Bad EGG'''" in the [[bp:Generation III|Generation III]] Pokémon games and later "'''Bad Egg'''" in the [[bp:Generation IV|Generation IV]] games, refers to an error handler which was presumably, originally used by the game developers to refer to individual Pokémon (as eggs) with [[bp:stats|stats]] which do not conform to the original defined data of that Pokémon for when it should hatch such as the [[bp:individual values|individual values]], [[bp:base statistics|base stats]] and [[bp:ability|ability]] of that Pokémon. For example, of an egg which was illegitimately (without writing to the checksum) given an excessively large attack stat for when it should hatch. Normally, when a player recieves an egg, the game should write to the checksum by using an algorithm to calculate the total of {{Explain|unencrypted|In this case, not protected by XOR}} Pokémon data. If the game later considers the checksum to be invalid, i.e. if it is greater or lower than a possible value based on [[wikipedia:XOR|XOR]] calculations (perhaps if the EV total is greater than 510) the game will interpret the Egg as a "Bad Egg".