61
edits
Bad Egg: Difference between revisions
I highly doubt that
Breawycker (talk | contribs) m (→Generation IV) |
(I highly doubt that) |
||
| Line 21: | Line 21: | ||
===Generation IV=== | ===Generation IV=== | ||
It is possible to encounter a bad egg in the wild by using an [[Action Replay]] on {{game2|Diamond|Pearl|Platinum}} and setting the wild Pokémon modifier code to 495 (normal eggs appear for 494). The game will freeze instantly on capture when the game attempts to show the Pokédex entry. A normal egg captured in this way will hatch into a random Pokémon, including Pokémon that do not normally hatch from eggs like [[legendary Pokémon]] and evolved Pokémon, or may hatch into [[DPBox]] or, like its [[Glitch egg|Generation II counterpart]], another egg (which will then go on to hatch into a DPBox itself). Due to being incorrectly generated, whatever is hatched may eventually turn into a bad egg itself, and then subsequently hatch yet again. | It is possible to encounter a bad egg in the wild by using an [[Action Replay]] on {{game2|Diamond|Pearl|Platinum}} and setting the wild Pokémon modifier code to 495 (normal eggs appear for 494). The game will freeze instantly on capture when the game attempts to show the Pokédex entry. A normal egg captured in this way will hatch into a random Pokémon, including Pokémon that do not normally hatch from eggs like [[legendary Pokémon]] and evolved Pokémon, or may hatch into [[DPBox]] or, like its [[Glitch egg|Generation II counterpart]], another egg (which will then go on to hatch into a DPBox itself). Due to being incorrectly generated, whatever is hatched may eventually turn into a bad egg itself, and then subsequently hatch yet again. | ||
The same issues with regards to capturing Trainers' Pokémon and double battles remain in play in Generation IV, with bad eggs popping up in the same situations. | The same issues with regards to capturing Trainers' Pokémon and double battles remain in play in Generation IV, with bad eggs popping up in the same situations. | ||