Jump to content

Pokémon cloning (Generation II): Difference between revisions

m
Text replacement - "~" to "–"
>Bbbbbbbbba
(Added explanation and changed things. I don't think the original method as written is doable, since saving the game correctly when changing the box would update the party already.)
m (Text replacement - "~" to "–")
Line 44:
If the game is reset after step 1 has finished but before step 3 starts, then the contents of the active box is updated, but the party (a part of the main game data) is not, resulting in Pokémon cloning.
 
Although the save file is protected by a 16-bit checksum and a backup copy, they only apply to the main game data, so this glitch is not prevented. Furthermore, this means that even if step 3 has started, as long as the game hasn't finished writing the main save file, the main save file would likely be detected as corrupt and the backup would be used instead, resulting in successful cloning anyway. On the Crystal version, the timing window to get good clones is about 9~109–10 frames, making the glitch relatively easy to execute. <!-- TODO: What about G/S? -->
 
Interrupting step 1 by resetting may result in the [[bad clone glitch]], which is much harder to execute due to a smaller timing window.
Cookies help us deliver our services. By using our services, you agree to our use of cookies.