Anonymous user
Pokémon cloning (Generation II): Difference between revisions
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.
>Sherkel No edit summary |
>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.) |
||
Line 8:
* A Box that isn't full.
* Pokémon to be cloned.
* Another
==Procedure==
1. Save the game.
1. Deposit the Pokémon to be duplicated into a Box on the PC.▼
[[Image:Gscclone1.png]]
[[Image:Gscclone2.png]]
[[image:Gscclone3.png]]
Line 28 ⟶ 30:
[[Image:Gscclone4.png]]
Another possibility is that there will be two of the Pokémon in the Box. {{clarify}}
==Notes==
* Up to 5 Pokémon can be duplicated at a time under normal circumstances.
* Items can be duplicated this way by making the cloned Pokémon hold the item to be cloned.
* This can possibly damage the PC, and cause Pokémon to disappear. Details on this and why this can happen is not known.
==Explanation==
Saving the game for changing the box is handled a little differently than saving the game normally. It consists of three steps:
* The contents of the active box (before changing) is saved to the SRAM.
* The number of the active box changes, and the contents of the new box is loaded from the SRAM.
* The game is saved as normal.
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~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.
[[Category:Generation II glitches]]
| |||