The Glitchhouse · Gen 1 battle bugs

The Focus Energy bug in Pokemon Red, Blue and Yellow

The move that is supposed to raise your critical hit chance lowers it instead. Here is the one wrong instruction behind it, and the exact odds for all 151 Pokemon.

By GardenFlouer · tested in the game's own code in an emulator, 10 November 2026 · part of The Glitchhouse and Gen 1 battle bugs

The short answer. Focus Energy is bugged in Pokemon Red, Blue and Yellow: instead of raising your critical hit chance, it cuts it to about a quarter. The game's critical hit routine halves a number where it should double it, so after Focus Energy (or a Dire Hit) a Scyther's SLASH lands a critical hit 104 times in 256 instead of 255, and its QUICK ATTACK 13 times in 256 instead of 52. Gold, Silver and Crystal fixed it.

Your Scyther knows FOCUS ENERGY, SLASH and QUICK ATTACK, against a Chansey that only heals. Watch the critical hit chance in Why did that happen? before and after.Try it in the battler

Your Pokemon's critical hit chance, with and without Focus Energy

Pick a Pokemon and a kind of move. The numbers are worked out the way the game works them out, step by step, and the board shows all 256 values the game's random byte can take: the green ones are critical hits.

Move
Focus Energy
a critical hitno critical hit

The wrong instruction

The routine is CriticalHitTest in the game's battle engine (engine/battle/core.asm in pret's disassembly of Red and Blue). It loads the attacker's base Speed and halves it. Then it checks the Focus Energy flag, GETTING_PUMPED. Without the flag it doubles the number with sla b. With the flag it was supposed to double it again, but it runs srl b, a shift to the right: it halves it.

; CriticalHitTest, pret pokered engine/battle/core.asm
	ld a, [wMonHBaseSpeed]
	ld b, a
	srl b                ; base Speed / 2
	...
	bit GETTING_PUMPED, a
	jr nz, .focusEnergyUsed
	sla b                ; x 2 (capped at 255)
	...
.focusEnergyUsed
	srl b                ; / 2: the bug
	...
	srl b                ; / 2 again for an ordinary move
	...                  ; or x 2, x 2 for SLASH and the others
	call BattleRandom
	rlc a
	rlc a
	rlc a                ; the random byte, rotated left 3 times
	cp b                 ; a critical hit if it is below the threshold

pret's own comment on that line: "bug: using focus energy causes a shift to the right instead of left, resulting in 1/4 the usual crit chance".

So the two paths part by a factor of 4 right there: one doubles, the other halves. For Scyther, whose base Speed is 105:

StepWithoutWith Focus Energy
base Speed / 25252
the Focus Energy stepx 2 = 104/ 2 = 26
QUICK ATTACK (an ordinary move): / 252 in 25613 in 256
SLASH: x 2, then x 2 (capped at 255)255 in 256104 in 256

The rotation at the end (rlc a three times) moves the random byte's bits around but keeps every value distinct, so it changes which bytes crit, never how many. That is why the board above has a striped pattern.

Nothing else goes in. The level, the Attack stat, stat stages and the target never touch the chance, and Speed means the species' base Speed, not the Pokemon's Speed stat. A Pokemon that used Transform takes its target's species, so it uses the target's base Speed.

All 151 Pokemon, before and after Focus Energy

Critical hits out of 256. The high critical column only matters for the Pokemon that learn one of the four high critical moves, but the game would treat any of them the same way. The fastest Pokemon lose the most: Electrode goes from 70 to 17.

PokemonBase SpeedOrdinarywith FEHigh critwith FE
Bulbasaur4522517644
Ivysaur6030724060
Venusaur80401025580
Charmander6532825564
Charmeleon80401025580
Charizard1005012255100
Squirtle4321516840
Wartortle5829723256
Blastoise7839925576
Caterpie4522517644
Metapod3015312028
Butterfree7035825568
Weedle5025620048
Kakuna3517413632
Beedrill7537925572
Pidgey5628722456
Pidgeotto7135825568
Pidgeot91451125588
Rattata7236925572
Raticate97481225596
Spearow7035825568
Fearow1005012255100
Ekans5527621652
Arbok80401025580
Pikachu90451125588
Raichu1005012255100
Sandshrew4020516040
Sandslash6532825564
Nidoran♀4120516040
Nidorina5628722456
Nidoqueen7638925576
Nidoran♂5025620048
Nidorino6532825564
Nidoking85421025584
Clefairy3517413632
Clefable6030724060
Vulpix6532825564
Ninetales1005012255100
Jigglypuff201028020
Wigglytuff4522517644
Zubat5527621652
Golbat90451125588
Oddish3015312028
Gloom4020516040
Vileplume5025620048
Paras251239624
Parasect3015312028
Venonat4522517644
Venomoth90451125588
Diglett95471125592
Dugtrio1206015255120
Meowth90451125588
Persian1155714255112
Psyduck5527621652
Golduck85421025584
Mankey7035825568
Primeape95471125592
Growlithe6030724060
Arcanine95471125592
Poliwag90451125588
Poliwhirl90451125588
Poliwrath7035825568
Abra90451125588
Kadabra1055213255104
Alakazam1206015255120
Machop3517413632
Machoke4522517644
Machamp5527621652
Bellsprout4020516040
Weepinbell5527621652
Victreebel7035825568
Tentacool7035825568
Tentacruel1005012255100
Geodude201028020
Graveler3517413632
Golem4522517644
Ponyta90451125588
Rapidash1055213255104
Slowpoke15715612
Slowbro3015312028
Magnemite4522517644
Magneton7035825568
Farfetch'd6030724060
Doduo7537925572
Dodrio1005012255100
Seel4522517644
Dewgong7035825568
Grimer251239624
Muk5025620048
Shellder4020516040
Cloyster7035825568
Gastly80401025580
Haunter95471125592
Gengar1105513255108
Onix7035825568
Drowzee4221516840
Hypno6733825564
Krabby5025620048
Kingler7537925572
Voltorb1005012255100
Electrode1407017255140
Exeggcute4020516040
Exeggutor5527621652
Cubone3517413632
Marowak4522517644
Hitmonlee87431025584
Hitmonchan7638925576
Lickitung3015312028
Koffing3517413632
Weezing6030724060
Rhyhorn251239624
Rhydon4020516040
Chansey5025620048
Tangela6030724060
Kangaskhan90451125588
Horsea6030724060
Seadra85421025584
Goldeen6331724860
Seaking6834825568
Staryu85421025584
Starmie1155714255112
Mr.Mime90451125588
Scyther1055213255104
Jynx95471125592
Electabuzz1055213255104
Magmar93461125592
Pinsir85421025584
Tauros1105513255108
Magikarp80401025580
Gyarados81401025580
Lapras6030724060
Ditto4824619248
Eevee5527621652
Vaporeon6532825564
Jolteon1306516255128
Flareon6532825564
Porygon4020516040
Omanyte3517413632
Omastar5527621652
Kabuto5527621652
Kabutops80401025580
Aerodactyl1306516255128
Snorlax3015312028
Articuno85421025584
Zapdos1005012255100
Moltres90451125588
Dratini5025620048
Dragonair7035825568
Dragonite80401025580
Mewtwo1306516255128
Mew1005012255100

Which games have it

How I checked it

See it yourself: Scyther and a Chansey that only heals. Use SLASH, then FOCUS ENERGY, then SLASH, and open Why did that happen? under the battle screen.Try it in the battler

Questions

Does Focus Energy work in Pokemon Red and Blue?

No. In Pokemon Red, Blue and Yellow, Focus Energy lowers your critical hit chance to about a quarter of what it was. The game's CriticalHitTest routine shifts a number right where it should shift it left, so the chance is halved instead of doubled. Scyther's Slash drops from 255 in 256 to 104 in 256, and its Quick Attack from 52 in 256 to 13 in 256.

What does Dire Hit do in Gen 1?

The same as Focus Energy. The Dire Hit item sets the very same flag in battle (ItemUseDireHit sets GETTING_PUMPED), so it lowers your critical hit chance to about a quarter too. It wears off when the Pokemon switches out.

How is the critical hit chance worked out in Gen 1?

Only from the attacker's base Speed and the move. An ordinary move crits when a random byte, rotated left three times, is below half the base Speed, so the chance is base Speed / 2 out of 256. Karate Chop, Razor Leaf, Crabhammer and Slash use 8 times that, capped at 255 out of 256. Level, stat changes and the target do not count.

Was the Focus Energy bug ever fixed?

Yes, in Gold, Silver and Crystal. Their critical hit routine (BattleCommand_Critical in pret's disassembly) adds one to a critical hit stage when Focus Energy is up, so it raises the chance as intended.

Does a second Focus Energy make it worse?

No. The flag can only be set once: a second Focus Energy says But, it failed! and changes nothing. The chance stays at its lowered value until the Pokemon switches out or Haze clears the flag.

Was this tested on a real Game Boy?

No. I read the routine in pret's disassembly of Red, Blue and Yellow, and ran it in the game's own code in the PyBoy emulator: battles where the random byte was set just under and just at each threshold, before and after Focus Energy, in Red and in Yellow. Every one matched the battler's engine.

More Gen 1 battle bugs