1636 Pokemon Fire Red Squirrels _verified_ (2024)

Most historians dismiss this as a sailor’s fever dream. But the code in FireRed tells a different story.

Why does it matter? Because every time you play FireRed and walk through the tall grass of Route 1, the game’s RNG cycles through 1,500 possible encounter slots. Slot 1636 is empty. But for a single frame, the game almost looks there. If you press A at the exact moment the frame hits, the screen will flash orange for a millisecond. That is the FireRed Squirrel. It is not a Pokémon. It is a memory of a memory—a burnt acorn stored in a tree hollow that no longer exists, in a forest that burned down three hundred and seventy years before the first Pokémon game was ever conceived. 1636 pokemon fire red squirrels

The truth, I believe, is more melancholic. In the final, stable build of FireRed , the squirrel was erased. Its cry (a mix of a chirp and a crackle) was reassigned to the move “Sweet Scent.” Its sprite data was overwritten by a placeholder tree tile. But the 0x1636 index remained, a digital fossil. It’s what programmers call a “ghost in the machine”—a remnant of an idea that was too strange for the final product: a squirrel that survived a fire in 1636, only to be deleted in 2004. Most historians dismiss this as a sailor’s fever dream

When I activated the 0x1636 glitch using a GameShark, my Game Boy Advance screen flickered. The usual battle music warped into a low, humming drone. And there it stood on the virtual grass of Route 1: a Squirrel. Not a Pikachu. Not a Sandshrew. A pixelated, orange-furred squirrel with a single stripe down its back and eyes that glowed like embers. Its Pokédex entry, a garbled mess of Japanese characters and English phonemes, read: “This Pokémon fled the burning forests of 1636. It hides in the time-between-frames. It knows only the move ‘Ember Cache.’” Because every time you play FireRed and walk

It began not with a bang, but with a rustle. In the autumn of 2004, while datamining the newly released Pokémon FireRed Version , I stumbled upon a hexadecimal sequence that should not have existed. The address was 0x1636. Within the game’s code, nestled between the cry data for Rattata and the sprite pointers for Spearow, lay a set of 12 unused bytes. When forced to compile, they generated a creature the fandom would later call the “FireRed Squirrel.”

So the next time you hear a rustle in the bushes outside, or see a squirrel bury a nut with frantic, purposeful energy, consider this: it might be hiding an Ember. It might be waiting for the right player to press A at frame 1636. And if you ever manage to catch it? Do not save. Do not trade it. Let it run back into the time-between-frames, where the autumn of 1636 never ends, and the forests of Kanto are still full of fire-colored squirrels.

End of log.