The Glitchhouse · Gen 1 battle bugs

Hyper Beam's recharge in Pokemon Red, Blue and Yellow

In Gen 1 the strongest move in the game often costs nothing. Here is exactly when Hyper Beam skips its recharge turn, why, and what the other side can do to it.

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. In Pokemon Red, Blue and Yellow, Hyper Beam only has to recharge when it hits and the target survives. If it knocks the target out, misses, has no effect (on a Ghost), or breaks a Substitute, there is no recharge turn, because the game sets the recharge in the very last step of the move and skips that step in all four cases. The other side can also cancel a recharge with Wrap, Bind, Fire Spin or Clamp, a flinch, or a sleep move.

Your Tauros has HYPER BEAM. Knock out the Pikachu (no rest), hit the Chansey (it must recharge), then break its SUBSTITUTE (no rest again).Try it in the battler

Every case

Hyper Beam's turnRecharge next turn?Why
Hits, the target survivesYesthe last step runs and sets the flag
Hits, the target faintsNo"don't do anything else if the enemy fainted": the move ends first
MissesNoa miss ends the move before the last step
Has no effect (the target is a Ghost)Nothe type chart takes the damage to 0, which counts as a miss
Breaks a SubstituteNoa broken Substitute zeroes the attacker's move effect
Hits a Substitute that survivesYesthe effect is untouched

Hyper Beam's damage is huge, so most of these come up all the time. A level 100 Tauros knocks out a level 100 Pikachu every time it hits: 307 to 361 damage against 273 HP.

Will it have to recharge?

Pick the two Pokemon (level 100, with the battler's stats: DV 15 and full stat experience) and how much HP the target has left. The odds below count every roll the game makes: the hit roll, the critical hit roll and the 39 damage rolls.

Target

Why: the recharge is the move's last step

Hyper Beam's effect, HyperBeamEffect (engine/battle/effects.asm in pret's disassembly), does one thing: it sets the NEEDS_TO_RECHARGE flag. It is not one of the effects the game runs early, so it waits for the end of ExecutePlayerMove (and its twin for the other side), and the end is only reached when nothing stopped the move:

; the end of ExecutePlayerMove, pret pokered engine/battle/core.asm
	ld a, [wMoveMissed]
	and a
	jr z, .moveDidNotMiss
	call PrintMoveFailureText
	...
	jp ExecutePlayerMoveDone      ; missed: done, no recharge
	...
	ld hl, wEnemyMonHP
	ld a, [hli]
	ld b, [hl]
	or b
	ret z ; don't do anything else if the enemy fainted
	...
	ld a, [wPlayerMoveEffect]
	and a
	jp z, ExecutePlayerMoveDone   ; effect wiped by a broken Substitute
	...
	call nc, JumpMoveEffect       ; HyperBeamEffect: recharge next turn

The Substitute case comes from AttackSubstitute: when a Substitute breaks, the routine writes 0 over the attacker's move effect. The same line is why Explosion does not faint its user when it breaks a Substitute (see the Substitute bugs).

What the other side can do to a recharging Pokemon

Which games

How I checked it

Tauros against a Pikachu and a Chansey with SUBSTITUTE: three Hyper Beams, three different answers.Try it in the battler

Questions

Does Hyper Beam need to recharge after a KO in Gen 1?

No. In Pokemon Red, Blue and Yellow, Hyper Beam sets the recharge flag only in the last step of the move, and the game stops before that step when the target has fainted. So a Hyper Beam that knocks out its target needs no recharge turn, and the user can act normally the next turn.

When else does Hyper Beam skip the recharge in Red and Blue?

When it misses (it hits 229 times in 256), when it has no effect (on a Ghost-type Pokemon), and when it breaks a Substitute, because breaking a Substitute wipes the attacker's move effect. It only has to recharge when it hits and the target survives, or when it hits a Substitute that survives.

Can the opponent cancel Hyper Beam's recharge?

Yes, in three ways. A trapping move (Wrap, Bind, Fire Spin, Clamp) clears it before its own hit roll, so even one that misses frees the user. A flinch clears it. And a sleep move used on a recharging Pokemon clears it and skips all its own checks: it always lands and replaces any status the Pokemon had.

Is Hyper Beam different in Pokemon Yellow?

Mostly the same, with one difference: in a Yellow link battle, any hit by a move that can make the target flinch (Stomp, Headbutt, Bite and the rest) clears the recharge, even when no flinch happens. In Red and Blue only a real flinch does.

Was Hyper Beam changed in Gold and Silver?

Yes. In Gold, Silver and Crystal the recharge is set before the game checks for a faint (the move's script in pret's disassembly), so a knockout no longer skips it.

Was this tested on a real Game Boy?

No. I read the routines in pret's disassembly and ran battles in the game's own code in the PyBoy emulator, in Red and in Yellow, with the random numbers set to make each case happen. The battler's engine matched the game in every one.

More Gen 1 battle bugs