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.
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.
- The numbers are not random. The move table ends at Struggle (0xA5), and the base stats table comes right after it, so 0xA6 reads Bulbasaur's base stats and works as Jump Kick, with 45 accuracy out of 256 and 1 PP.
- All 91 glitch moves (0x00 and 0xA6 to 0xFF) are in the table below for Red and Blue and for Yellow: the six bytes, what each one does, and whether it crashed, froze or locked up in my tests. 23 of them have 0 PP, so you can never pick them.
- 0xFF (TM55) never runs: the game reads $FF as "cannot move" and skips the turn.
- How I tested it: the game's own code, run in the PyBoy emulator from a crafted battle by button presses, every run replayed in a second copy of PyBoy. Only the FIGHT menu names were also run in a second emulator, gambatte, and the two disagree on most Super Glitch names, so no name of a Super Glitch here is "the" name. The method.
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.
- Anim, Effect, Power, Type, Acc., PP are the six bytes the game loads for a move. Accuracy is out of 256: a random byte below it hits. PP is the low six bits of its byte; the top two are PP Ups.
- What it does is the move with its name kept to 20 bytes, so the effect shows on its own. A type byte that is not one of the 15 real types matches no row of the type chart, so it is neutral against everything.
- In my tests is what the game did in my test battle: opening FIGHT with the move first in the list, using it, a foe using it, the same with the name kept short, and the status screen. A crash or freeze from the name depends on what is in memory, so it is one sample, not a rule.
- Try it opens the battler with a glitch Pokemon that knows only that move as the computer's Pokemon (the battler shows it as a challenge), with Red and Blue's bytes. The battler runs the game's battle code and ends the battle where my runs saw the game crash or freeze. A move with 0 PP has no link: the computer plays by link battle rules, which keep PP.
| Move | Name | Anim | Effect | Power | Type | Acc. | PP | What it does | In my tests | Battler |
|---|---|---|---|---|---|---|---|---|---|---|
0x00 0 | none (dashes) | 90 | $74 | 102 | $7A | 80 | 13 | The empty move: with it first, FIGHT shows only dashes, yet A picks it. Then: damage, then a jump past the effect table into other code | Freezes A foe whose only move is 0x00 freezes the game choosing a move. | builder, slot 1 |
0xA6 166 | 20 zero bytes | 1 | $2D | 49 | $31 | 45 | 1 +1 up | Acts as Jump Kick, the effect of Jump Kick and Hi Jump Kick | Crashes Opening FIGHT crashes the game (its name). The foe using it crashes the game (its name). | Try it |
0xA7 167 | from memory | 22 | $03 | 45 | $40 | 85 | 0 never pickable | Acts as drain HP, the effect of Absorb, Mega Drain and Leech Life | No crash seen | 0 PP |
0xA8 168 | from memory | 64 | $E5 | 64 | $21 | 45 | 0 never pickable | Damage, then a jump past the effect table into other code | Crashes 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 169 | from memory | 0 | $03 | 164 | $03 Poison | 56 | 0 +3 up never pickable | Acts as drain HP, the effect of Absorb, Mega Drain and Leech Life | Crashes Opening FIGHT crashes the game (its name). The foe using it crashes the game (its name). | 0 PP |
0xAA 170 | from memory | 3 | $08 | 6 | $00 Normal | 2 | 60 | Acts as Dream Eater, the effect of Dream Eater | Crashes Opening FIGHT freezes the game (its name). The foe using it crashes the game (its name). | Try it |
0xAB 171 | from memory | 62 | $3F | 60 | $50 | 22 | 3 | Acts as evasion down 2, an effect no real move has | No crash seen | Try it |
0xAC 172 | from memory | 45 | $8D | 102 | $2B | 80 | 23 +1 up | Damage, then Special up 1's code runs with the wrong byte ($8D): the stat code reads past its stat table | Crashes Opening FIGHT crashes the game (its name). The foe using it crashes the game (its name). | Try it |
0xAD 173 | from memory | 81 | $21 | 45 | $49 | 0 | 3 | Acts as may poison, the effect of Smog and Sludge | No crash seen | Try it |
0xAE 174 | from memory | 164 | $03 | 56 | $C0 | 3 | 8 | Acts as drain HP, the effect of Absorb, Mega Drain and Leech Life | No crash seen | Try it |
0xAF 175 | from memory | 6 | $00 | 3 | $50 | 82 | 19 +1 up | Damage only | No crash seen | Try it |
0xB0 176 | from memory | 80 | $64 | 22 | $03 Poison | 45 | 16 +3 up | Damage, then a jump past the effect table into other code | Crashes Opening FIGHT crashes the game (its name). The foe using it crashes the game (its name). | Try it |
0xB1 177 | from memory | 119 | $62 | 65 | $97 | 67 | 33 | Damage, then a jump past the effect table into other code | Crashes 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 178 | from memory | 45 | $49 | 22 | $03 Poison | 164 | 3 +1 up | Acts as unused effect $49, an effect no real move has | Crashes Opening FIGHT crashes the game (its name). The foe using it crashes the game (its name). | Try it |
0xB3 179 | from memory | 56 | $C0 | 3 | $08 Ghost | 6 | 0 never pickable | Damage, then Light Screen's code runs with the wrong byte ($C0) | Crashes The foe using it crashes the game (its name). | 0 PP |
0xB4 180 | from memory | 4 | $27 | 52 | $2B | 65 | 50 | Acts as charge, then attack, the effect of Razor Wind, Solarbeam and others | Crashes Opening FIGHT crashes the game (its name). Its status screen (page 2) softlocks the game. | Try it |
0xB5 181 | from memory | 20 | $14 | 45 | $41 | 85 | 28 +1 up | Acts as Speed down 1, the effect of String Shot | Crashes Opening FIGHT freezes the game (its name). The foe using it crashes the game (its name). | Try it |
0xB6 182 | from memory | 92 | $5C | 93 | $0A | 45 | 0 never pickable | Damage, then a jump past the effect table into other code | Crashes Opening FIGHT freezes the game (its name). The foe using it crashes the game (its name). | 0 PP |
0xB7 183 | from memory | 0 | $03 | 181 | $03 Poison | 79 | 8 +3 up | Acts as drain HP, the effect of Absorb, Mega Drain and Leech Life | Crashes Opening FIGHT crashes the game (its name). The foe using it crashes the game (its name). | Try it |
0xB8 184 | from memory | 227 | $08 | 38 | $00 Normal | 5 | 58 | Acts as Dream Eater, the effect of Dream Eater | No crash seen | Try it |
0xB9 185 | from memory | 64 | $3A | 80 | $41 | 20 | 20 | Acts as Attack down 2, an effect no real move has | Crashes The foe using it crashes the game (its name). | Try it |
0xBA 186 | from memory | 45 | $8E | 102 | $0C | 95 | 8 +1 up | Damage, then accuracy up 1's code runs with the wrong byte ($8E): the stat code reads past its stat table | Crashes The foe using it crashes the game (its name). | Try it |
0xBB 187 | from memory | 96 | $0A | 45 | $34 | 0 | 3 | Acts as Attack up 1, the effect of Meditate and Sharpen | Crashes Opening FIGHT crashes the game (its name). | Try it |
0xBC 188 | from memory | 181 | $03 | 79 | $C8 | 227 | 8 | Acts as drain HP, the effect of Absorb, Mega Drain and Leech Life | Crashes Using it crashes the game (its name). | Try it |
0xBD 189 | from memory | 38 | $00 | 6 | $4E | 84 | 14 +1 up | Damage only | No crash seen | Try it |
0xBE 190 | from memory | 100 | $55 | 20 | $02 Flying | 45 | 17 +3 up | Acts as Splash, the effect of Splash | Crashes Using it crashes the game (its name). The foe using it crashes the game (its name). | Try it |
0xBF 191 | from memory | 119 | $86 | 98 | $95 | 100 | 10 | Damage, then may paralyze's code runs with the wrong byte ($86) | No crash seen | Try it |
0xC0 192 | from memory | 45 | $34 | 43 | $03 Poison | 181 | 3 +1 up | Acts as Speed up 2, the effect of Agility | Crashes Opening FIGHT crashes the game (its name). | Try it |
0xC1 193 | from memory | 79 | $CE | 227 | $08 Ghost | 38 | 0 never pickable | Damage, then unused effect $4E's code runs with the wrong byte ($CE): that table entry is empty, so the game jumps to address $0000 | Crashes Opening FIGHT crashes the game (its name). | 0 PP |
0xC2 194 | from memory | 7 | $2C | 48 | $41 | 43 | 50 | Acts as hit twice, the effect of Double Kick and Bonemerang | Crashes Opening FIGHT crashes the game (its name). | Try it |
0xC3 195 | from memory | 21 | $15 | 45 | $42 | 85 | 56 +2 up | Acts as Special down 1, an effect no real move has | Crashes The foe using it crashes the game (its name). | Try it |
0xC4 196 | HM01 | 93 | $8F | 94 | $21 | 39 | 0 never pickable | Damage, then evasion up 1's code runs with the wrong byte ($8F): the stat code reads past its stat table | No crash seen | 0 PP |
0xC5 197 | HM02 | 0 | $03 | 177 | $3F | 15 | 8 +3 up | Acts as drain HP, the effect of Absorb, Mega Drain and Leech Life | No crash seen | Try it |
0xC6 198 | HM03 | 131 | $08 | 50 | $00 Normal | 8 | 59 | Acts as Dream Eater, the effect of Dream Eater | No crash seen | Try it |
0xC7 199 | HM04 | 63 | $50 | 58 | $41 | 21 | 21 | Acts as Hyper Beam's recharge, the effect of Hyper Beam | No crash seen | Try it |
0xC8 200 | HM05 | 45 | $8F | 102 | $B1 | 96 | 49 +3 up | Damage, then evasion up 1's code runs with the wrong byte ($8F): the stat code reads past its stat table | No crash seen | Try it |
0xC9 201 | TM01 | 97 | $21 | 39 | $91 | 0 | 3 | Acts as may poison, the effect of Smog and Sludge | No crash seen | Try it |
0xCA 202 | TM02 | 177 | $3F | 15 | $C8 | 131 | 8 | Acts as evasion down 2, an effect no real move has | No crash seen | Try it |
0xCB 203 | TM03 | 50 | $00 | 9 | $4F | 83 | 36 +1 up | Damage only | No crash seen | Try it |
0xCC 204 | TM04 | 78 | $55 | 21 | $15 Water | 45 | 18 +3 up | Acts as Splash, the effect of Splash | No crash seen | Try it |
0xCD 205 | TM05 | 119 | $37 | 118 | $51 | 120 | 33 | Acts as evasion up 2, an effect no real move has | No crash seen | Try it |
0xCE 206 | TM06 | 39 | $91 | 55 | $03 Poison | 177 | 63 +1 up | Damage, then Swift's code runs with the wrong byte ($91): that table entry is empty, so the game jumps to address $0000 | Crashes Its effect crashes the game for you and the foe, even with its name kept short. | Try it |
0xCF 207 | TM07 | 15 | $CE | 131 | $08 Ghost | 50 | 0 never pickable | Damage, then unused effect $4E's code runs with the wrong byte ($CE): that table entry is empty, so the game jumps to address $0000 | Crashes Its effect crashes the game when a foe uses it, even with its name kept short. | 0 PP |
0xD0 208 | TM08 | 10 | $2D | 30 | $23 | 45 | 20 | Acts as Jump Kick, the effect of Jump Kick and Hi Jump Kick | No crash seen | Try it |
0xD1 209 | TM09 | 7 | $07 | 255 | $35 | 85 | 9 +1 up | Acts as explode, the effect of Selfdestruct and Explosion | No crash seen | Try it |
0xD2 210 | TM10 | 74 | $E1 | 74 | $21 | 81 | 0 never pickable | Damage, then a jump past the effect table into other code | No crash seen | 0 PP |
0xD3 211 | TM11 | 0 | $00 | 0 | $00 Normal | 0 | 0 never pickable | Does nothing | No crash seen | 0 PP |
0xD4 212 | TM12 | 0 | $00 | 0 | $00 Normal | 11 | 50 | Does nothing | No crash seen | Try it |
0xD5 213 | TM13 | 20 | $37 | 30 | $19 Ice | 7 | 7 | Acts as evasion up 2, an effect no real move has | No crash seen | Try it |
0xD6 214 | TM14 | 120 | $48 | 85 | $3A | 75 | 8 +3 up | Acts as unused effect $48, an effect no real move has | No crash seen | Try it |
0xD7 215 | TM15 | 75 | $6A | 0 | $00 Normal | 0 | 0 never pickable | Damage, then a jump past the effect table to $A778, inside cartridge RAM (the save data), and runs it as code | Crashes Its effect crashes the game when a foe uses it, even with its name kept short. | 0 PP |
0xD8 216 | TM16 | 0 | $00 | 0 | $00 Normal | 0 | 0 never pickable | Does nothing | No crash seen | 0 PP |
0xD9 217 | TM17 | 0 | $00 | 12 | $3C | 45 | 50 | Damage only | No crash seen | Try it |
0xDA 218 | TM18 | 70 | $50 | 7 | $02 Flying | 45 | 32 +2 up | Acts as Hyper Beam's recharge, the effect of Hyper Beam | No crash seen | Try it |
0xDB 219 | TM19 | 119 | $37 | 76 | $0E | 78 | 29 +1 up | Acts as evasion up 2, an effect no real move has | No crash seen | not in the battler |
0xDC 220 | TM20 | 0 | $00 | 0 | $00 Normal | 42 | 3 +1 up | Does nothing | No crash seen | Try it |
0xDD 221 | TM21 | 56 | $F0 | 67 | $28 | 2 | 0 never pickable | Damage, then a jump past the effect table into other code | No crash seen | 0 PP |
0xDE 222 | TM22 | 13 | $28 | 35 | $1E | 50 | 20 | Acts as Super Fang, the effect of Super Fang | No crash seen | not in the battler |
0xDF 223 | TM23 | 7 | $03 | 255 | $34 | 85 | 61 +1 up | Acts as drain HP, the effect of Absorb, Mega Drain and Leech Life | No crash seen | Try it |
0xE0 224 | TM24 | 117 | $24 | 118 | $28 | 81 | 0 never pickable | Acts as may paralyze, the effect of Body Slam and Lick | No crash seen | 0 PP |
0xE1 225 | TM25 | 0 | $00 | 0 | $00 Normal | 0 | 0 never pickable | Does nothing | No crash seen | 0 PP |
0xE2 226 | TM26 | 0 | $00 | 0 | $00 Normal | 14 | 45 | Does nothing | No crash seen | Try it |
0xE3 227 | TM27 | 25 | $32 | 35 | $19 Ice | 7 | 3 | Acts as Attack up 2, the effect of Swords Dance | No crash seen | Try it |
0xE4 228 | TM28 | 120 | $47 | 85 | $77 | 118 | 54 | Acts as may lower Special, the effect of Psychic | No crash seen | Try it |
0xE5 229 | TM29 | 119 | $6A | 0 | $00 Normal | 0 | 0 never pickable | Damage, then a jump past the effect table to $A778, inside cartridge RAM (the save data), and runs it as code | Crashes Its effect crashes the game when a foe uses it, even with its name kept short. | 0 PP |
0xE6 230 | TM30 | 0 | $00 | 0 | $00 Normal | 0 | 0 never pickable | Does nothing | No crash seen | 0 PP |
0xE7 231 | TM31 | 0 | $00 | 15 | $41 | 80 | 40 | Damage only | No crash seen | Try it |
0xE8 232 | TM32 | 75 | $2D | 7 | $03 Poison | 45 | 31 +2 up | Acts as Jump Kick, the effect of Jump Kick and Hi Jump Kick | No crash seen | Try it |
0xE9 233 | TM33 | 119 | $88 | 119 | $80 | 121 | 31 | Damage, then Dream Eater's code runs with the wrong byte ($88) | No crash seen | Try it |
0xEA 234 | TM34 | 0 | $00 | 0 | $00 Normal | 36 | 3 +1 up | Does nothing | No crash seen | Try it |
0xEB 235 | TM35 | 24 | $C0 | 195 | $08 Ghost | 6 | 0 never pickable | Damage, then Light Screen's code runs with the wrong byte ($C0) | No crash seen | 0 PP |
0xEC 236 | TM36 | 16 | $28 | 45 | $28 | 56 | 35 | Acts as Super Fang, the effect of Super Fang | No crash seen | Try it |
0xED 237 | TM37 | 0 | $02 | 255 | $37 | 85 | 39 +2 up | Acts as may poison, the effect of Poison Sting | No crash seen | not in the battler |
0xEE 238 | TM38 | 69 | $5B | 70 | $10 | 0 | 0 never pickable | Damage, then a jump past the effect table into other code | No crash seen | 0 PP |
0xEF 239 | TM39 | 0 | $03 | 42 | $03 Poison | 8 | 0 +3 up never pickable | Acts as drain HP, the effect of Absorb, Mega Drain and Leech Life | No crash seen | 0 PP |
0xF0 240 | TM40 | 67 | $0C | 10 | $00 Normal | 17 | 63 | Acts as Speed up 1, an effect no real move has | No crash seen | Try it |
0xF1 241 | TM41 | 60 | $37 | 71 | $32 | 0 | 2 | Acts as evasion up 2, an effect no real move has | No crash seen | Try it |
0xF2 242 | TM42 | 120 | $71 | 102 | $0A | 120 | 27 +1 up | Damage, then a jump past the effect table into other code | Red: 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 243 | TM43 | 121 | $10 | 28 | $00 Normal | 0 | 3 | Acts as Pay Day, the effect of Pay Day | No crash seen | Try it |
0xF4 244 | TM44 | 42 | $03 | 8 | $C0 | 67 | 12 | Acts as drain HP, the effect of Absorb, Mega Drain and Leech Life | No crash seen | Try it |
0xF5 245 | TM45 | 10 | $00 | 18 | $53 | 80 | 11 +1 up | Damage only | No crash seen | Try it |
0xF6 246 | TM46 | 91 | $46 | 0 | $02 Flying | 45 | 44 +2 up | Acts as may lower Speed, the effect of Bubblebeam, Constrict and Bubble | No crash seen | Try it |
0xF7 247 | TM47 | 119 | $C2 | 121 | $79 | 123 | 16 | Damage, then poison's code runs with the wrong byte ($C2) | No crash seen | Try it |
0xF8 248 | TM48 | 28 | $62 | 0 | $03 Poison | 42 | 3 +1 up | Damage, 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 249 | TM49 | 8 | $C0 | 67 | $0C | 10 | 0 never pickable | Damage, then Light Screen's code runs with the wrong byte ($C0) | No crash seen | 0 PP |
0xFA 250 | TM50 | 19 | $1E | 56 | $23 | 72 | 25 | Acts as unused effect $1E, an effect no real move has | No crash seen | Try it |
0xFB 251 | TM51 | 0 | $00 | 255 | $39 | 85 | 42 +1 up | Damage only | No crash seen | not in the battler |
0xFC 252 | TM52 | 79 | $41 | 80 | $21 | 39 | 0 never pickable | Acts as Reflect, the effect of Reflect | No crash seen | 0 PP |
0xFD 253 | TM53 | 0 | $00 | 160 | $2F | 136 | 9 +3 up | Damage only | No crash seen | Try it |
0xFE 254 | TM54 | 194 | $08 | 2 | $00 Normal | 20 | 55 | Acts as Dream Eater, the effect of Dream Eater | No crash seen | Try it |
0xFF 255 | TM55 | 81 | $3C | 97 | $32 | 0 | 0 never pickable | Never runs: the game reads move $FF as "cannot move" and skips the turn | No crash seen | 0 PP |
| Move | Name | Anim | Effect | Power | Type | Acc. | PP | What it does | In my tests |
|---|---|---|---|---|---|---|---|---|---|
0x00 0 ≠| none (dashes) | 90 | $74 | 102 | $31 | 81 | 10 | The empty move: with it first, FIGHT shows only dashes, yet A picks it. Then: damage, then a jump past the effect table into echo RAM | Freezes A foe whose only move is 0x00 freezes the game choosing a move. |
0xA6 166 | 20 zero bytes | 1 | $2D | 49 | $31 | 45 | 1 +1 up | Acts as Jump Kick, the effect of Jump Kick and Hi Jump Kick | Crashes Opening FIGHT crashes the game (its name). The foe using it softlocks the game (its name). |
0xA7 167 | blank (from ROM) | 22 | $03 | 45 | $40 | 85 | 0 never pickable | Acts as drain HP, the effect of Absorb, Mega Drain and Leech Life | No crash seen |
0xA8 168 ≠| from ROM, runs on | 64 | $E4 | 64 | $21 | 45 | 0 never pickable | Damage, then a jump past the effect table into other code | Crashes Opening FIGHT crashes the game (its name). The foe using it softlocks the game (its name). |
0xA9 169 | from memory | 0 | $03 | 164 | $03 Poison | 56 | 0 +3 up never pickable | Acts as drain HP, the effect of Absorb, Mega Drain and Leech Life | No crash seen |
0xAA 170 | from memory | 3 | $08 | 6 | $00 Normal | 2 | 60 | Acts as Dream Eater, the effect of Dream Eater | Crashes Opening FIGHT crashes the game (its name). The foe using it softlocks the game (its name). |
0xAB 171 | from memory | 62 | $3F | 60 | $50 | 22 | 3 | Acts as evasion down 2, an effect no real move has | Crashes Opening FIGHT crashes the game (its name). The foe using it softlocks the game (its name). |
0xAC 172 ≠| from memory | 45 | $8D | 102 | $E9 | 79 | 51 +1 up | Damage, then Special up 1's code runs with the wrong byte ($8D): the stat code reads past its stat table | Freezes Opening FIGHT freezes the game (its name). The foe using it softlocks the game (its name). |
0xAD 173 | from memory | 81 | $21 | 45 | $49 | 0 | 3 | Acts as may poison, the effect of Smog and Sludge | No crash seen |
0xAE 174 | from memory | 164 | $03 | 56 | $C0 | 3 | 8 | Acts as drain HP, the effect of Absorb, Mega Drain and Leech Life | Crashes Opening FIGHT crashes the game (its name). The foe using it softlocks the game (its name). |
0xAF 175 | from memory | 6 | $00 | 3 | $50 | 82 | 19 +1 up | Damage only | No crash seen |
0xB0 176 | from memory | 80 | $64 | 22 | $03 Poison | 45 | 16 +3 up | Damage, then a jump past the effect table into other code | No crash seen |
0xB1 177 ≠| from memory | 119 | $61 | 65 | $81 | 67 | 33 | Damage, then a jump past the effect table into other code | Crashes Its effect crashes the game when the foe uses it, even with its name kept short. |
0xB2 178 | from memory | 45 | $49 | 22 | $03 Poison | 164 | 3 +1 up | Acts as unused effect $49, an effect no real move has | Crashes Opening FIGHT crashes the game (its name). The foe using it softlocks the game (its name). |
0xB3 179 | from memory | 56 | $C0 | 3 | $08 Ghost | 6 | 0 never pickable | Damage, 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 180 | from memory | 4 | $27 | 52 | $2B | 65 | 50 | Acts as charge, then attack, the effect of Razor Wind, Solarbeam and others | Crashes 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 memory | 20 | $14 | 45 | $41 | 85 | 48 +3 up | Acts as Speed down 1, the effect of String Shot | Crashes Opening FIGHT crashes the game (its name). The foe using it softlocks the game (its name). |
0xB6 182 ≠| from memory | 93 | $FC | 94 | $0A | 45 | 0 never pickable | Damage, then a jump past the effect table into other code | Softlocks The foe using it softlocks the game (its name). |
0xB7 183 | from memory | 0 | $03 | 181 | $03 Poison | 79 | 8 +3 up | Acts as drain HP, the effect of Absorb, Mega Drain and Leech Life | Crashes Opening FIGHT crashes the game (its name). |
0xB8 184 | from memory | 227 | $08 | 38 | $00 Normal | 5 | 58 | Acts as Dream Eater, the effect of Dream Eater | Crashes Opening FIGHT crashes the game (its name). The foe using it softlocks the game (its name). |
0xB9 185 | from memory | 64 | $3A | 80 | $41 | 20 | 20 | Acts as Attack down 2, an effect no real move has | Crashes Opening FIGHT crashes the game (its name). |
0xBA 186 ≠| from memory | 45 | $8E | 102 | $C8 | 96 | 37 | Damage, then accuracy up 1's code runs with the wrong byte ($8E): the stat code reads past its stat table | Crashes Opening FIGHT crashes the game (its name). The foe using it softlocks the game (its name). |
0xBB 187 ≠| from memory | 98 | $0A | 45 | $34 | 0 | 3 | Acts as Attack up 1, the effect of Meditate and Sharpen | Crashes Opening FIGHT crashes the game (its name). The foe using it softlocks the game (its name). |
0xBC 188 | from memory | 181 | $03 | 79 | $C8 | 227 | 8 | Acts as drain HP, the effect of Absorb, Mega Drain and Leech Life | No crash seen |
0xBD 189 | from memory | 38 | $00 | 6 | $4E | 84 | 14 +1 up | Damage only | Crashes Using it crashes the game (its name). The foe using it softlocks the game (its name). |
0xBE 190 | from memory | 100 | $55 | 20 | $02 Flying | 45 | 17 +3 up | Acts as Splash, the effect of Splash | Softlocks The foe using it softlocks the game (its name). |
0xBF 191 ≠| from memory | 119 | $A9 | 100 | $00 Normal | 103 | 10 | Damage, then fixed damage's code runs with the wrong byte ($A9): that table entry is empty, so the game jumps to address $0000 | Crashes Opening FIGHT crashes the game (its name). Its effect crashes the game for you and the foe, even with its name kept short. |
0xC0 192 | from memory | 45 | $34 | 43 | $03 Poison | 181 | 3 +1 up | Acts as Speed up 2, the effect of Agility | No crash seen |
0xC1 193 ≠| from memory | 79 | $CE | 227 | $08 Ghost | 46 | 0 never pickable | Damage, then unused effect $4E's code runs with the wrong byte ($CE): that table entry is empty, so the game jumps to address $0000 | No crash seen |
0xC2 194 | from memory | 7 | $2C | 48 | $41 | 43 | 50 | Acts as hit twice, the effect of Double Kick and Bonemerang | No crash seen |
0xC3 195 ≠| from memory | 21 | $15 | 45 | $42 | 85 | 24 +1 up | Acts as Special down 1, an effect no real move has | Softlocks The foe using it softlocks the game (its name). |
0xC4 196 ≠| HM01 | 95 | $4B | 96 | $21 | 39 | 0 never pickable | Acts as unused effect $4B, an effect no real move has | No crash seen |
0xC5 197 | HM02 | 0 | $03 | 177 | $3F | 15 | 8 +3 up | Acts as drain HP, the effect of Absorb, Mega Drain and Leech Life | No crash seen |
0xC6 198 | HM03 | 131 | $08 | 50 | $00 Normal | 8 | 59 | Acts as Dream Eater, the effect of Dream Eater | No crash seen |
0xC7 199 | HM04 | 63 | $50 | 58 | $41 | 21 | 21 | Acts as Hyper Beam's recharge, the effect of Hyper Beam | No crash seen |
0xC8 200 ≠| HM05 | 45 | $8F | 102 | $8E | 98 | 20 | Damage, then evasion up 1's code runs with the wrong byte ($8F): the stat code reads past its stat table | No crash seen |
0xC9 201 ≠| TM01 | 100 | $21 | 39 | $91 | 0 | 3 | Acts as may poison, the effect of Smog and Sludge | No crash seen |
0xCA 202 | TM02 | 177 | $3F | 15 | $C8 | 131 | 8 | Acts as evasion down 2, an effect no real move has | No crash seen |
0xCB 203 | TM03 | 50 | $00 | 9 | $4F | 83 | 36 +1 up | Damage only | No crash seen |
0xCC 204 | TM04 | 78 | $55 | 21 | $15 Water | 45 | 18 +3 up | Acts as Splash, the effect of Splash | No crash seen |
0xCD 205 ≠| TM05 | 119 | $FA | 117 | $0B | 120 | 33 | Damage, then a jump past the effect table into echo RAM | Crashes Its effect crashes the game for you and the foe, even with its name kept short. |
0xCE 206 | TM06 | 39 | $91 | 55 | $03 Poison | 177 | 63 +1 up | Damage, then Swift's code runs with the wrong byte ($91): that table entry is empty, so the game jumps to address $0000 | Crashes Its effect crashes the game for you and the foe, even with its name kept short. |
0xCF 207 | TM07 | 15 | $CE | 131 | $08 Ghost | 50 | 0 never pickable | Damage, then unused effect $4E's code runs with the wrong byte ($CE): that table entry is empty, so the game jumps to address $0000 | No crash seen |
0xD0 208 | TM08 | 10 | $2D | 30 | $23 | 45 | 20 | Acts as Jump Kick, the effect of Jump Kick and Hi Jump Kick | No crash seen |
0xD1 209 ≠| TM09 | 7 | $07 | 255 | $35 | 85 | 5 | Acts as explode, the effect of Selfdestruct and Explosion | No crash seen |
0xD2 210 ≠| TM10 | 75 | $E8 | 75 | $21 | 81 | 0 never pickable | Damage, then a jump past the effect table into other code | Crashes |
0xD3 211 | TM11 | 0 | $00 | 0 | $00 Normal | 0 | 0 never pickable | Does nothing | No crash seen |
0xD4 212 | TM12 | 0 | $00 | 0 | $00 Normal | 11 | 50 | Does nothing | No crash seen |
0xD5 213 | TM13 | 20 | $37 | 30 | $19 Ice | 7 | 7 | Acts as evasion up 2, an effect no real move has | No crash seen |
0xD6 214 ≠| TM14 | 120 | $48 | 85 | $41 | 76 | 46 +3 up | Acts as unused effect $48, an effect no real move has | No crash seen |
0xD7 215 ≠| TM15 | 76 | $6A | 0 | $00 Normal | 0 | 0 never pickable | Damage, then a jump past the effect table to $A778, inside cartridge RAM (the save data), and runs it as code | Crashes Its effect crashes the game when a foe uses it, even with its name kept short. |
0xD8 216 | TM16 | 0 | $00 | 0 | $00 Normal | 0 | 0 never pickable | Does nothing | No crash seen |
0xD9 217 | TM17 | 0 | $00 | 12 | $3C | 45 | 50 | Damage only | No crash seen |
0xDA 218 | TM18 | 70 | $50 | 7 | $02 Flying | 45 | 32 +2 up | Acts as Hyper Beam's recharge, the effect of Hyper Beam | No crash seen |
0xDB 219 ≠| TM19 | 119 | $5D | 77 | $34 | 79 | 29 +1 up | Damage, then a jump past the effect table into other code | No crash seen |
0xDC 220 | TM20 | 0 | $00 | 0 | $00 Normal | 42 | 3 +1 up | Does nothing | No crash seen |
0xDD 221 ≠| TM21 | 56 | $F0 | 67 | $28 | 66 | 0 never pickable | Damage, then a jump past the effect table into the link cable routine, which waits for a link partner forever | No crash seen |
0xDE 222 | TM22 | 13 | $28 | 35 | $1E | 50 | 20 | Acts as Super Fang, the effect of Super Fang | No crash seen |
0xDF 223 ≠| TM23 | 7 | $03 | 255 | $34 | 85 | 2 | Acts as drain HP, the effect of Absorb, Mega Drain and Leech Life | No crash seen |
0xE0 224 ≠| TM24 | 119 | $B4 | 119 | $28 | 81 | 0 never pickable | Damage, then Speed up 2's code runs with the wrong byte ($B4): the stat code reads past its stat table | No crash seen |
0xE1 225 | TM25 | 0 | $00 | 0 | $00 Normal | 0 | 0 never pickable | Does nothing | No crash seen |
0xE2 226 | TM26 | 0 | $00 | 0 | $00 Normal | 14 | 45 | Does nothing | No crash seen |
0xE3 227 | TM27 | 25 | $32 | 35 | $19 Ice | 7 | 3 | Acts as Attack up 2, the effect of Swords Dance | No crash seen |
0xE4 228 ≠| TM28 | 120 | $47 | 85 | $07 Bug | 120 | 9 +3 up | Acts as may lower Special, the effect of Psychic | No crash seen |
0xE5 229 ≠| TM29 | 120 | $6A | 0 | $00 Normal | 0 | 0 never pickable | Damage, then a jump past the effect table to $A778, inside cartridge RAM (the save data), and runs it as code | Crashes Its effect crashes the game when a foe uses it, even with its name kept short. |
0xE6 230 | TM30 | 0 | $00 | 0 | $00 Normal | 0 | 0 never pickable | Does nothing | No crash seen |
0xE7 231 | TM31 | 0 | $00 | 15 | $41 | 80 | 40 | Damage only | No crash seen |
0xE8 232 | TM32 | 75 | $2D | 7 | $03 Poison | 45 | 31 +2 up | Acts as Jump Kick, the effect of Jump Kick and Hi Jump Kick | No crash seen |
0xE9 233 ≠| TM33 | 119 | $1B | 121 | $2A | 123 | 31 | Acts as Thrash, the effect of Thrash and Petal Dance | No crash seen |
0xEA 234 | TM34 | 0 | $00 | 0 | $00 Normal | 36 | 3 +1 up | Does nothing | No crash seen |
0xEB 235 | TM35 | 24 | $C0 | 195 | $08 Ghost | 6 | 0 never pickable | Damage, then Light Screen's code runs with the wrong byte ($C0) | No crash seen |
0xEC 236 | TM36 | 16 | $28 | 45 | $28 | 56 | 35 | Acts as Super Fang, the effect of Super Fang | No crash seen |
0xED 237 ≠| TM37 | 0 | $02 | 255 | $37 | 85 | 53 +3 up | Acts as may poison, the effect of Poison Sting | No crash seen |
0xEE 238 ≠| TM38 | 69 | $E6 | 70 | $10 | 0 | 0 never pickable | Damage, then a jump past the effect table into other code | No crash seen |
0xEF 239 | TM39 | 0 | $03 | 42 | $03 Poison | 8 | 0 +3 up never pickable | Acts as drain HP, the effect of Absorb, Mega Drain and Leech Life | No crash seen |
0xF0 240 | TM40 | 67 | $0C | 10 | $00 Normal | 17 | 63 | Acts as Speed up 1, an effect no real move has | No crash seen |
0xF1 241 | TM41 | 60 | $37 | 71 | $32 | 0 | 2 | Acts as evasion up 2, an effect no real move has | No crash seen |
0xF2 242 ≠| TM42 | 120 | $71 | 102 | $C6 | 118 | 43 | Damage, then a jump past the effect table into other code | Crashes 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 ≠| TM43 | 120 | $10 | 28 | $00 Normal | 0 | 3 | Acts as Pay Day, the effect of Pay Day | No crash seen |
0xF4 244 | TM44 | 42 | $03 | 8 | $C0 | 67 | 12 | Acts as drain HP, the effect of Absorb, Mega Drain and Leech Life | No crash seen |
0xF5 245 | TM45 | 10 | $00 | 18 | $53 | 80 | 11 +1 up | Damage only | No crash seen |
0xF6 246 | TM46 | 91 | $46 | 0 | $02 Flying | 45 | 44 +2 up | Acts as may lower Speed, the effect of Bubblebeam, Constrict and Bubble | No crash seen |
0xF7 247 ≠| TM47 | 119 | $92 | 120 | $D1 | 122 | 16 | Damage, then Attack down 1's code runs with the wrong byte ($92): the stat code reads past its stat table | No crash seen |
0xF8 248 | TM48 | 28 | $62 | 0 | $03 Poison | 42 | 3 +1 up | Damage, then a jump past the effect table into other code | No crash seen |
0xF9 249 | TM49 | 8 | $C0 | 67 | $0C | 10 | 0 never pickable | Damage, then Light Screen's code runs with the wrong byte ($C0) | No crash seen |
0xFA 250 | TM50 | 19 | $1E | 56 | $23 | 72 | 25 | Acts as unused effect $1E, an effect no real move has | No crash seen |
0xFB 251 ≠| TM51 | 0 | $00 | 255 | $39 | 85 | 3 | Damage only | No crash seen |
0xFC 252 ≠| TM52 | 80 | $F8 | 80 | $21 | 39 | 0 never pickable | Damage, then a jump past the effect table into other code | No crash seen |
0xFD 253 | TM53 | 0 | $00 | 160 | $2F | 136 | 9 +3 up | Damage only | No crash seen |
0xFE 254 | TM54 | 194 | $08 | 2 | $00 Normal | 20 | 55 | Acts as Dream Eater, the effect of Dream Eater | No crash seen |
0xFF 255 | TM55 | 81 | $3C | 97 | $32 | 0 | 0 never pickable | Never runs: the game reads move $FF as "cannot move" and skips the turn | No 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.
| Move | Bytes | Where they come from |
|---|---|---|
0xA6 | 1 $2D 49 $31 45 65 | Bulbasaur: Pokedex No. 1, base HP 45, Attack 49, Defense 49, Speed 45, Special 65 |
0xFF TM55 | 81 $3C 97 $32 0 0 | Raticate: base Attack 81, Defense 60, Speed 97, Special 50, and its two types, Normal and Normal (0) |
0x00 | 90 $74 102 $7A 80 13 | Raticate: 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)
0x00Raticate (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)0xA6Bulbasaur (No. 1): Pokedex No., base HP, base Attack, base Defense, base Speed, base Special: 1 45 49 49 45 65 (Yellow: the same bytes)0xA7Bulbasaur (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)0xA8Bulbasaur (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)0xA9Bulbasaur (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)0xAABulbasaur (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)0xABIvysaur (No. 2): base Attack, base Defense, base Speed, base Special, type 1, type 2: 62 63 60 80 22 3 (Yellow: the same bytes)0xACIvysaur (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)0xADIvysaur (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)0xAEIvysaur (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)0xAFIvysaur (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)0xB0Venusaur (No. 3): base Speed, base Special, type 1, type 2, catch rate, base experience: 80 100 22 3 45 208 (Yellow: the same bytes)0xB1Venusaur (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)0xB2Venusaur (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)0xB3Venusaur (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)0xB4Charmander (No. 4): Pokedex No., base HP, base Attack, base Defense, base Speed, base Special: 4 39 52 43 65 50 (Yellow: the same bytes)0xB5Charmander (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)0xB6Charmander (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)0xB7Charmander (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)0xB8Charmander (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)0xB9Charmeleon (No. 5): base Attack, base Defense, base Speed, base Special, type 1, type 2: 64 58 80 65 20 20 (Yellow: the same bytes)0xBACharmeleon (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)0xBBCharmeleon (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)0xBCCharmeleon (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)0xBDCharmeleon (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)0xBECharizard (No. 6): base Speed, base Special, type 1, type 2, catch rate, base experience: 100 85 20 2 45 209 (Yellow: the same bytes)0xBFCharizard (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)0xC0Charizard (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)0xC1Charizard (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)0xC2Squirtle (No. 7): Pokedex No., base HP, base Attack, base Defense, base Speed, base Special: 7 44 48 65 43 50 (Yellow: the same bytes)0xC3Squirtle (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)0xC4Squirtle (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)0xC5Squirtle (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)0xC6Squirtle (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)0xC7Wartortle (No. 8): base Attack, base Defense, base Speed, base Special, type 1, type 2: 63 80 58 65 21 21 (Yellow: the same bytes)0xC8Wartortle (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)0xC9Wartortle (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)0xCAWartortle (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)0xCBWartortle (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)0xCCBlastoise (No. 9): base Speed, base Special, type 1, type 2, catch rate, base experience: 78 85 21 21 45 210 (Yellow: the same bytes)0xCDBlastoise (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)0xCEBlastoise (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)0xCFBlastoise (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)0xD0Caterpie (No. 10): Pokedex No., base HP, base Attack, base Defense, base Speed, base Special: 10 45 30 35 45 20 (Yellow: the same bytes)0xD1Caterpie (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)0xD2Caterpie (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)0xD3Caterpie (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)0xD4Caterpie (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)0xD5Metapod (No. 11): base Attack, base Defense, base Speed, base Special, type 1, type 2: 20 55 30 25 7 7 (Yellow: the same bytes)0xD6Metapod (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)0xD7Metapod (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)0xD8Metapod (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)0xD9Metapod (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)0xDAButterfree (No. 12): base Speed, base Special, type 1, type 2, catch rate, base experience: 70 80 7 2 45 160 (Yellow: the same bytes)0xDBButterfree (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)0xDCButterfree (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)0xDDButterfree (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)0xDEWeedle (No. 13): Pokedex No., base HP, base Attack, base Defense, base Speed, base Special: 13 40 35 30 50 20 (Yellow: the same bytes)0xDFWeedle (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)0xE0Weedle (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)0xE1Weedle (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)0xE2Weedle (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)0xE3Kakuna (No. 14): base Attack, base Defense, base Speed, base Special, type 1, type 2: 25 50 35 25 7 3 (Yellow: the same bytes)0xE4Kakuna (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)0xE5Kakuna (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)0xE6Kakuna (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)0xE7Kakuna (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)0xE8Beedrill (No. 15): base Speed, base Special, type 1, type 2, catch rate, base experience: 75 45 7 3 45 159 (Yellow: the same bytes)0xE9Beedrill (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)0xEABeedrill (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)0xEBBeedrill (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)0xECPidgey (No. 16): Pokedex No., base HP, base Attack, base Defense, base Speed, base Special: 16 40 45 40 56 35 (Yellow: the same bytes)0xEDPidgey (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)0xEEPidgey (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)0xEFPidgey (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)0xF0Pidgey (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)0xF1Pidgeotto (No. 17): base Attack, base Defense, base Speed, base Special, type 1, type 2: 60 55 71 50 0 2 (Yellow: the same bytes)0xF2Pidgeotto (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)0xF3Pidgeotto (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)0xF4Pidgeotto (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)0xF5Pidgeotto (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)0xF6Pidgeot (No. 18): base Speed, base Special, type 1, type 2, catch rate, base experience: 91 70 0 2 45 172 (Yellow: the same bytes)0xF7Pidgeot (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)0xF8Pidgeot (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)0xF9Pidgeot (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)0xFARattata (No. 19): Pokedex No., base HP, base Attack, base Defense, base Speed, base Special: 19 30 56 35 72 25 (Yellow: the same bytes)0xFBRattata (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)0xFCRattata (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)0xFDRattata (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)0xFERattata (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)0xFFRaticate (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.
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.
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.
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:
Yellow, standard battle, PyBoy:
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.
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.
; 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.
- One test battle. A save I wrote stands in Pallet Town with all badges and one Pokemon, a level 50 Lapras with perfect DVs. The game's own battle start then begins a wild battle with a level 50 Snorlax, and every test starts from that moment, in each game. Text speed fast, battle style Set, animations on.
- Each move, five ways. Lapras using it from the first slot (opening FIGHT, picking it, the turn). The same with its name kept to 20 bytes: the byte right after the name buffer set to the end marker before every name lookup, so the name cannot run over memory and the effect shows on its own. The Snorlax using it, both ways. The status screen's move list. And the FIGHT menu again in a second battle with other Pokemon, to see how much the name depends on memory. A move with 0 PP was given 10 PP for the kept-short run, to see what it would do.
- Watching. Every name lookup, every name copy and the bytes it wrote, the six bytes the game loaded, every jump to an effect's code, the damage formula, misses, animations, the battle before and after, and every line of text, all read from memory or from the game reaching one of its own routines. No screenshot decided anything.
- Replayed. Every run was recorded button by button and replayed in a second copy of PyBoy with no hooks at all, and it counted only when both ended with the same memory, byte for byte. All completed runs agreed: 448 each in Red and Blue, 454 in Yellow. Runs that stopped the emulator have no replay.
- When the game does not come back. A crash is the main program stuck in the rst $38 loop at $0038, the classic Gen 1 crash. A freeze is the main program stuck in the cartridge's code, no longer waiting for the next frame, and a softlock is frames still coming but the game never getting back. A CPU lock-up is the CPU reaching one of the Game Boy's unused opcodes, which stops PyBoy. The Game Boy's CPU is documented to lock up on those too; I did not run that, and I did not trace which instruction it was.
- One emulator, mostly. Only the FIGHT menu names were also run in gambatte, which times the video chip the way the console does, and it disagreed with PyBoy on most Super Glitch names. Everything else here rests on PyBoy alone, and every hit, miss and damage roll is one sample from one battle. Nothing here was run on a Game Boy or a 3DS.
- From the code, not from a run: why the engine does what the runs show (the effect lists, GetName's TM and HM rule, the meaning of $FF), read in pret's source.
- Yellow, on both hardware paths. Yellow checks at power-on whether it is on a Game Boy or a Game Boy Color and runs extra color code on the Color. The Yellow numbers on this page are from the Game Boy run. Everything structural is the same on both: the bytes, the names' sources, the overflow sizes, the 0 PP moves and where the failing jumps go. What a given Super Glitch then does in a battle is a sample of whatever its name walk found in memory, and that differs between the two paths just as it differs between two runs: the Color run of this battle had two moves stop the CPU from the FIGHT menu, the Game Boy run none.
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
- My Glitch Lab runs of every glitch move in Red, Blue and Yellow, 31 October 2026, published as the glitch move data file (JSON and CSV).
- pret's disassemblies of Pokemon Red, Blue and Yellow (pokered and pokeyellow): constants/move_constants.asm, home/names2.asm (GetName), engine/battle/core.asm (GetCurrentMove, ExecutePlayerMove, the effect checks, the enemy's move choice), data/moves/moves.asm and data/pokemon/base_stats.asm.
- The battler, held to the game event for event in 724 glitch move battles per game.
- The glitch community, on the Glitch City Wiki and Bulbapedia, for the name Super Glitch and decades of notes on these moves, and TheZzazzGlitch, who mapped ways to steer the corruption with what is on screen. I have not tested those methods here.
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.
Related specimens
Go deeper: the Gen 1 battler | the Gen 1 glitch data | the Name Glitch tool | the Mew glitch | browse the Glitchhouse.