1636 Pokemon Fire Red Squirrels [hot] File

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

Let me rewind to the historical parallel. The year is 1636 CE in the human calendar. In our world, that year marks the height of the Little Ice Age, the founding of Harvard College, and the beginning of the Pequot War in New England. But in the lore of Pokémon FireRed , 1636 is the year a cartographer named Ezekiel “Red” Maple, an ancestor of Professor Oak, sailed from the port of Vermilion City to explore the uncharted “Sinnoh Tangle.” His ship, The S.S. Anne , was lost at sea for six weeks. When he returned, he was clutching a small, burnt diary. The diary contained a single sketch: a rodent with a curled, fiery tail, storing nuts in a tree hollow. Below the sketch, written in faded ink, was the word “Risukooru” — an archaic transliteration of “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. 1636 pokemon fire red squirrels

The fan community, upon learning of my discovery via a long-defunct Geocities forum, went wild. Theories exploded. Some claimed that “1636” was a nod to the year of the first recorded forest fire in Japanese history (which is historically inaccurate—the first major recorded fire was in 1657, the Great Meireki Fire, but the fanatics rounded down). Others argued it was a developer’s inside joke: a tribute to a childhood pet squirrel that had chewed through a power cord and fried a development kit in October 1636 of the Japanese calendar? That made no sense, but the internet loved it.

For context, there are no squirrels in Kanto. Not one. The region boasts electric mice, beavers, psychic foxes, and even living piles of sludge, but the humble squirrel— Sciurus vulgaris —is conspicuously absent. This is a botanical mystery, as Kanto is filled with oak and chestnut trees. Yet, in the 1636th line of the Pokémon species database, a ghost of a creature stirs. Most historians dismiss this as a sailor’s fever dream

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.

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.” The year is 1636 CE in the human calendar

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.’”