The Glitchhouse · Pokemon Red, Blue and Yellow

Super Glitch and every glitch move in Red, Blue and Yellow

Super Glitch is what happens in Pokemon Red, Blue and Yellow when the game has to show one of the 30 glitch moves that have no name, 0xA6 to 0xC3: it reads a name from past the end of its move-name list, out of whatever memory holds, and that copy can run on until it wrecks your party. Here is every one of the 91 glitch moves, run in the game's own code, with what each does and which ones crash.

By GardenFlouer · every glitch move run in the game's own code in an emulator, 31 October 2026 · part of The Glitchhouse

The short answer. A Super Glitch is one of the 30 glitch moves 0xA6 to 0xC3 (166 to 195) in Pokemon Red, Blue and Yellow. The game has no names for them, so it reads each name past the end of its move-name list, out of whatever memory holds, and copying that name can run on and write over memory. In my tests, opening FIGHT with 0xA6 crashed all three games. The glitch moves after them, 0xC4 to 0xFF, are named HM01 to HM05 and TM01 to TM55 by a bug in the name routine, so their names are fixed and safe, although a few of them still crash or lock up the game when used.

Jump to every glitch move · Download the data

Every move in Pokemon Red and Blue has a name, and the game prints it with a simple copy: find the name, copy letters until the end marker, stop. There are 165 real moves, and the 165th, Struggle, is the last one with a name. The move numbers right after it have none: IDs 166 to 195, hex $A6 to $C3, the Super Glitch band. Ask the game to show one, and it goes looking for a name that was never written, takes whatever it finds as letters, and keeps copying until it happens across an end marker somewhere in memory. That runaway copy is Super Glitch. The rest of each move, its power, type and effect, is not random at all. It is read from the base stats of the first Pokemon in the Pokedex.

Every glitch move in Red, Blue and Yellow

A move slot in these games is one byte, so it can hold 256 numbers, and only 1 to 165 are real moves. The other 91, 0x00 and 0xA6 to 0xFF, are the glitch moves. I ran each one in each game, from the same battle, and this is what the game did. Red and Blue hold the same bytes for all 91, so they share a table; Yellow differs on 33 of them.

Pokemon Red and Blue: every glitch move, 0x00 and 0xA6 to 0xFF. Red and Blue hold the same bytes; where their test battles ended differently, the row says so.
MoveNameAnimEffectPowerTypeAcc.PPWhat it doesIn my testsBattler
0x00 0none (dashes)90$74102$7A8013The empty move: with it first, FIGHT shows only dashes, yet A picks it. Then: damage, then a jump past the effect table into other codeFreezes A foe whose only move is 0x00 freezes the game choosing a move.builder, slot 1
0xA6 16620 zero bytes1$2D49$31451 +1 upActs as Jump Kick, the effect of Jump Kick and Hi Jump KickCrashes Opening FIGHT crashes the game (its name). The foe using it crashes the game (its name).Try it
0xA7 167from memory22$0345$40850 never pickableActs as drain HP, the effect of Absorb, Mega Drain and Leech LifeNo crash seen0 PP
0xA8 168from memory64$E564$21450 never pickableDamage, then a jump past the effect table into other codeCrashes Red: Opening FIGHT crashes the game (its name). The foe using it crashes the game (its name). Blue: Opening FIGHT crashes the game (its name). Its effect locks up the CPU when a foe uses it, even with its name kept short.0 PP
0xA9 169from memory0$03164$03 Poison560 +3 up never pickableActs as drain HP, the effect of Absorb, Mega Drain and Leech LifeCrashes Opening FIGHT crashes the game (its name). The foe using it crashes the game (its name).0 PP
0xAA 170from memory3$086$00 Normal260Acts as Dream Eater, the effect of Dream EaterCrashes Opening FIGHT freezes the game (its name). The foe using it crashes the game (its name).Try it
0xAB 171from memory62$3F60$50223Acts as evasion down 2, an effect no real move hasNo crash seenTry it
0xAC 172from memory45$8D102$2B8023 +1 upDamage, then Special up 1's code runs with the wrong byte ($8D): the stat code reads past its stat tableCrashes Opening FIGHT crashes the game (its name). The foe using it crashes the game (its name).Try it
0xAD 173from memory81$2145$4903Acts as may poison, the effect of Smog and SludgeNo crash seenTry it
0xAE 174from memory164$0356$C038Acts as drain HP, the effect of Absorb, Mega Drain and Leech LifeNo crash seenTry it
0xAF 175from memory6$003$508219 +1 upDamage onlyNo crash seenTry it
0xB0 176from memory80$6422$03 Poison4516 +3 upDamage, then a jump past the effect table into other codeCrashes Opening FIGHT crashes the game (its name). The foe using it crashes the game (its name).Try it
0xB1 177from memory119$6265$976733Damage, then a jump past the effect table into other codeCrashes Red: Opening FIGHT crashes the game (its name). Its effect locks up the CPU for you and the foe, even with its name kept short. Blue: Opening FIGHT crashes the game (its name). Its effect locks up the CPU when the foe uses it, even with its name kept short.Try it
0xB2 178from memory45$4922$03 Poison1643 +1 upActs as unused effect $49, an effect no real move hasCrashes Opening FIGHT crashes the game (its name). The foe using it crashes the game (its name).Try it
0xB3 179from memory56$C03$08 Ghost60 never pickableDamage, then Light Screen's code runs with the wrong byte ($C0)Crashes The foe using it crashes the game (its name).0 PP
0xB4 180from memory4$2752$2B6550Acts as charge, then attack, the effect of Razor Wind, Solarbeam and othersCrashes Opening FIGHT crashes the game (its name). Its status screen (page 2) softlocks the game.Try it
0xB5 181from memory20$1445$418528 +1 upActs as Speed down 1, the effect of String ShotCrashes Opening FIGHT freezes the game (its name). The foe using it crashes the game (its name).Try it
0xB6 182from memory92$5C93$0A450 never pickableDamage, then a jump past the effect table into other codeCrashes Opening FIGHT freezes the game (its name). The foe using it crashes the game (its name).0 PP
0xB7 183from memory0$03181$03 Poison798 +3 upActs as drain HP, the effect of Absorb, Mega Drain and Leech LifeCrashes Opening FIGHT crashes the game (its name). The foe using it crashes the game (its name).Try it
0xB8 184from memory227$0838$00 Normal558Acts as Dream Eater, the effect of Dream EaterNo crash seenTry it
0xB9 185from memory64$3A80$412020Acts as Attack down 2, an effect no real move hasCrashes The foe using it crashes the game (its name).Try it
0xBA 186from memory45$8E102$0C958 +1 upDamage, then accuracy up 1's code runs with the wrong byte ($8E): the stat code reads past its stat tableCrashes The foe using it crashes the game (its name).Try it
0xBB 187from memory96$0A45$3403Acts as Attack up 1, the effect of Meditate and SharpenCrashes Opening FIGHT crashes the game (its name).Try it
0xBC 188from memory181$0379$C82278Acts as drain HP, the effect of Absorb, Mega Drain and Leech LifeCrashes Using it crashes the game (its name).Try it
0xBD 189from memory38$006$4E8414 +1 upDamage onlyNo crash seenTry it
0xBE 190from memory100$5520$02 Flying4517 +3 upActs as Splash, the effect of SplashCrashes Using it crashes the game (its name). The foe using it crashes the game (its name).Try it
0xBF 191from memory119$8698$9510010Damage, then may paralyze's code runs with the wrong byte ($86)No crash seenTry it
0xC0 192from memory45$3443$03 Poison1813 +1 upActs as Speed up 2, the effect of AgilityCrashes Opening FIGHT crashes the game (its name).Try it
0xC1 193from memory79$CE227$08 Ghost380 never pickableDamage, then unused effect $4E's code runs with the wrong byte ($CE): that table entry is empty, so the game jumps to address $0000Crashes Opening FIGHT crashes the game (its name).0 PP
0xC2 194from memory7$2C48$414350Acts as hit twice, the effect of Double Kick and BonemerangCrashes Opening FIGHT crashes the game (its name).Try it
0xC3 195from memory21$1545$428556 +2 upActs as Special down 1, an effect no real move hasCrashes The foe using it crashes the game (its name).Try it
0xC4 196HM0193$8F94$21390 never pickableDamage, then evasion up 1's code runs with the wrong byte ($8F): the stat code reads past its stat tableNo crash seen0 PP
0xC5 197HM020$03177$3F158 +3 upActs as drain HP, the effect of Absorb, Mega Drain and Leech LifeNo crash seenTry it
0xC6 198HM03131$0850$00 Normal859Acts as Dream Eater, the effect of Dream EaterNo crash seenTry it
0xC7 199HM0463$5058$412121Acts as Hyper Beam's recharge, the effect of Hyper BeamNo crash seenTry it
0xC8 200HM0545$8F102$B19649 +3 upDamage, then evasion up 1's code runs with the wrong byte ($8F): the stat code reads past its stat tableNo crash seenTry it
0xC9 201TM0197$2139$9103Acts as may poison, the effect of Smog and SludgeNo crash seenTry it
0xCA 202TM02177$3F15$C81318Acts as evasion down 2, an effect no real move hasNo crash seenTry it
0xCB 203TM0350$009$4F8336 +1 upDamage onlyNo crash seenTry it
0xCC 204TM0478$5521$15 Water4518 +3 upActs as Splash, the effect of SplashNo crash seenTry it
0xCD 205TM05119$37118$5112033Acts as evasion up 2, an effect no real move hasNo crash seenTry it
0xCE 206TM0639$9155$03 Poison17763 +1 upDamage, then Swift's code runs with the wrong byte ($91): that table entry is empty, so the game jumps to address $0000Crashes Its effect crashes the game for you and the foe, even with its name kept short.Try it
0xCF 207TM0715$CE131$08 Ghost500 never pickableDamage, then unused effect $4E's code runs with the wrong byte ($CE): that table entry is empty, so the game jumps to address $0000Crashes Its effect crashes the game when a foe uses it, even with its name kept short.0 PP
0xD0 208TM0810$2D30$234520Acts as Jump Kick, the effect of Jump Kick and Hi Jump KickNo crash seenTry it
0xD1 209TM097$07255$35859 +1 upActs as explode, the effect of Selfdestruct and ExplosionNo crash seenTry it
0xD2 210TM1074$E174$21810 never pickableDamage, then a jump past the effect table into other codeNo crash seen0 PP
0xD3 211TM110$000$00 Normal00 never pickableDoes nothingNo crash seen0 PP
0xD4 212TM120$000$00 Normal1150Does nothingNo crash seenTry it
0xD5 213TM1320$3730$19 Ice77Acts as evasion up 2, an effect no real move hasNo crash seenTry it
0xD6 214TM14120$4885$3A758 +3 upActs as unused effect $48, an effect no real move hasNo crash seenTry it
0xD7 215TM1575$6A0$00 Normal00 never pickableDamage, then a jump past the effect table to $A778, inside cartridge RAM (the save data), and runs it as codeCrashes Its effect crashes the game when a foe uses it, even with its name kept short.0 PP
0xD8 216TM160$000$00 Normal00 never pickableDoes nothingNo crash seen0 PP
0xD9 217TM170$0012$3C4550Damage onlyNo crash seenTry it
0xDA 218TM1870$507$02 Flying4532 +2 upActs as Hyper Beam's recharge, the effect of Hyper BeamNo crash seenTry it
0xDB 219TM19119$3776$0E7829 +1 upActs as evasion up 2, an effect no real move hasNo crash seennot in the battler
0xDC 220TM200$000$00 Normal423 +1 upDoes nothingNo crash seenTry it
0xDD 221TM2156$F067$2820 never pickableDamage, then a jump past the effect table into other codeNo crash seen0 PP
0xDE 222TM2213$2835$1E5020Acts as Super Fang, the effect of Super FangNo crash seennot in the battler
0xDF 223TM237$03255$348561 +1 upActs as drain HP, the effect of Absorb, Mega Drain and Leech LifeNo crash seenTry it
0xE0 224TM24117$24118$28810 never pickableActs as may paralyze, the effect of Body Slam and LickNo crash seen0 PP
0xE1 225TM250$000$00 Normal00 never pickableDoes nothingNo crash seen0 PP
0xE2 226TM260$000$00 Normal1445Does nothingNo crash seenTry it
0xE3 227TM2725$3235$19 Ice73Acts as Attack up 2, the effect of Swords DanceNo crash seenTry it
0xE4 228TM28120$4785$7711854Acts as may lower Special, the effect of PsychicNo crash seenTry it
0xE5 229TM29119$6A0$00 Normal00 never pickableDamage, then a jump past the effect table to $A778, inside cartridge RAM (the save data), and runs it as codeCrashes Its effect crashes the game when a foe uses it, even with its name kept short.0 PP
0xE6 230TM300$000$00 Normal00 never pickableDoes nothingNo crash seen0 PP
0xE7 231TM310$0015$418040Damage onlyNo crash seenTry it
0xE8 232TM3275$2D7$03 Poison4531 +2 upActs as Jump Kick, the effect of Jump Kick and Hi Jump KickNo crash seenTry it
0xE9 233TM33119$88119$8012131Damage, then Dream Eater's code runs with the wrong byte ($88)No crash seenTry it
0xEA 234TM340$000$00 Normal363 +1 upDoes nothingNo crash seenTry it
0xEB 235TM3524$C0195$08 Ghost60 never pickableDamage, then Light Screen's code runs with the wrong byte ($C0)No crash seen0 PP
0xEC 236TM3616$2845$285635Acts as Super Fang, the effect of Super FangNo crash seenTry it
0xED 237TM370$02255$378539 +2 upActs as may poison, the effect of Poison StingNo crash seennot in the battler
0xEE 238TM3869$5B70$1000 never pickableDamage, then a jump past the effect table into other codeNo crash seen0 PP
0xEF 239TM390$0342$03 Poison80 +3 up never pickableActs as drain HP, the effect of Absorb, Mega Drain and Leech LifeNo crash seen0 PP
0xF0 240TM4067$0C10$00 Normal1763Acts as Speed up 1, an effect no real move hasNo crash seenTry it
0xF1 241TM4160$3771$3202Acts as evasion up 2, an effect no real move hasNo crash seenTry it
0xF2 242TM42120$71102$0A12027 +1 upDamage, then a jump past the effect table into other codeRed: Locks up Blue: No crash seen Red: Its effect locks up the CPU when you use it, even with its name kept short. Blue: no crash seen.Try it
0xF3 243TM43121$1028$00 Normal03Acts as Pay Day, the effect of Pay DayNo crash seenTry it
0xF4 244TM4442$038$C06712Acts as drain HP, the effect of Absorb, Mega Drain and Leech LifeNo crash seenTry it
0xF5 245TM4510$0018$538011 +1 upDamage onlyNo crash seenTry it
0xF6 246TM4691$460$02 Flying4544 +2 upActs as may lower Speed, the effect of Bubblebeam, Constrict and BubbleNo crash seenTry it
0xF7 247TM47119$C2121$7912316Damage, then poison's code runs with the wrong byte ($C2)No crash seenTry it
0xF8 248TM4828$620$03 Poison423 +1 upDamage, then a jump past the effect table into other code (read from the ROM at its address: no run of it came back, so the game was never seen loading it)Locks up Every run stopped PyBoy (a CPU lock-up) before its record came back, so that is all I know of it.Try it
0xF9 249TM498$C067$0C100 never pickableDamage, then Light Screen's code runs with the wrong byte ($C0)No crash seen0 PP
0xFA 250TM5019$1E56$237225Acts as unused effect $1E, an effect no real move hasNo crash seenTry it
0xFB 251TM510$00255$398542 +1 upDamage onlyNo crash seennot in the battler
0xFC 252TM5279$4180$21390 never pickableActs as Reflect, the effect of ReflectNo crash seen0 PP
0xFD 253TM530$00160$2F1369 +3 upDamage onlyNo crash seenTry it
0xFE 254TM54194$082$00 Normal2055Acts as Dream Eater, the effect of Dream EaterNo crash seenTry it
0xFF 255TM5581$3C97$3200 never pickableNever runs: the game reads move $FF as "cannot move" and skips the turnNo crash seen0 PP
Pokemon Yellow: every glitch move, 0x00 and 0xA6 to 0xFF. Yellow's bytes differ from Red and Blue's on 33 moves, marked ≠.
MoveNameAnimEffectPowerTypeAcc.PPWhat it doesIn my tests
0x00 0 ≠none (dashes)90$74102$318110The empty move: with it first, FIGHT shows only dashes, yet A picks it. Then: damage, then a jump past the effect table into echo RAMFreezes A foe whose only move is 0x00 freezes the game choosing a move.
0xA6 16620 zero bytes1$2D49$31451 +1 upActs as Jump Kick, the effect of Jump Kick and Hi Jump KickCrashes Opening FIGHT crashes the game (its name). The foe using it softlocks the game (its name).
0xA7 167blank (from ROM)22$0345$40850 never pickableActs as drain HP, the effect of Absorb, Mega Drain and Leech LifeNo crash seen
0xA8 168 ≠from ROM, runs on64$E464$21450 never pickableDamage, then a jump past the effect table into other codeCrashes Opening FIGHT crashes the game (its name). The foe using it softlocks the game (its name).
0xA9 169from memory0$03164$03 Poison560 +3 up never pickableActs as drain HP, the effect of Absorb, Mega Drain and Leech LifeNo crash seen
0xAA 170from memory3$086$00 Normal260Acts as Dream Eater, the effect of Dream EaterCrashes Opening FIGHT crashes the game (its name). The foe using it softlocks the game (its name).
0xAB 171from memory62$3F60$50223Acts as evasion down 2, an effect no real move hasCrashes Opening FIGHT crashes the game (its name). The foe using it softlocks the game (its name).
0xAC 172 ≠from memory45$8D102$E97951 +1 upDamage, then Special up 1's code runs with the wrong byte ($8D): the stat code reads past its stat tableFreezes Opening FIGHT freezes the game (its name). The foe using it softlocks the game (its name).
0xAD 173from memory81$2145$4903Acts as may poison, the effect of Smog and SludgeNo crash seen
0xAE 174from memory164$0356$C038Acts as drain HP, the effect of Absorb, Mega Drain and Leech LifeCrashes Opening FIGHT crashes the game (its name). The foe using it softlocks the game (its name).
0xAF 175from memory6$003$508219 +1 upDamage onlyNo crash seen
0xB0 176from memory80$6422$03 Poison4516 +3 upDamage, then a jump past the effect table into other codeNo crash seen
0xB1 177 ≠from memory119$6165$816733Damage, then a jump past the effect table into other codeCrashes Its effect crashes the game when the foe uses it, even with its name kept short.
0xB2 178from memory45$4922$03 Poison1643 +1 upActs as unused effect $49, an effect no real move hasCrashes Opening FIGHT crashes the game (its name). The foe using it softlocks the game (its name).
0xB3 179from memory56$C03$08 Ghost60 never pickableDamage, then Light Screen's code runs with the wrong byte ($C0)Freezes Opening FIGHT freezes the game (its name). The foe using it softlocks the game (its name).
0xB4 180from memory4$2752$2B6550Acts as charge, then attack, the effect of Razor Wind, Solarbeam and othersCrashes Opening FIGHT crashes the game (its name). The foe using it softlocks the game (its name). Its status screen (page 2) softlocks the game.
0xB5 181 ≠from memory20$1445$418548 +3 upActs as Speed down 1, the effect of String ShotCrashes Opening FIGHT crashes the game (its name). The foe using it softlocks the game (its name).
0xB6 182 ≠from memory93$FC94$0A450 never pickableDamage, then a jump past the effect table into other codeSoftlocks The foe using it softlocks the game (its name).
0xB7 183from memory0$03181$03 Poison798 +3 upActs as drain HP, the effect of Absorb, Mega Drain and Leech LifeCrashes Opening FIGHT crashes the game (its name).
0xB8 184from memory227$0838$00 Normal558Acts as Dream Eater, the effect of Dream EaterCrashes Opening FIGHT crashes the game (its name). The foe using it softlocks the game (its name).
0xB9 185from memory64$3A80$412020Acts as Attack down 2, an effect no real move hasCrashes Opening FIGHT crashes the game (its name).
0xBA 186 ≠from memory45$8E102$C89637Damage, then accuracy up 1's code runs with the wrong byte ($8E): the stat code reads past its stat tableCrashes Opening FIGHT crashes the game (its name). The foe using it softlocks the game (its name).
0xBB 187 ≠from memory98$0A45$3403Acts as Attack up 1, the effect of Meditate and SharpenCrashes Opening FIGHT crashes the game (its name). The foe using it softlocks the game (its name).
0xBC 188from memory181$0379$C82278Acts as drain HP, the effect of Absorb, Mega Drain and Leech LifeNo crash seen
0xBD 189from memory38$006$4E8414 +1 upDamage onlyCrashes Using it crashes the game (its name). The foe using it softlocks the game (its name).
0xBE 190from memory100$5520$02 Flying4517 +3 upActs as Splash, the effect of SplashSoftlocks The foe using it softlocks the game (its name).
0xBF 191 ≠from memory119$A9100$00 Normal10310Damage, then fixed damage's code runs with the wrong byte ($A9): that table entry is empty, so the game jumps to address $0000Crashes Opening FIGHT crashes the game (its name). Its effect crashes the game for you and the foe, even with its name kept short.
0xC0 192from memory45$3443$03 Poison1813 +1 upActs as Speed up 2, the effect of AgilityNo crash seen
0xC1 193 ≠from memory79$CE227$08 Ghost460 never pickableDamage, then unused effect $4E's code runs with the wrong byte ($CE): that table entry is empty, so the game jumps to address $0000No crash seen
0xC2 194from memory7$2C48$414350Acts as hit twice, the effect of Double Kick and BonemerangNo crash seen
0xC3 195 ≠from memory21$1545$428524 +1 upActs as Special down 1, an effect no real move hasSoftlocks The foe using it softlocks the game (its name).
0xC4 196 ≠HM0195$4B96$21390 never pickableActs as unused effect $4B, an effect no real move hasNo crash seen
0xC5 197HM020$03177$3F158 +3 upActs as drain HP, the effect of Absorb, Mega Drain and Leech LifeNo crash seen
0xC6 198HM03131$0850$00 Normal859Acts as Dream Eater, the effect of Dream EaterNo crash seen
0xC7 199HM0463$5058$412121Acts as Hyper Beam's recharge, the effect of Hyper BeamNo crash seen
0xC8 200 ≠HM0545$8F102$8E9820Damage, then evasion up 1's code runs with the wrong byte ($8F): the stat code reads past its stat tableNo crash seen
0xC9 201 ≠TM01100$2139$9103Acts as may poison, the effect of Smog and SludgeNo crash seen
0xCA 202TM02177$3F15$C81318Acts as evasion down 2, an effect no real move hasNo crash seen
0xCB 203TM0350$009$4F8336 +1 upDamage onlyNo crash seen
0xCC 204TM0478$5521$15 Water4518 +3 upActs as Splash, the effect of SplashNo crash seen
0xCD 205 ≠TM05119$FA117$0B12033Damage, then a jump past the effect table into echo RAMCrashes Its effect crashes the game for you and the foe, even with its name kept short.
0xCE 206TM0639$9155$03 Poison17763 +1 upDamage, then Swift's code runs with the wrong byte ($91): that table entry is empty, so the game jumps to address $0000Crashes Its effect crashes the game for you and the foe, even with its name kept short.
0xCF 207TM0715$CE131$08 Ghost500 never pickableDamage, then unused effect $4E's code runs with the wrong byte ($CE): that table entry is empty, so the game jumps to address $0000No crash seen
0xD0 208TM0810$2D30$234520Acts as Jump Kick, the effect of Jump Kick and Hi Jump KickNo crash seen
0xD1 209 ≠TM097$07255$35855Acts as explode, the effect of Selfdestruct and ExplosionNo crash seen
0xD2 210 ≠TM1075$E875$21810 never pickableDamage, then a jump past the effect table into other codeCrashes
0xD3 211TM110$000$00 Normal00 never pickableDoes nothingNo crash seen
0xD4 212TM120$000$00 Normal1150Does nothingNo crash seen
0xD5 213TM1320$3730$19 Ice77Acts as evasion up 2, an effect no real move hasNo crash seen
0xD6 214 ≠TM14120$4885$417646 +3 upActs as unused effect $48, an effect no real move hasNo crash seen
0xD7 215 ≠TM1576$6A0$00 Normal00 never pickableDamage, then a jump past the effect table to $A778, inside cartridge RAM (the save data), and runs it as codeCrashes Its effect crashes the game when a foe uses it, even with its name kept short.
0xD8 216TM160$000$00 Normal00 never pickableDoes nothingNo crash seen
0xD9 217TM170$0012$3C4550Damage onlyNo crash seen
0xDA 218TM1870$507$02 Flying4532 +2 upActs as Hyper Beam's recharge, the effect of Hyper BeamNo crash seen
0xDB 219 ≠TM19119$5D77$347929 +1 upDamage, then a jump past the effect table into other codeNo crash seen
0xDC 220TM200$000$00 Normal423 +1 upDoes nothingNo crash seen
0xDD 221 ≠TM2156$F067$28660 never pickableDamage, then a jump past the effect table into the link cable routine, which waits for a link partner foreverNo crash seen
0xDE 222TM2213$2835$1E5020Acts as Super Fang, the effect of Super FangNo crash seen
0xDF 223 ≠TM237$03255$34852Acts as drain HP, the effect of Absorb, Mega Drain and Leech LifeNo crash seen
0xE0 224 ≠TM24119$B4119$28810 never pickableDamage, then Speed up 2's code runs with the wrong byte ($B4): the stat code reads past its stat tableNo crash seen
0xE1 225TM250$000$00 Normal00 never pickableDoes nothingNo crash seen
0xE2 226TM260$000$00 Normal1445Does nothingNo crash seen
0xE3 227TM2725$3235$19 Ice73Acts as Attack up 2, the effect of Swords DanceNo crash seen
0xE4 228 ≠TM28120$4785$07 Bug1209 +3 upActs as may lower Special, the effect of PsychicNo crash seen
0xE5 229 ≠TM29120$6A0$00 Normal00 never pickableDamage, then a jump past the effect table to $A778, inside cartridge RAM (the save data), and runs it as codeCrashes Its effect crashes the game when a foe uses it, even with its name kept short.
0xE6 230TM300$000$00 Normal00 never pickableDoes nothingNo crash seen
0xE7 231TM310$0015$418040Damage onlyNo crash seen
0xE8 232TM3275$2D7$03 Poison4531 +2 upActs as Jump Kick, the effect of Jump Kick and Hi Jump KickNo crash seen
0xE9 233 ≠TM33119$1B121$2A12331Acts as Thrash, the effect of Thrash and Petal DanceNo crash seen
0xEA 234TM340$000$00 Normal363 +1 upDoes nothingNo crash seen
0xEB 235TM3524$C0195$08 Ghost60 never pickableDamage, then Light Screen's code runs with the wrong byte ($C0)No crash seen
0xEC 236TM3616$2845$285635Acts as Super Fang, the effect of Super FangNo crash seen
0xED 237 ≠TM370$02255$378553 +3 upActs as may poison, the effect of Poison StingNo crash seen
0xEE 238 ≠TM3869$E670$1000 never pickableDamage, then a jump past the effect table into other codeNo crash seen
0xEF 239TM390$0342$03 Poison80 +3 up never pickableActs as drain HP, the effect of Absorb, Mega Drain and Leech LifeNo crash seen
0xF0 240TM4067$0C10$00 Normal1763Acts as Speed up 1, an effect no real move hasNo crash seen
0xF1 241TM4160$3771$3202Acts as evasion up 2, an effect no real move hasNo crash seen
0xF2 242 ≠TM42120$71102$C611843Damage, then a jump past the effect table into other codeCrashes Its effect crashes the game when you use it, even with its name kept short. Its effect locks up the CPU when the foe uses it, even with its name kept short.
0xF3 243 ≠TM43120$1028$00 Normal03Acts as Pay Day, the effect of Pay DayNo crash seen
0xF4 244TM4442$038$C06712Acts as drain HP, the effect of Absorb, Mega Drain and Leech LifeNo crash seen
0xF5 245TM4510$0018$538011 +1 upDamage onlyNo crash seen
0xF6 246TM4691$460$02 Flying4544 +2 upActs as may lower Speed, the effect of Bubblebeam, Constrict and BubbleNo crash seen
0xF7 247 ≠TM47119$92120$D112216Damage, then Attack down 1's code runs with the wrong byte ($92): the stat code reads past its stat tableNo crash seen
0xF8 248TM4828$620$03 Poison423 +1 upDamage, then a jump past the effect table into other codeNo crash seen
0xF9 249TM498$C067$0C100 never pickableDamage, then Light Screen's code runs with the wrong byte ($C0)No crash seen
0xFA 250TM5019$1E56$237225Acts as unused effect $1E, an effect no real move hasNo crash seen
0xFB 251 ≠TM510$00255$39853Damage onlyNo crash seen
0xFC 252 ≠TM5280$F880$21390 never pickableDamage, then a jump past the effect table into other codeNo crash seen
0xFD 253TM530$00160$2F1369 +3 upDamage onlyNo crash seen
0xFE 254TM54194$082$00 Normal2055Acts as Dream Eater, the effect of Dream EaterNo crash seen
0xFF 255TM5581$3C97$3200 never pickableNever runs: the game reads move $FF as "cannot move" and skips the turnNo crash seen

The same rows as JSON and CSV, with every column explained, are on the Gen 1 glitch data page.

Why the numbers are what they are

When a move is used, the game copies six bytes for it out of its move table: the animation, the effect, the power, the type, the accuracy and the PP. It finds them by multiplying: move number minus one, times six, from the start of the table. The table holds exactly 165 moves and ends at Struggle. In all three games the very next thing in the cartridge is the base stats table, the 28 bytes the game keeps for each Pokemon, in Pokedex order. So the glitch moves are not reading noise. They are reading Bulbasaur, Ivysaur, Venusaur and the rest, six bytes at a time.

That is why 0xA6 is the most famous one. Its six bytes are Bulbasaur's Pokedex number and base stats: 1, 45, 49, 49, 45, 65. Read as a move, that is animation 1 (Pound's), effect 45 ($2D, the effect of Jump Kick), power 49, type 49 ($31, not a real type, so neutral to everything and a Special attack), accuracy 45 out of 256, and PP byte 65, which is 1 PP with 1 PP Up. With its name kept short, 0xA6 behaves as a Jump Kick of power 49 that misses 211 times in 256, and then the user "kept going and crashed!".

The glitch moves walk through the first 20 Pokemon, Bulbasaur to Raticate. Move 0x00 is no exception: the game subtracts one in a single byte, so 0 becomes 255 and reads the slot after 0xFF, a little further into Raticate. Pick a move and see which bytes it borrows.

Pick a move to see the six bytes it reads.

The 20 rows are the base data of Pokedex No. 1 to 20, 28 bytes each; the red cells are the six this move reads. Only those six bytes are shown. Where a byte has no meaning as a move (a picture pointer used as a type, say), the move just takes the number.
Three examples, Red and Blue
MoveBytesWhere they come from
0xA61 $2D 49 $31 45 65Bulbasaur: Pokedex No. 1, base HP 45, Attack 49, Defense 49, Speed 45, Special 65
0xFF TM5581 $3C 97 $32 0 0Raticate: base Attack 81, Defense 60, Speed 97, Special 50, and its two types, Normal and Normal (0)
0x0090 $74 102 $7A 80 13Raticate: catch rate 90, base experience 116, picture size, front picture pointer and the low byte of the back picture pointer
Where all 91 come from (Red and Blue, with Yellow's bytes where they differ)
  • 0x00 Raticate (No. 20): catch rate, base experience, picture size, front picture pointer (low byte), front picture pointer (high byte), back picture pointer (low byte): 90 116 102 122 80 13 (Yellow: 90 116 102 49 81 10)
  • 0xA6 Bulbasaur (No. 1): Pokedex No., base HP, base Attack, base Defense, base Speed, base Special: 1 45 49 49 45 65 (Yellow: the same bytes)
  • 0xA7 Bulbasaur (No. 1): type 1, type 2, catch rate, base experience, picture size, front picture pointer (low byte): 22 3 45 64 85 0 (Yellow: the same bytes)
  • 0xA8 Bulbasaur (No. 1): front picture pointer (high byte), back picture pointer (low byte), back picture pointer (high byte), level 1 move 1, level 1 move 2, level 1 move 3: 64 229 64 33 45 0 (Yellow: 64 228 64 33 45 0)
  • 0xA9 Bulbasaur (No. 1): level 1 move 4, growth rate, TM and HM bits (byte 1), TM and HM bits (byte 2), TM and HM bits (byte 3), TM and HM bits (byte 4): 0 3 164 3 56 192 (Yellow: the same bytes)
  • 0xAA Bulbasaur (No. 1): TM and HM bits (byte 5), TM and HM bits (byte 6), TM and HM bits (byte 7), padding; Ivysaur (No. 2): Pokedex No., base HP: 3 8 6 0 2 60 (Yellow: the same bytes)
  • 0xAB Ivysaur (No. 2): base Attack, base Defense, base Speed, base Special, type 1, type 2: 62 63 60 80 22 3 (Yellow: the same bytes)
  • 0xAC Ivysaur (No. 2): catch rate, base experience, picture size, front picture pointer (low byte), front picture pointer (high byte), back picture pointer (low byte): 45 141 102 43 80 87 (Yellow: 45 141 102 233 79 115)
  • 0xAD Ivysaur (No. 2): back picture pointer (high byte), level 1 move 1, level 1 move 2, level 1 move 3, level 1 move 4, growth rate: 81 33 45 73 0 3 (Yellow: the same bytes)
  • 0xAE Ivysaur (No. 2): TM and HM bits (byte 1), TM and HM bits (byte 2), TM and HM bits (byte 3), TM and HM bits (byte 4), TM and HM bits (byte 5), TM and HM bits (byte 6): 164 3 56 192 3 8 (Yellow: the same bytes)
  • 0xAF Ivysaur (No. 2): TM and HM bits (byte 7), padding; Venusaur (No. 3): Pokedex No., base HP, base Attack, base Defense: 6 0 3 80 82 83 (Yellow: the same bytes)
  • 0xB0 Venusaur (No. 3): base Speed, base Special, type 1, type 2, catch rate, base experience: 80 100 22 3 45 208 (Yellow: the same bytes)
  • 0xB1 Venusaur (No. 3): picture size, front picture pointer (low byte), front picture pointer (high byte), back picture pointer (low byte), back picture pointer (high byte), level 1 move 1: 119 98 65 151 67 33 (Yellow: 119 97 65 129 67 33)
  • 0xB2 Venusaur (No. 3): level 1 move 2, level 1 move 3, level 1 move 4, growth rate, TM and HM bits (byte 1), TM and HM bits (byte 2): 45 73 22 3 164 67 (Yellow: the same bytes)
  • 0xB3 Venusaur (No. 3): TM and HM bits (byte 3), TM and HM bits (byte 4), TM and HM bits (byte 5), TM and HM bits (byte 6), TM and HM bits (byte 7), padding: 56 192 3 8 6 0 (Yellow: the same bytes)
  • 0xB4 Charmander (No. 4): Pokedex No., base HP, base Attack, base Defense, base Speed, base Special: 4 39 52 43 65 50 (Yellow: the same bytes)
  • 0xB5 Charmander (No. 4): type 1, type 2, catch rate, base experience, picture size, front picture pointer (low byte): 20 20 45 65 85 92 (Yellow: 20 20 45 65 85 240)
  • 0xB6 Charmander (No. 4): front picture pointer (high byte), back picture pointer (low byte), back picture pointer (high byte), level 1 move 1, level 1 move 2, level 1 move 3: 92 92 93 10 45 0 (Yellow: 93 252 94 10 45 0)
  • 0xB7 Charmander (No. 4): level 1 move 4, growth rate, TM and HM bits (byte 1), TM and HM bits (byte 2), TM and HM bits (byte 3), TM and HM bits (byte 4): 0 3 181 3 79 200 (Yellow: the same bytes)
  • 0xB8 Charmander (No. 4): TM and HM bits (byte 5), TM and HM bits (byte 6), TM and HM bits (byte 7), padding; Charmeleon (No. 5): Pokedex No., base HP: 227 8 38 0 5 58 (Yellow: the same bytes)
  • 0xB9 Charmeleon (No. 5): base Attack, base Defense, base Speed, base Special, type 1, type 2: 64 58 80 65 20 20 (Yellow: the same bytes)
  • 0xBA Charmeleon (No. 5): catch rate, base experience, picture size, front picture pointer (low byte), front picture pointer (high byte), back picture pointer (low byte): 45 142 102 12 95 72 (Yellow: 45 142 102 200 96 37)
  • 0xBB Charmeleon (No. 5): back picture pointer (high byte), level 1 move 1, level 1 move 2, level 1 move 3, level 1 move 4, growth rate: 96 10 45 52 0 3 (Yellow: 98 10 45 52 0 3)
  • 0xBC Charmeleon (No. 5): TM and HM bits (byte 1), TM and HM bits (byte 2), TM and HM bits (byte 3), TM and HM bits (byte 4), TM and HM bits (byte 5), TM and HM bits (byte 6): 181 3 79 200 227 8 (Yellow: the same bytes)
  • 0xBD Charmeleon (No. 5): TM and HM bits (byte 7), padding; Charizard (No. 6): Pokedex No., base HP, base Attack, base Defense: 38 0 6 78 84 78 (Yellow: the same bytes)
  • 0xBE Charizard (No. 6): base Speed, base Special, type 1, type 2, catch rate, base experience: 100 85 20 2 45 209 (Yellow: the same bytes)
  • 0xBF Charizard (No. 6): picture size, front picture pointer (low byte), front picture pointer (high byte), back picture pointer (low byte), back picture pointer (high byte), level 1 move 1: 119 134 98 149 100 10 (Yellow: 119 169 100 0 103 10)
  • 0xC0 Charizard (No. 6): level 1 move 2, level 1 move 3, level 1 move 4, growth rate, TM and HM bits (byte 1), TM and HM bits (byte 2): 45 52 43 3 181 67 (Yellow: the same bytes)
  • 0xC1 Charizard (No. 6): TM and HM bits (byte 3), TM and HM bits (byte 4), TM and HM bits (byte 5), TM and HM bits (byte 6), TM and HM bits (byte 7), padding: 79 206 227 8 38 0 (Yellow: 79 206 227 8 46 0)
  • 0xC2 Squirtle (No. 7): Pokedex No., base HP, base Attack, base Defense, base Speed, base Special: 7 44 48 65 43 50 (Yellow: the same bytes)
  • 0xC3 Squirtle (No. 7): type 1, type 2, catch rate, base experience, picture size, front picture pointer (low byte): 21 21 45 66 85 184 (Yellow: 21 21 45 66 85 88)
  • 0xC4 Squirtle (No. 7): front picture pointer (high byte), back picture pointer (low byte), back picture pointer (high byte), level 1 move 1, level 1 move 2, level 1 move 3: 93 143 94 33 39 0 (Yellow: 95 75 96 33 39 0)
  • 0xC5 Squirtle (No. 7): level 1 move 4, growth rate, TM and HM bits (byte 1), TM and HM bits (byte 2), TM and HM bits (byte 3), TM and HM bits (byte 4): 0 3 177 63 15 200 (Yellow: the same bytes)
  • 0xC6 Squirtle (No. 7): TM and HM bits (byte 5), TM and HM bits (byte 6), TM and HM bits (byte 7), padding; Wartortle (No. 8): Pokedex No., base HP: 131 8 50 0 8 59 (Yellow: the same bytes)
  • 0xC7 Wartortle (No. 8): base Attack, base Defense, base Speed, base Special, type 1, type 2: 63 80 58 65 21 21 (Yellow: the same bytes)
  • 0xC8 Wartortle (No. 8): catch rate, base experience, picture size, front picture pointer (low byte), front picture pointer (high byte), back picture pointer (low byte): 45 143 102 177 96 241 (Yellow: 45 143 102 142 98 20)
  • 0xC9 Wartortle (No. 8): back picture pointer (high byte), level 1 move 1, level 1 move 2, level 1 move 3, level 1 move 4, growth rate: 97 33 39 145 0 3 (Yellow: 100 33 39 145 0 3)
  • 0xCA Wartortle (No. 8): TM and HM bits (byte 1), TM and HM bits (byte 2), TM and HM bits (byte 3), TM and HM bits (byte 4), TM and HM bits (byte 5), TM and HM bits (byte 6): 177 63 15 200 131 8 (Yellow: the same bytes)
  • 0xCB Wartortle (No. 8): TM and HM bits (byte 7), padding; Blastoise (No. 9): Pokedex No., base HP, base Attack, base Defense: 50 0 9 79 83 100 (Yellow: the same bytes)
  • 0xCC Blastoise (No. 9): base Speed, base Special, type 1, type 2, catch rate, base experience: 78 85 21 21 45 210 (Yellow: the same bytes)
  • 0xCD Blastoise (No. 9): picture size, front picture pointer (low byte), front picture pointer (high byte), back picture pointer (low byte), back picture pointer (high byte), level 1 move 1: 119 55 118 81 120 33 (Yellow: 119 250 117 11 120 33)
  • 0xCE Blastoise (No. 9): level 1 move 2, level 1 move 3, level 1 move 4, growth rate, TM and HM bits (byte 1), TM and HM bits (byte 2): 39 145 55 3 177 127 (Yellow: the same bytes)
  • 0xCF Blastoise (No. 9): TM and HM bits (byte 3), TM and HM bits (byte 4), TM and HM bits (byte 5), TM and HM bits (byte 6), TM and HM bits (byte 7), padding: 15 206 131 8 50 0 (Yellow: the same bytes)
  • 0xD0 Caterpie (No. 10): Pokedex No., base HP, base Attack, base Defense, base Speed, base Special: 10 45 30 35 45 20 (Yellow: the same bytes)
  • 0xD1 Caterpie (No. 10): type 1, type 2, catch rate, base experience, picture size, front picture pointer (low byte): 7 7 255 53 85 73 (Yellow: 7 7 255 53 85 5)
  • 0xD2 Caterpie (No. 10): front picture pointer (high byte), back picture pointer (low byte), back picture pointer (high byte), level 1 move 1, level 1 move 2, level 1 move 3: 74 225 74 33 81 0 (Yellow: 75 232 75 33 81 0)
  • 0xD3 Caterpie (No. 10): level 1 move 4, growth rate, TM and HM bits (byte 1), TM and HM bits (byte 2), TM and HM bits (byte 3), TM and HM bits (byte 4): 0 0 0 0 0 0 (Yellow: the same bytes)
  • 0xD4 Caterpie (No. 10): TM and HM bits (byte 5), TM and HM bits (byte 6), TM and HM bits (byte 7), padding; Metapod (No. 11): Pokedex No., base HP: 0 0 0 0 11 50 (Yellow: the same bytes)
  • 0xD5 Metapod (No. 11): base Attack, base Defense, base Speed, base Special, type 1, type 2: 20 55 30 25 7 7 (Yellow: the same bytes)
  • 0xD6 Metapod (No. 11): catch rate, base experience, picture size, front picture pointer (low byte), front picture pointer (high byte), back picture pointer (low byte): 120 72 85 58 75 200 (Yellow: 120 72 85 65 76 238)
  • 0xD7 Metapod (No. 11): back picture pointer (high byte), level 1 move 1, level 1 move 2, level 1 move 3, level 1 move 4, growth rate: 75 106 0 0 0 0 (Yellow: 76 106 0 0 0 0)
  • 0xD8 Metapod (No. 11): TM and HM bits (byte 1), TM and HM bits (byte 2), TM and HM bits (byte 3), TM and HM bits (byte 4), TM and HM bits (byte 5), TM and HM bits (byte 6): 0 0 0 0 0 0 (Yellow: the same bytes)
  • 0xD9 Metapod (No. 11): TM and HM bits (byte 7), padding; Butterfree (No. 12): Pokedex No., base HP, base Attack, base Defense: 0 0 12 60 45 50 (Yellow: the same bytes)
  • 0xDA Butterfree (No. 12): base Speed, base Special, type 1, type 2, catch rate, base experience: 70 80 7 2 45 160 (Yellow: the same bytes)
  • 0xDB Butterfree (No. 12): picture size, front picture pointer (low byte), front picture pointer (high byte), back picture pointer (low byte), back picture pointer (high byte), level 1 move 1: 119 55 76 14 78 93 (Yellow: 119 93 77 52 79 93)
  • 0xDC Butterfree (No. 12): level 1 move 2, level 1 move 3, level 1 move 4, growth rate, TM and HM bits (byte 1), TM and HM bits (byte 2): 0 0 0 0 42 67 (Yellow: the same bytes)
  • 0xDD Butterfree (No. 12): TM and HM bits (byte 3), TM and HM bits (byte 4), TM and HM bits (byte 5), TM and HM bits (byte 6), TM and HM bits (byte 7), padding: 56 240 67 40 2 0 (Yellow: 56 240 67 40 66 0)
  • 0xDE Weedle (No. 13): Pokedex No., base HP, base Attack, base Defense, base Speed, base Special: 13 40 35 30 50 20 (Yellow: the same bytes)
  • 0xDF Weedle (No. 13): type 1, type 2, catch rate, base experience, picture size, front picture pointer (low byte): 7 3 255 52 85 125 (Yellow: 7 3 255 52 85 2)
  • 0xE0 Weedle (No. 13): front picture pointer (high byte), back picture pointer (low byte), back picture pointer (high byte), level 1 move 1, level 1 move 2, level 1 move 3: 117 36 118 40 81 0 (Yellow: 119 180 119 40 81 0)
  • 0xE1 Weedle (No. 13): level 1 move 4, growth rate, TM and HM bits (byte 1), TM and HM bits (byte 2), TM and HM bits (byte 3), TM and HM bits (byte 4): 0 0 0 0 0 0 (Yellow: the same bytes)
  • 0xE2 Weedle (No. 13): TM and HM bits (byte 5), TM and HM bits (byte 6), TM and HM bits (byte 7), padding; Kakuna (No. 14): Pokedex No., base HP: 0 0 0 0 14 45 (Yellow: the same bytes)
  • 0xE3 Kakuna (No. 14): base Attack, base Defense, base Speed, base Special, type 1, type 2: 25 50 35 25 7 3 (Yellow: the same bytes)
  • 0xE4 Kakuna (No. 14): catch rate, base experience, picture size, front picture pointer (low byte), front picture pointer (high byte), back picture pointer (low byte): 120 71 85 119 118 54 (Yellow: 120 71 85 7 120 201)
  • 0xE5 Kakuna (No. 14): back picture pointer (high byte), level 1 move 1, level 1 move 2, level 1 move 3, level 1 move 4, growth rate: 119 106 0 0 0 0 (Yellow: 120 106 0 0 0 0)
  • 0xE6 Kakuna (No. 14): TM and HM bits (byte 1), TM and HM bits (byte 2), TM and HM bits (byte 3), TM and HM bits (byte 4), TM and HM bits (byte 5), TM and HM bits (byte 6): 0 0 0 0 0 0 (Yellow: the same bytes)
  • 0xE7 Kakuna (No. 14): TM and HM bits (byte 7), padding; Beedrill (No. 15): Pokedex No., base HP, base Attack, base Defense: 0 0 15 65 80 40 (Yellow: the same bytes)
  • 0xE8 Beedrill (No. 15): base Speed, base Special, type 1, type 2, catch rate, base experience: 75 45 7 3 45 159 (Yellow: the same bytes)
  • 0xE9 Beedrill (No. 15): picture size, front picture pointer (low byte), front picture pointer (high byte), back picture pointer (low byte), back picture pointer (high byte), level 1 move 1: 119 136 119 128 121 31 (Yellow: 119 27 121 42 123 31)
  • 0xEA Beedrill (No. 15): level 1 move 2, level 1 move 3, level 1 move 4, growth rate, TM and HM bits (byte 1), TM and HM bits (byte 2): 0 0 0 0 36 67 (Yellow: the same bytes)
  • 0xEB Beedrill (No. 15): TM and HM bits (byte 3), TM and HM bits (byte 4), TM and HM bits (byte 5), TM and HM bits (byte 6), TM and HM bits (byte 7), padding: 24 192 195 8 6 0 (Yellow: the same bytes)
  • 0xEC Pidgey (No. 16): Pokedex No., base HP, base Attack, base Defense, base Speed, base Special: 16 40 45 40 56 35 (Yellow: the same bytes)
  • 0xED Pidgey (No. 16): type 1, type 2, catch rate, base experience, picture size, front picture pointer (low byte): 0 2 255 55 85 167 (Yellow: 0 2 255 55 85 245)
  • 0xEE Pidgey (No. 16): front picture pointer (high byte), back picture pointer (low byte), back picture pointer (high byte), level 1 move 1, level 1 move 2, level 1 move 3: 69 91 70 16 0 0 (Yellow: 69 230 70 16 0 0)
  • 0xEF Pidgey (No. 16): level 1 move 4, growth rate, TM and HM bits (byte 1), TM and HM bits (byte 2), TM and HM bits (byte 3), TM and HM bits (byte 4): 0 3 42 3 8 192 (Yellow: the same bytes)
  • 0xF0 Pidgey (No. 16): TM and HM bits (byte 5), TM and HM bits (byte 6), TM and HM bits (byte 7), padding; Pidgeotto (No. 17): Pokedex No., base HP: 67 12 10 0 17 63 (Yellow: the same bytes)
  • 0xF1 Pidgeotto (No. 17): base Attack, base Defense, base Speed, base Special, type 1, type 2: 60 55 71 50 0 2 (Yellow: the same bytes)
  • 0xF2 Pidgeotto (No. 17): catch rate, base experience, picture size, front picture pointer (low byte), front picture pointer (high byte), back picture pointer (low byte): 120 113 102 10 120 91 (Yellow: 120 113 102 198 118 43)
  • 0xF3 Pidgeotto (No. 17): back picture pointer (high byte), level 1 move 1, level 1 move 2, level 1 move 3, level 1 move 4, growth rate: 121 16 28 0 0 3 (Yellow: 120 16 28 0 0 3)
  • 0xF4 Pidgeotto (No. 17): TM and HM bits (byte 1), TM and HM bits (byte 2), TM and HM bits (byte 3), TM and HM bits (byte 4), TM and HM bits (byte 5), TM and HM bits (byte 6): 42 3 8 192 67 12 (Yellow: the same bytes)
  • 0xF5 Pidgeotto (No. 17): TM and HM bits (byte 7), padding; Pidgeot (No. 18): Pokedex No., base HP, base Attack, base Defense: 10 0 18 83 80 75 (Yellow: the same bytes)
  • 0xF6 Pidgeot (No. 18): base Speed, base Special, type 1, type 2, catch rate, base experience: 91 70 0 2 45 172 (Yellow: the same bytes)
  • 0xF7 Pidgeot (No. 18): picture size, front picture pointer (low byte), front picture pointer (high byte), back picture pointer (low byte), back picture pointer (high byte), level 1 move 1: 119 194 121 121 123 16 (Yellow: 119 146 120 209 122 16)
  • 0xF8 Pidgeot (No. 18): level 1 move 2, level 1 move 3, level 1 move 4, growth rate, TM and HM bits (byte 1), TM and HM bits (byte 2): 28 98 0 3 42 67 (Yellow: the same bytes)
  • 0xF9 Pidgeot (No. 18): TM and HM bits (byte 3), TM and HM bits (byte 4), TM and HM bits (byte 5), TM and HM bits (byte 6), TM and HM bits (byte 7), padding: 8 192 67 12 10 0 (Yellow: the same bytes)
  • 0xFA Rattata (No. 19): Pokedex No., base HP, base Attack, base Defense, base Speed, base Special: 19 30 56 35 72 25 (Yellow: the same bytes)
  • 0xFB Rattata (No. 19): type 1, type 2, catch rate, base experience, picture size, front picture pointer (low byte): 0 0 255 57 85 106 (Yellow: 0 0 255 57 85 3)
  • 0xFC Rattata (No. 19): front picture pointer (high byte), back picture pointer (low byte), back picture pointer (high byte), level 1 move 1, level 1 move 2, level 1 move 3: 79 65 80 33 39 0 (Yellow: 80 248 80 33 39 0)
  • 0xFD Rattata (No. 19): level 1 move 4, growth rate, TM and HM bits (byte 1), TM and HM bits (byte 2), TM and HM bits (byte 3), TM and HM bits (byte 4): 0 0 160 47 136 201 (Yellow: the same bytes)
  • 0xFE Rattata (No. 19): TM and HM bits (byte 5), TM and HM bits (byte 6), TM and HM bits (byte 7), padding; Raticate (No. 20): Pokedex No., base HP: 194 8 2 0 20 55 (Yellow: the same bytes)
  • 0xFF Raticate (No. 20): base Attack, base Defense, base Speed, base Special, type 1, type 2: 81 60 97 50 0 0 (Yellow: the same bytes)

In Yellow the same table holds other picture pointers for these Pokemon, and two of their TM and HM bytes differ, which is why 33 of its glitch moves have other bytes. The layout is the same, so the same move reads the same Pokemon's fields.

Where the moves run out of names

The game keeps its move names in one long list, 165 of them, in order. Turn the dial and watch the list end: number 165 is Struggle, the last move with a name. 166 to 195 are the Super Glitch band. From 196 up something else happens, which the last widget in this section shows.

Move IDs 1 to 165 are real moves, read straight from the game's name list. 166 through 195, hex $A6 to $C3, are the Super Glitch band: valid move IDs with no name behind them. 196 to 255 are named as TMs and HMs, and 0 is the empty slot.

Why a move with no name corrupts

To print a move's name, the game does not jump straight to it. It starts at the top of the name list and walks forward, counting end markers, until it has counted one fewer than the move's number. The name starts right after that. For a real move that lands on a real name. For 166 the walk stops on Struggle's own end marker, and the name starts in the zeros after it. From 167 on, the walk runs off the end of the list and keeps counting end markers in whatever comes next. Pick a move and watch the search.

MOVE NAME LIST · 1 to 165
PAST THE LIST
end markers counted: 0target: 163
The search counts end markers, the "@" byte ($50), from the top of the list. In Red and Blue the cartridge holds only zeros after Struggle's name, so from 167 on the count leaves the cartridge and goes on through video memory and work memory: the sound engine's variables, the screen, the battle variables and the names of the Pokemon in battle. Whatever bytes follow the last marker it counts become the name.

Then the game copies 20 bytes from there into its name buffer, and copies them on, letter by letter, until it reaches an end marker. If those 20 bytes hold no end marker, the copy keeps reading what sits after the buffer in memory and keeps writing. That is the overflow, and the next section measures it.

The names it does give

So does a move with no name ever show a name? Yes, and it exposes a second bug. The routine that fetches a name first checks whether the number is high enough to be a TM or HM item, and that check runs for every list, moves included. So from 196 on the game hands out clean machine names. Slide across the range and watch a move go from having no name to being called a TM.

Move IDs 166 to 195 ($A6 to $C3) have no names. In Red and Blue the move-name bank is empty after Struggle, so 166 copies twenty zero bytes with no end marker, and from 167 on the name starts past the end of the bank, in whatever memory sits there at that moment. Yellow keeps other data after its names, and its 167 lands right on an end marker, so it prints as a blank name. Its 168 also starts in that data, and from 169 on Yellow's names come from memory too, two names later than Red's. But 196 and up cross the threshold the game reserves for TM and HM items, and the bug in GetName applies it to moves too, so $C4 to $C8 print as HM01 to HM05 and $C9 to $FF print as TM01 to TM55. Checked in home/names2.asm and in every FIGHT menu run.

How far a Super Glitch name runs

Here is how many bytes each Super Glitch's name copy wrote in my test battle's FIGHT menu, with the move first in the list. The four names in that menu share a 56-byte space; the dashed line marks it. A red bar ran past it.

Red (Blue gave the same lengths), standard battle, PyBoy:

  1. 0xA6628 bytes, 584 past the list
  2. 0xA72 bytes
  3. 0xA8628 bytes, 584 past the list
  4. 0xA9628 bytes, 584 past the list
  5. 0xAA628 bytes, 584 past the list
  6. 0xAB0 bytes (a blank name)
  7. 0xAC628 bytes, 584 past the list
  8. 0xAD0 bytes (a blank name)
  9. 0xAE6 bytes
  10. 0xAF0 bytes (a blank name)
  11. 0xB0628 bytes, 584 past the list
  12. 0xB1628 bytes, 584 past the list
  13. 0xB2628 bytes, 584 past the list
  14. 0xB3628 bytes, 584 past the list
  15. 0xB42 bytes
  16. 0xB5628 bytes, 584 past the list
  17. 0xB6628 bytes, 584 past the list
  18. 0xB7628 bytes, 584 past the list
  19. 0xB80 bytes (a blank name)
  20. 0xB90 bytes (a blank name)
  21. 0xBA0 bytes (a blank name)
  22. 0xBB628 bytes, 584 past the list
  23. 0xBC0 bytes (a blank name)
  24. 0xBD0 bytes (a blank name)
  25. 0xBE0 bytes (a blank name)
  26. 0xBF628 bytes, 584 past the list
  27. 0xC00 bytes (a blank name)
  28. 0xC10 bytes (a blank name)
  29. 0xC20 bytes (a blank name)
  30. 0xC30 bytes (a blank name)

Yellow, standard battle, PyBoy:

  1. 0xA6627 bytes, 583 past the list
  2. 0xA70 bytes (a blank name)
  3. 0xA8627 bytes, 583 past the list
  4. 0xA92 bytes
  5. 0xAA627 bytes, 583 past the list
  6. 0xAB627 bytes, 583 past the list
  7. 0xAC627 bytes, 583 past the list
  8. 0xAD0 bytes (a blank name)
  9. 0xAE627 bytes, 583 past the list
  10. 0xAF0 bytes (a blank name)
  11. 0xB06 bytes
  12. 0xB10 bytes (a blank name)
  13. 0xB2627 bytes, 583 past the list
  14. 0xB3627 bytes, 583 past the list
  15. 0xB4627 bytes, 583 past the list
  16. 0xB5627 bytes, 583 past the list
  17. 0xB6627 bytes, 583 past the list
  18. 0xB72 bytes
  19. 0xB8627 bytes, 583 past the list
  20. 0xB9627 bytes, 583 past the list
  21. 0xBA627 bytes, 583 past the list
  22. 0xBB627 bytes, 583 past the list
  23. 0xBC0 bytes (a blank name)
  24. 0xBD0 bytes (a blank name)
  25. 0xBE0 bytes (a blank name)
  26. 0xBF627 bytes, 583 past the list
  27. 0xC00 bytes (a blank name)
  28. 0xC10 bytes (a blank name)
  29. 0xC20 bytes (a blank name)
  30. 0xC3627 bytes, 583 past the list

Treat every bar as one sample from one emulator. The name walk counts end markers in video memory, and the Game Boy's video chip refuses reads of video memory while it draws a line, which PyBoy does not model. When I ran the FIGHT menu step by step in PyBoy and in gambatte together, from the same save with the same button presses, only 6 of the 30 Super Glitch names in Red had the same 20 name bytes in both, 9 in Blue, and 7 of the 30 in Yellow. Even inside PyBoy, the same move's name came out different on the status screen and in a second battle with other Pokemon: only 2 of the 30 were the same in all three places in Red and Blue, 7 in Yellow. A Super Glitch's name, and how far it runs, depends on what is in memory and on where the video chip is when the walk passes. 0xA6 is the steady one: its 20 bytes are always zeros from the cartridge, which print as nothing, and it ran over memory and crashed in both emulators.

What a long name runs over is the part that matters. In Red and Blue, 0xA6's FIGHT menu list wrote 628 bytes, 584 past its 56, over the number of Pokemon in your party, the whole party with its trainer names and nicknames, the Pokedex owned and seen flags, the bag, the money, the rival's name, the options and the badges, all of it data the game saves. Yellow's ran one byte shorter.

What the other glitch move lists do not tell you

Running every move turned up five things I could not find on any glitch move list.

TM55, move 0xFF, never runs

The battle engine uses $FF in the "selected move" byte to mean that a Pokemon cannot move this turn, and checks for it before anything else. So when 0xFF is chosen, the turn is skipped without a word, for you or a foe. Its bytes, 81 $3C 97 $32 0 0, are only ever read for the TYPE/ box in the FIGHT menu. It also has 0 PP, so you could never pick it anyway.

Move 0x00 can be used

0x00 is the empty move slot, and in a move list it ends the list, so with 0x00 in the first slot the FIGHT menu shows only dashes. Yet A on the first row still picks it, and it runs with the bytes of entry 255 (in Red: power 102, accuracy 80, effect $74, which is past the effect table). A foe whose four moves are all 0x00 freezes the game: the routine that picks its move draws random slots forever, looking for one that is not 0.

The effect byte is checked twice, in two different ways

The battle engine's lists and checks compare a move's whole effect byte, and the real effects run from $01 to $56. The jump to the effect's own code drops the top bit. So a byte from $81 to $D6 is unknown to every list, takes the plain damage path, and then runs the code of effect byte minus $80, with the wrong byte still in place. In my Red test battle a foe's 0xEB (effect $C0) did 94 damage and then ran Light Screen's code, which checks for Light Screen, fails, and puts up Reflect instead: "gained armor!". 0xF7 (effect $C2) does its damage and then "was poisoned!". The stat codes (0xAC, 0xBA, 0xC4, 0xC8) get a stat number past their table and print "Nothing happened!" or nothing. Bytes $57 to $80 and $D7 to $FF read past the end of the 86-entry effect table and jump into whatever code follows it. Those stray jumps, and the table's empty entries, are where the crashes and lock-ups of the TM and HM named moves come from.

Try 0xF7 in the battler

Where the failing jumps land

0xCE and 0xCF (and Yellow's 0xBF and 0xC1) have effect bytes whose table entry is one of the table's empty entries, so using them jumps the game to address $0000 (in my Yellow battle 0xC1 happened to miss, so only 0xBF took the jump there). 0xD7 and 0xE5 (effect $6A) jump to $A778, inside cartridge RAM, where your save lives, and run it as code. Yellow's 0x00 and 0xCD point into echo RAM. Yellow's 0xDD lands in the link cable routine, which can wait on a link partner forever. The lock-ups (0xA8, 0xB1, 0xF2 and 0xF8) stopped the emulator before their records came back. Red and Blue have the same code where these jumps land, so they go to the same places; whether that code returns, crashes or locks up depends on the registers and memory at that moment, which is why 0xA8 and 0xF2 locked up in one game's test battle and not the other's. 0xF8 locked up every run in Red and Blue, so it has no completed record at all.

0xA6 crashes FIGHT, but its status screen does not

Opening FIGHT with 0xA6 crashed Red, Blue and Yellow. In Red and Blue the copy of the name under the cursor never found an end marker at all, and the game ended in its classic crash; in Yellow that copy did end, and the game crashed there all the same. The status screen (page 2) builds the move list a second way, and there the same name wrote 596 bytes, 552 past the list (595 and 551 in Yellow), over the same party data, and the game survived: back on the party menu, with the party overwritten. A save at that moment would keep it.

From the ROM

The whole page rests on a few lines of the game's source, from pret's disassembly. The last real move is number 165. Tap a move to read its number, and watch the list stop at Struggle.

Struggle is move $A5, decimal 165, and the game defines NUM_ATTACKS as exactly that. Every ID above it, $A6 and up, has no constant and no name.
; constants/move_constants.asm
    const SUBSTITUTE   ; a4
    const STRUGGLE     ; a5
DEF NUM_ATTACKS EQU const_value - 1   ; = 165

; engine/battle/core.asm, GetCurrentMove: six bytes from Moves + (move - 1) * 6
	ld [wNameListIndex], a
	dec a
	ld hl, Moves
	ld bc, MOVE_LENGTH
	call AddNTimes

; home/names2.asm, GetName: any number from $C4 (HM01) up is named as a TM or HM
	cp HM01
	jp nc, GetMachineName

; engine/battle/core.asm, ExecutePlayerMove: $FF means "cannot move"
	ld a, [wPlayerSelectedMove]
	ASSERT CANNOT_MOVE == $ff
	inc a
	jp z, ExecutePlayerMoveDone

In the built games, the move table sits at $4000 in bank $0E and the base stats table starts at $43DE, exactly 165 times 6 bytes later, in Red, Blue and Yellow alike.

How I tested this

Every result on this page comes from running the game's own code, not from reading it. The games are dumps of my own Red, Blue and Yellow cartridges, checked byte for byte against the games the pret disassemblies build.

Questions

What is Super Glitch in Pokemon Red and Blue?

Super Glitch is the community's name for the glitch moves 0xA6 to 0xC3 (166 to 195), the 30 move numbers right after Struggle, the last real move. The game has no names for them, so it reads each name past the end of its move-name list, out of whatever is in memory, and copying such a name can run on and write over memory. In my tests, opening FIGHT with 0xA6 crashed Red, Blue and Yellow.

Which moves are glitch moves?

Every move number the game can hold that is not one of the 165 real moves: 0x00 and 0xA6 to 0xFF, 91 in each game. 0xA6 to 0xC3 are the Super Glitches. 0xC4 to 0xFF are named HM01 to HM05 and TM01 to TM55, because the name routine treats every number from 0xC4 up as a TM or HM. 0x00 is the empty slot.

Does Super Glitch crash the game or ruin my save?

It can do both. In my Red and Blue test battles, 15 of the 30 Super Glitches crashed the game and 3 froze it when I opened FIGHT or used them, and in Yellow 15 crashed it and 2 froze it. A long name writes over your party, the Pokedex flags, the bag, the money, the rival's name, the options and the badges, all of which the game saves. On the status screen, 0xA6's name wrote 552 bytes over that data and the game carried on, so saving afterwards would keep the damage.

Is Super Glitch different in Yellow?

In the details, yes. Yellow's bytes differ from Red and Blue's on 33 of the 91 glitch moves, because its base stats table differs. Its 0xA7 and 0xA8 take their names from data in the cartridge rather than from memory, and 0xA7's is blank. And in my Yellow test battle a foe using a Super Glitch softlocked the game instead of crashing it: 18 softlocks and no crashes.

What does TM55, move 0xFF, do?

Nothing, ever. The battle engine uses $FF to mean that a Pokemon cannot move, so when 0xFF is chosen the turn is skipped without a word, for you or a foe. It also has 0 PP, so you can never pick it yourself.

Why do Super Glitch names change?

Because they are not stored anywhere. The game finds a move's name by counting end markers from the start of the name list, and for 0xA7 to 0xC3 that count runs out of the list and on through video memory and work memory, so a different screen, party or foe moves every name after it. When I ran the FIGHT menu in two emulators side by side, only 6 of the 30 Super Glitch names in Red came out the same in both, 9 in Blue and 7 of the 30 in Yellow.

How do you get a glitch move?

From a glitch Pokemon. Real Pokemon learn no glitch move, and TMs and HMs teach only real moves. Some glitch Pokemon know glitch moves from level 1 or learn them as they level up: in Red, glitch Pokemon 0xD4 learns 0xA6 at level 97. The data file lists every one.

Was this tested on a Game Boy?

No. I ran the cartridge's own code in the PyBoy emulator and replayed every run in a second copy of it, and I checked the FIGHT menu names in a second emulator, gambatte. Nothing here was run on a Game Boy or a 3DS.

Sources

The family it belongs to

Super Glitch is one member of a family, and they all share a single idea: the game reads memory it was never meant to read, and treats whatever it finds as real. Move names here, species numbers next door, your own name down the hall. Pick a relative.

Every one of these is the same trick pointed at a different table: moves, species, or names. Learn one and the rest click into place, which is exactly why they are gathered in the Glitchhouse.

Related specimens

Go deeper: the Gen 1 battler | the Gen 1 glitch data | the Name Glitch tool | the Mew glitch | browse the Glitchhouse.