Bad Egg: Difference between revisions

Line 4:

[[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".

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 algorithms suggesting what stats that Pokémon should have, 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".

However, since after [[bp:Generation II|Generation II]] Pokémon in one sense are simply eggs with an additional byte with a value of 01 (ON) it is possible that a hatched Pokémon would also be taken by the game as a 'Bad Egg', which could suggest that the game developers did not expect other game developers to accidentally invalidate the checksum of a gift Pokémon with variable characteristics for example.

@@ Line 4: / Line 4: @@
 [[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".
+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 algorithms suggesting what stats that Pokémon should have, 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".
 However, since after [[bp:Generation II|Generation II]] Pokémon in one sense are simply eggs with an additional byte with a value of 01 (ON) it is possible that a hatched Pokémon would also be taken by the game as a 'Bad Egg', which could suggest that the game developers did not expect other game developers to accidentally invalidate the checksum of a gift Pokémon with variable characteristics for example.

Bad Egg: Difference between revisions

Navigation menu

Search