Main Menu


Major Glitches

Glitches by Generation/Game


Useful Tools


Search Wiki


Item stack duplication glitch
 Page | Discussion | View source | History

From Glitch City Laboratories

(Redirected from Item Slot Duplication)
Jump to: navigation, search
Miscellaneous glitches of Pokémon Red and Blue and Pokémon Yellow

Cooltrainer move | Super Glitch | Surfing glitch | Statue behaviour glitch | ZZAZZ Glitch | Amazing Man | Stand on a Tree | Invisible PC | Evolving Raichu | Walking Pikachu happiness glitch (Yellow only) | Walking lag glitch | Transform into a Ditto | See a Ghost without a Silph Scope | Get stuck in a wall | Invisible Tree | Billʼs Secret Garden | Coastal Flooding | Evolve without an Evolution Stone | Walk on water | Super effective move AI flaw | Glitch battle systems | Item stack duplication glitch | Silph Co. PC Glitch | Trick Zone | Introduction Nidorino glitch | Mute the music in the Pokémon League | Walk around with only fainted Pokémon | Wild appeared! | Pokémon Tower Pokédex glitch | Partial trapping move link battle glitch | PP Reset Glitch | Substitute glitch | Focus Energy glitch | Recovery move glitch | Expanded item pack | Cable Club escape glitch

(view, talk, edit)

The item stack duplication glitch is a glitch in Pokémon Red, Blue and Pokémon Yellow. It is required for the item underflow glitch.

It allows the player to duplicate an item stack with 255 items (so that the player obtains another copy of that item x255) of any item to be held.

It is not to be confused with an item duplication glitch caused by encountering a Pokémon with an invalid Pokédex number, such as Missingno. and 'M (00)'s addition of 128 to the sixth item if there is less than 128 items there.


1) 255 of an item in a slot below the first item are needed.

In Pokémon Red and Blue, this is possible by using the old man glitch to encounter a Missingno. or 'M (00)| with an item in the sixth position that has a quantity less than 128.

From there, if the player originally had one of the item, they can use the item in battle to get 127 and capture Missingno. or 'M (00) to get 255 items in the sixth position. Alternatively, the player can end the battle, then toss one of the item (or whatever number needs to be tossed to get less than 128) to get 127 items in the sixth position, and then encounter another Missingno. or 'M (00).

In Pokémon Yellow, the player can still do this trick with a Yellow regular Missingno. encountered with the Ditto Trick, but a freeze is likely. It is more ideal to use a Kabutops Fossil (Special 182), a Aerodactyl Fossil (Special 183) or Pokémon Tower Ghost (Special 184) Missingno., which never freeze the game or cause any known side effects after being sent out from the opponent's side (though if the player sends one out then its backsprite will corrupt the Hall of Fame) other than duplicating the player's sixth item.

In Pokémon Red, Blue and Pokémon Yellow, the level 127 Missingno. variant of the TMTRAINER effect can be used to duplicate the player's sixth item if they catch it, but pulling this off may not work after a certain point in the player's game, so more reliably, but more slowly, the Cable Club escape glitch can be used in Red, Blue, Yellow to battle a Trainer with more than one Fossil or Ghost Missingno if the other player that 'player one' linked to had them.

The Cable Club escape glitch can also be used to encounter Missingno. This may be ideal in Pokémon Yellow if the player does not have the required Special stat for encountering a (Fossil or Ghost) Missingno. with the Ditto Trick, or if the level 127 Missingno. variant of the TMTRAINER effect is not working.

2) An item which is unimportant to the player in the slot directly below the item that the player has 255 of. This will be replaced with the item stack above it.


  1. Toss all of an item above the stack of 255 items.
  2. A copy of the stack of 255 items will appear above it. The player's number of items is decreased by 1, and items before and including the Cancel button are not shifted up, the item above the Cancel will act like Cancel.

The player's last item will become unusable, so it is ideal to use an item there that is not valuable (key items may be lost). This item can be deposited in the PC as PC items are not affected by the item stack duplication glitch.


This glitch can be used to make regular items function as Cancel, because the location of the Cancel button is not shifted up.

At memory address D31D (D31C in Yellow), the player's current number of items is stored. If the player had, say 09 items, the item at position 10 is selectable but not usable. Normally the Cancel button is always at [number of current items +1].

When the player tosses a stack of items above the stack of 255 items, although the player's number of items is decreased by 1, the items below it are not shifted up. Consider this example:

Before tossing the item:

Number of items: 09

  1. Master Ball x1
  2. Ultra Ball x255
  3. X Accuracy x96
  4. Hyper Potion x6
  5. X Attack x66
  6. Full Restore x2
  7. Full Heal x98
  8. Max Revive x5
  9. Poké Ball x1
  10. Cancel

After tossing the item:

Number of items: 08

  1. Ultra Ball x255
  2. Ultra Ball x255
  3. X Accuracy x96
  4. Hyper Potion x6
  5. X Attack x66
  6. Full Restore x2
  7. Full Heal x98
  8. Max Revive x5
  9. Poké Ball x1
  10. Cancel

Note that the Poké Ball x1 is at position 09, which is the player's new number of items +1, so the Poké Ball x1 is selectable but not usable, just like how Cancel is supposed to work.

Incidentally, if the Cancel button was usable (e.g. if it was at position 9 to begin with), it would act like TM55.

Buying an item (or otherwise adding an item to the player's inventory) will erase the item acting as the Cancel button as well as those underneath it. A normally functioning Cancel button will be directly below the bought item. This way, it is possible to erase unwanted key items and hard to toss glitch items.


  1. Faster duplication of items than encountering Missingno.
  2. Erasing unwanted key items and hard to toss glitch items.
  3. Item underflow glitch