18,955
edits
Bad Egg: Difference between revisions
m
Text replacement - "{{game|Black and White|s 2|Pokémon Black 2 and White 2}}" to "{{B2W2}}"
m (Text replacement - "/None|v=Sword|v2=Shield|t=FFF|t2=FFF|" to "/None|v=Sword|v2=Shield|") Tag: Manual revert |
m (Text replacement - "{{game|Black and White|s 2|Pokémon Black 2 and White 2}}" to "{{B2W2}}") |
||
| Line 8: | Line 8: | ||
All core series Pokémon games from Generation III onward, [[Pokémon Box Ruby & Sapphire]], and [[My Pokémon Ranch]], calculate a checksum over most of a Pokémon's data before storing it in an {{wp|Encryption|encrypted}} form. This checksum is stored in an unencrypted portion of the Pokémon data structure. When the games load a Pokémon's data, they decrypt it and recalculate the checksum over the decrypted data. This checksum is compared to the stored value, and if they do not match, the game sets the Bad Egg {{wp|Flag (programming)|flag}} located in an unencrypted portion of the Pokémon data structure. Other parts of the game check this value and treat the Pokémon as a Bad Egg as a result. The checksum can fail to match due to {{wp|data corruption}} (such as through [[glitch]]es, communication errors, failing {{wp|flash memory}}, or {{wp|Soft error|bit flips}}) or external modifications that alter a Pokémon's data without recalculating the checksum (such as through exploits, [[cheating]], or third-party tools). | All core series Pokémon games from Generation III onward, [[Pokémon Box Ruby & Sapphire]], and [[My Pokémon Ranch]], calculate a checksum over most of a Pokémon's data before storing it in an {{wp|Encryption|encrypted}} form. This checksum is stored in an unencrypted portion of the Pokémon data structure. When the games load a Pokémon's data, they decrypt it and recalculate the checksum over the decrypted data. This checksum is compared to the stored value, and if they do not match, the game sets the Bad Egg {{wp|Flag (programming)|flag}} located in an unencrypted portion of the Pokémon data structure. Other parts of the game check this value and treat the Pokémon as a Bad Egg as a result. The checksum can fail to match due to {{wp|data corruption}} (such as through [[glitch]]es, communication errors, failing {{wp|flash memory}}, or {{wp|Soft error|bit flips}}) or external modifications that alter a Pokémon's data without recalculating the checksum (such as through exploits, [[cheating]], or third-party tools). | ||
In {{ | In {{B2W2}}, Pokémon with an index number greater than 649 (such as [[Pokéstar Studios opponents]]) are marked as Bad Eggs if put in the player's [[party]]. In [[Pokémon: Let's Go, Pikachu! and Let's Go, Eevee!|Pokémon: Let's Go, Pikachu!, Let's Go, Eevee!]], and {{pkmn|Legends: Arceus}}, Pokémon with species, forms, or [[move]]s not coded into the game are marked as Bad Eggs. In [[Pokémon HOME]], Pokémon flagged by HOME's cheat detection are marked as Bad Eggs. | ||
In {{g|Colosseum}}, {{XD}}, and {{pkmn|Battle Revolution}}, checksums are not validated for any Pokémon stored on the game's save file, as Pokémon data is not encrypted by the game. However, they do display Pokémon with the Bad Egg flag in the [[Game Boy Advance]]/[[Nintendo DS]] games as Bad Eggs. Pokémon Colosseum and XD do not store a Pokémon's checksum at all, and will only calculate a checksum for a Pokémon when it is traded to the GBA games. Pokémon Battle Revolution additionally sets the Bad Egg flag on its copies of Pokémon with more than 510 [[effort values]] when they are copied from the handheld [[Generation IV]] games. | In {{g|Colosseum}}, {{XD}}, and {{pkmn|Battle Revolution}}, checksums are not validated for any Pokémon stored on the game's save file, as Pokémon data is not encrypted by the game. However, they do display Pokémon with the Bad Egg flag in the [[Game Boy Advance]]/[[Nintendo DS]] games as Bad Eggs. Pokémon Colosseum and XD do not store a Pokémon's checksum at all, and will only calculate a checksum for a Pokémon when it is traded to the GBA games. Pokémon Battle Revolution additionally sets the Bad Egg flag on its copies of Pokémon with more than 510 [[effort values]] when they are copied from the handheld [[Generation IV]] games. | ||