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.
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.
- Hyper Beam hits 229 times in 256 (it is a 90% move), and every miss is a free turn.
- A Substitute breaks Hyper Beam's recharge. Breaking one wipes the attacker's move effect, so a Hyper Beam into a Substitute is free. If the Substitute survives the hit, the recharge stays.
- Being frozen while it must recharge leaves your Pokemon with no menu at all: see the freeze glitch.
- Tested in the game's own code in an emulator, in Red and Yellow, every case. How I checked it.
Every case
| Hyper Beam's turn | Recharge next turn? | Why |
|---|---|---|
| Hits, the target survives | Yes | the last step runs and sets the flag |
| Hits, the target faints | No | "don't do anything else if the enemy fainted": the move ends first |
| Misses | No | a miss ends the move before the last step |
| Has no effect (the target is a Ghost) | No | the type chart takes the damage to 0, which counts as a miss |
| Breaks a Substitute | No | a broken Substitute zeroes the attacker's move effect |
| Hits a Substitute that survives | Yes | the 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.
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
- Wrap, Bind, Fire Spin and Clamp free it.
TrappingEffectclears the recharge flag before the trapping move rolls to hit, so even a trapping move that misses takes the recharge away. (pret: "the target won't need to recharge even if the trapping move missed".) In my test a Dragonite's Wrap missed, and the Tauros it missed used Hyper Beam again the next turn. - A flinch frees it. When a flinch lands,
FlinchSideEffectclears the recharge too. - A sleep move always lands on it.
SleepEffectclears the recharge flag, and when the flag was set it jumps past every check: "already asleep", "already has a status" and the hit roll. So Sleep Powder or Hypnosis on a recharging Pokemon never misses, and it replaces whatever status the Pokemon had. In my test a paralyzed Tauros, which Sleep Powder could not touch, fell asleep the turn it had to recharge. - Freezing it does not. When the other side freezes your recharging Pokemon, the flag stays, and that locks your menu: the freeze glitch. (When you freeze the other side's Pokemon, its flag is cleared.)
Which games
- Red and Blue: everything above.
- Yellow: the same, plus one difference. In a link battle, Yellow's
FlinchSideEffectclears the recharge whenever a move that can make the target flinch hits, before it rolls for the flinch. In my test, Snorlax's Headbutt with no flinch left Red's Tauros recharging, and Yellow's Tauros free. - Gold, Silver and Crystal: changed. In pret's disassemblies of Gold and Crystal, Hyper Beam's move script sets the recharge (
rechargenextturn) before it checks for a faint (checkfaint), so a knockout no longer skips the recharge. I read this; I did not run them.
How I checked it
- Read:
ExecutePlayerMove,ExecuteEnemyMove,HyperBeamEffect,AttackSubstitute,TrappingEffect,FlinchSideEffect,SleepEffectandFreezeBurnParalyzeEffectin pret's pokered and pokeyellow. - Run in the game: Red and Yellow under the PyBoy emulator, with the battler's battle oracle setting the rolls. One battle went through every case in order: a Tauros knocked out a Pikachu (no recharge), hit a Chansey that survived (recharge), broke its Substitute (no recharge), missed (no recharge), knocked it out, and did nothing to a Gengar (no recharge). Others covered a missed Wrap, Sleep Powder on a paralyzed, recharging Tauros, and Headbutt in Red and in Yellow. The battler's engine matched the game on every byte, message and battle state.
- The calculator uses the game's damage arithmetic, which a test compares with the battler's engine.
- Not tested: the Gen 2 games and anything on a real Game Boy.
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.