Bad Egg: Difference between revisions
>Torchickens No edit summary |
>Torchickens |
||
| (28 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
{{Error traps}} |
{{Error traps}} |
||
{{Summary page}} |
{{Summary page}} |
||
{{Bulbapedia}} |
|||
[[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: |
[[Image:Badegg_battlegeniii.png|270px|thumb|right|A [[glitch Pokémon]] with an invalid checksum after being labelled as a "Bad EGG" in Pokémon Ruby and Sapphire.]] |
||
"'''Bad EGGs'''" (Japanese: ダメタマゴ), as they are known in the [[bp:Generation III|Generation III]] Pokémon games and later "'''Bad Egg'''" in the [[bp:Generation IV|Generation IV]] games are error handlers. |
|||
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. |
|||
In Generation III, they appear for Pokémon that do not have a correct checksum value (which is stored in its own byte). The checksum is computed by adding all unencrypted values of the 'data' section of the [[bp:Pokémon data structure in Generation III|Pokémon data structure]] one [[word]] (two bytes) at a time. If the actual checksum does not match the checksum value, the Pokémon will be interpreted as a Bad EGG, and if a hex:0000 [[??????????]] was interpreted as a Bad EGG, it will appear as a Bad EGG with an invisible icon. |
|||
Simply changing the personality value of a Pokémon rather than its [[bp:Pokémon data substructures in Generation III|data]] substructures can also turn Pokémon into Bad EGGs, probably due to the substructure order being changed due to a different modulo value. For this reason, it is possible to obtain Bad EGGs without cheating in Pokémon Emerald and Pokémon FireRed and LeafGreen using the [[Pomeg data corruption glitch]]. |
|||
| ⚫ | Like ordinary |
||
| ⚫ | Like ordinary Eggs, Bad EGGs in Generation III under normal circumstances can never be released, however, they can be released with the [[inverse cloning glitch]]. When the player attempts to view a Bad EGG's summary screen the game will not give the details of the Pokémon inside but rather, the game will bring up an 'Egg' summary screen, showing its 'state' (an indicator of how long it'll take to hatch the Egg) and 'trainer memo' (origin). |
||
| ⚫ | |||
Regardless of what the trainer memo says, a Bad EGG will never hatch; only a normal Egg can hatch. {{fact}} |
|||
[[Image:BadEggPBR.png|270px|thumb|right|A Bad Egg being defeated by a [[bp:Chimchar|Chimchar]] in Pokémon Battle Revolution. Note the distinctive brown spots instead of the usual green.]] |
|||
A Bad Egg may also be seen during {{RS}}'s version of the [[switch glitch (Generation III)|switch glitch]] or be caught with the [[roaming Pokémon encounter glitch]]. |
|||
It is notable that the error handler "Bad EGG", or "Bad Egg" is still used in Pokémon Colosseum, Pokémon XD and Pokémon Battle Revolution; despite the fact that eggs alone are normally unobtainable within these games. For this reason, it could be suggested that it is used simply so that the game does not crash. Furthermore, Eggs and Bad Eggs even use their own unique models and strangely appear as eggs with brown spots instead of the usual green. In Pokémon Battle Revolution, unless the player turns the narration off the game will crash when a Bad Egg is sent into battle as such data is undefined. |
|||
Though the validity of this happening without cheats is unknown, there is also [https://www.youtube.com/watch?v=fqbG7YitDhw a report of another Bad Egg glitch in FireRed/LeafGreen]. |
|||
{{clr}} |
|||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
Bad Eggs appear in Pokémon Battle Revolution. |
|||
Unless the player turns the narrations off the game will lockup when a Bad Egg is sent into battle, probably because there is no voice file for announcing the Bad Egg's name.{{fact}} |
|||
| ⚫ | |||
==In Generation IV== |
|||
===As a Pokémon species=== |
===As a Pokémon species=== |
||
| ⚫ | |||
Main article: [[GlitchDex/DP:495]] |
|||
[[File:BadEgg.png]] |
|||
A [[glitch Pokémon]] in {{DP}} with an [[identifier|index number]] of 495 (hex:1EF), known as "Bad Egg". |
|||
"Bad Egg" is also mentioned in the [[trapping Ability flee glitch]] in {{Platinum}} if the player attempts to flee when the right side wild Pokémon has fainted (requires a Steel-type Pokémon on the user's side for Magnet Pull to prevent fleeing). |
|||
{{clr}} |
|||
| ⚫ | Unlike in the third generation of Pokémon games, |
||
==In Generation V== |
|||
==Rumours of Nintendo using Bad Eggs to punish cheaters== |
|||
Bad Eggs can be found in [[bp:Generation V|Generation V]]. |
|||
==In Generation VI== |
|||
''Main article: [[Glitch Myths]]'' |
|||
[[File:Bad Egg XY.png|thumb|right|250px|A 'Bad Egg' in an online battle]] |
|||
Bad Eggs apparently exist in {{XY}} ([https://twitter.com/CentroPokemon/status/499032246964060160 source]). |
|||
They are not to be confused with '[[Mystery Egg glitch|mystery Eggs]]' (they are not actually called this, they are just referred to as Eggs). Mystery Eggs marked as originating from the Mystery Zone have appeared in the PC boxes of some players of Pokémon X and Y. They also have an obtained date of '0/0/2000'. |
|||
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. |
|||
{{clr}} |
|||
[[Category:Generation III glitch Pokémon]] |
|||
[[Category:Generation IV glitch Pokémon]] |
|||
[[Category:Generation V glitch Pokémon]] |
|||
[[Category:Generation VI glitch Pokémon]] |
|||
[[Category:Glitch Pokémon]] |
|||
Latest revision as of 23:27, 6 December 2018
?????????? | ????? | ! | Abnormal Pokémon | Bad Egg | Enigma Berry (Generation III) | Error! | Error codes (Generations I and II) | Error traps for damaged save data | Error traps to prevent impossible progress | Event data debugging messages | Instant victory effect (Generation II) | Mystery Zone | N/A | Pokégear instruction booklet trap | Rhydon trap | Special (location) | This Game Pak is designed only for use on the Game Boy Color. | This Pokémon cannot be traded.
This article is a summary page for different variations of a glitches, etc. when talked about as a whole.
|
| Bulbapedia also has an article about Bad Egg. |
"Bad EGGs" (Japanese: ダメタマゴ), as they are known in the Generation III Pokémon games and later "Bad Egg" in the Generation IV games are error handlers.
In Generation III
In Generation III, they appear for Pokémon that do not have a correct checksum value (which is stored in its own byte). The checksum is computed by adding all unencrypted values of the 'data' section of the Pokémon data structure one word (two bytes) at a time. If the actual checksum does not match the checksum value, the Pokémon will be interpreted as a Bad EGG, and if a hex:0000 ?????????? was interpreted as a Bad EGG, it will appear as a Bad EGG with an invisible icon.
Simply changing the personality value of a Pokémon rather than its data substructures can also turn Pokémon into Bad EGGs, probably due to the substructure order being changed due to a different modulo value. For this reason, it is possible to obtain Bad EGGs without cheating in Pokémon Emerald and Pokémon FireRed and LeafGreen using the Pomeg data corruption glitch.
Like ordinary Eggs, Bad EGGs in Generation III under normal circumstances can never be released, however, they can be released with the inverse cloning glitch. When the player attempts to view a Bad EGG's summary screen the game will not give the details of the Pokémon inside but rather, the game will bring up an 'Egg' summary screen, showing its 'state' (an indicator of how long it'll take to hatch the Egg) and 'trainer memo' (origin).
Regardless of what the trainer memo says, a Bad EGG will never hatch; only a normal Egg can hatch. [citation needed]
A Bad Egg may also be seen during Pokémon Ruby and Sapphire's version of the switch glitch or be caught with the roaming Pokémon encounter glitch. Though the validity of this happening without cheats is unknown, there is also a report of another Bad Egg glitch in FireRed/LeafGreen.
In non handheld Pokémon games
Bad Eggs appear in Pokémon Battle Revolution.
Unless the player turns the narrations off the game will lockup when a Bad Egg is sent into battle, probably because there is no voice file for announcing the Bad Egg's name.[citation needed]
Reportedly, if a Pokémon with an EV total greater than 510 is uploaded on to Pokémon Battle Revolution, the game will regard that Pokémon as a Bad Egg.[citation needed]
In Generation IV
As a Pokémon species
Unlike in the third generation of Pokémon games, Bad Eggs actually have their own defined identifier of 495 (1EF) for a Pokémon species. If such a 'Pokémon' if encountered in the wild by the use of a cheating device, it will have Splash as its only move.
A glitch Pokémon in Pokémon Diamond and Pearl with an index number of 495 (hex:1EF), known as "Bad Egg".
"Bad Egg" is also mentioned in the trapping Ability flee glitch in Pokémon Platinum if the player attempts to flee when the right side wild Pokémon has fainted (requires a Steel-type Pokémon on the user's side for Magnet Pull to prevent fleeing).
In Generation V
Bad Eggs can be found in Generation V.
In Generation VI
Bad Eggs apparently exist in Pokémon X and Y (source).
They are not to be confused with 'mystery Eggs' (they are not actually called this, they are just referred to as Eggs). Mystery Eggs marked as originating from the Mystery Zone have appeared in the PC boxes of some players of Pokémon X and Y. They also have an obtained date of '0/0/2000'.