List of cloning glitches: Difference between revisions

m
m (→‎Pokéwalker: nope, trading the original doesn't stop the game from deleting the clone. Damn :P)
Line 5: Line 5:


===Trading method===
===Trading method===
The cloning glitch most popular in [[Generation I]] involves the interruption of the trading process. As [[link cable]]s for the [[Game Boy]] are unable to send and receive data simultaneously, one game cart first sends its traded Pokémon's data while the other receives it, and then viceversa for the second traded Pokémon. Interrupting the trade after one Pokémon was sent and the other wasn't causes the first Pokémon to be present on both games and the second one not present on either, essentially making two of the same Pokémon while making the other disappear. The interruption can be either accidental - because of dirty connectors or damaged link cables - or on purpose - by disconnecting the link cable or turning the Game Boy off.
The cloning glitch most popular in [[Generation I]] involves the interruption of the trading process. As [[link cable]]s for the [[Game Boy]] are unable to send and receive data simultaneously, one game card first sends its traded Pokémon's data while the other receives it, and then viceversa for the second traded Pokémon. Interrupting the trade after one Pokémon was sent and the other wasn't causes the first Pokémon to be present on both games and the second one not present on either, essentially making two of the same Pokémon while making the other disappear. The interruption can be either accidental - because of dirty connectors or damaged link cables - or on purpose - by disconnecting the link cable or turning the Game Boy off.


In the Generation I games, this glitch is potentially very hazardous to the save file, because in the period of time between sending and receiving a Pokémon (or viceversa) the game saves the player's party. If the glitch is performed wrong and the game has not finished saving, the saved data will be corrupted. In [[Generation II]] this process was changed, and thus this method is not hazardous for the save file.  
In the Generation I games, this glitch is potentially very hazardous to the save file, because in the period of time between sending and receiving a Pokémon (or viceversa) the game saves the player's party. If the glitch is performed wrong and the game has not finished saving, the saved data will be corrupted. In Generation II this process was changed, and thus this method is not hazardous for the save file.


===Storage system method===
===Storage system method===
8

edits