Main Menu





Search Wiki


Pokémon cloning (Generation II)
 Page | Discussion | View source | History

From Glitch City Laboratories

Revision as of 20:24, 17 February 2019 by Bbbbbbbbba (talk | contribs) (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.)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Major glitches of the Pokémon series
"Core" glitch Variants and Consequences
Arbitrary code execution see template, remote, cart-swap, unintended ROM code execution
2x2 block encounter glitches Left-facing shore tile glitch (in-game trade shore encounter trick, old man trick, Trade link up shore encounter trick, Fight Safari Zone Pokémon trick)
99 item stack glitch ­
Bad clone glitch ????? party overloading (Type 0xD0 move glitch, ????? map corruption, Celebi trick, Celebi Egg trick, Shiny Celebi trick, glitch move map corruption, overloaded party map corruption, Glitch Unown (Glitch Unown map corruption) Duplicate key items glitch (infinite items and item creation, expanded Balls pocket (TM/HMs outside of the TM/HM pocket, Glitch Pokédex categories))
Berry glitch
Bug-Catching Contest data copy glitch (Japan only)
Ditto DV manipulation
Elite Four door glitch (Japan only)
Expanded party encounter table manipulation
Glitch City Safari Zone exit glitch, RAM manipulation
Glitch meta-map script activation (Generation I)
Infinite Master Balls (Colosseum)
Large storage box byte shift glitch storage box remaining HP glitch, maximum stat glitch
Item duplication glitch
Item stack duplication glitch Generation I expanded items pack (Glitch Rocket HQ maps, Map FE (English and non-English European Yellow), Map script pointer manipulation (arbitrary code execution, map script pointer item ball manipulation), Text pointer manipulation (arbitrary code execution, item ball manipulation, mart buffer overflow), Trainerless instant encounter glitch
Transform held item glitch (Japan only)
Mimic glitch (Japan only)
Out of bounds Glitch City (Generation II) Slowpoke Well out of bounds corruption (French version)
Lumiose City save glitch
Pikachu off-screen glitch Trainer corruption glitch
Pokémon merge glitch
Pomeg glitch Pomeg data corruption glitch
Roaming Pokémon encounter glitch
(Mimic) Transform Rage glitch
Select glitches (Japan only) Closed menu: Dokokashira door glitch (international), Fossil conversion glitch (international), Second type glitch, Skip to Level 100 glitch, Trainer mutation glitch, walk through walls (international) Special menu: Lift glitch, Badge describer glitch)
Sketch glitch
SRAM glitch (Generation I) 255 Pokémon glitch, send party Pokémon to a new game
SRAM glitches (Generation II) Mailbox glitches, Mystery Gift item corruption, Trainer House glitches
Surf down glitch Grass/rock Surfing glitch (Spanish/Italian only) (adaptions: Submerge glitch (international), 8 8 (0x7C) grass/rock surfing glitch (English Red/Blue))
Time Capsule exploit
Trainer escape glitch Death-warp, Mew Trick, Ditto Trick, Experience underflow glitch
Buffer overflow techniques Japanese unterminated name glitch item instant encounter glitch, LOL glitch, Rival LOL glitch, Instant LOL glitch, RAM LOL glitch, oobLG, blockoobLG, Instant encounter infinite chain glitch (LGFly)), Super Glitch (Generation I) (party remaining HP glitch), Super Glitch (Generation III), Text pointer manipulation mart buffer overflow glitch, CoolTrainer♀-type move, Double distort CoolTrainer♀ corruption, Yami Shop glitch
Walk through walls ledge method, museum guy method, Rival's effect, Select glitch method (international), Brock Through Walls
ZZAZZ glitch party Pokémon box data shift glitch

(view, talk, edit)
PRAMA Initiative a également une page sur Pokémon cloning (Generation II).
Bulbapedia also has an article about Pokémon cloning (Generation II).

The Pokémon cloning method in Generation II was among the first methods discovered and is arguably more well-known than the methods for Generation I.


  • A Pokémon Gold, Silver, or Crystal Version cartridge.
  • An empty Box on the PC.
  • A Box that isn't full.
  • Pokémon to be cloned.
  • Another Pokémon to keep in the party.


1. Save the game.

2. Deposit the Pokémon to be duplicated into a Box on the PC.


3. Switch to an empty box on the PC.


4. You will be prompted to save the game for changing the box. Choose "YES" to the prompts, but shut off the power three seconds after the game starts to say "SAVING...DO NOT TURN OFF THE POWER.".



When the game is turned back on, there should be the Pokémon deposited into the PC in your party, and it should also be in the Box where it was deposited.


Another possibility is that there will be two of the Pokémon in the Box. [clarification needed]


  • 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.


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.

Interrupting step 1 by resetting may result in the bad clone glitch, which is much harder to execute due to a smaller timing window.