Similar to how my scrawling schoolboy script has deteriorated through decades of digital document creation, my natural urge to stop and save a game diminished. I attribute this to the emergence of automatic saving, save points, console quick-resume features, and experiences where the risk feels so great that I instinctively save every two seconds for fear of catastrophic failure. However, I am human. I get lazy. And this week, I was taught a vital reminder after significant time invested in the recently released Pokémon FireRed for Nintendo Switch: you still gotta smash that save button.
It had been years since I engaged with a pixel-art Pokémon adventure — as I skipped the GBA era, the Johto region games probably were the last mainline Poké-title I invested in. Consequently, I was thrilled to pay the asking price for a trip down memory lane to the Kanto region, and an attempt gathering those first 151 creatures. I quickly returned to my youth. Over a few successive evenings, I snagged Caterpie and Weedle, added Pikachu to my team, knocked out Brock with ease, invested in the future Gyarados from the salesman in the Pokémon Center, and scaled Mt. Moon without a worry in the world.
The problem: I failed to save even once! And it never crossed my mind.
That Jigglypuff shall never find love with my Mankey.
Disaster struck during a session where I didn’t play FireRed… and when my child took the console for a quick half-hour of the newer Pokémon title instead, closing my game to do so. As any Switch user understands (as I should have known…) opening a new game on Switch forces the closure of any software running. Your data is only preserved following an automatic save or after a manual save prior to changing games. Oops.
The Evolution of Game Saves: From Intentional to Invisible
One could view autosave, now so invisible its operation is largely unconscious, as a bona fide “next-generation” innovation. Although the classic text game Zork implemented a pioneering save functions in a game, 1986’s The Legend of Zelda is often credited as a milestone moment for not feeling totally ruined after a game over because of persistent memory saves in NES games. Obviously, the responsibility remained to save. (And once you erred), the lesson was learned for life. Through the 1990s, save cards for systems such as the PS1 popularized saving but remained precarious; failing to save (or having a card corrupt) could erase countless hours. Games like Resident Evil even turned saving into a scarce commodity.
Modern autosave, that eroded my natural saving reflex my FireRed run like a dope, took hold at the dawn of a new century. The original Halo pioneered seamless respawn points as the Call of Duty series honed the approach to smooth difficulty and reduce tedious replay. As experiences became more vast — and increasingly non-linear — devs cracked the code of persistent, invisible saving and, in time, the pinnacle of suspend/resume.
Pokémon's Own Journey: From Manual Ritual to Modern Convenience
Funny enough, the world of Pokémon serves as a perfect mirror of that historical progression. For decades, saving in a Pokémon game required a manual command: players were trained to select the Save option before closing their device. Starting with Pokémon Sword and Shield on the hybrid console, Game Freak implemented autosave (initially optional), representing a substantial design shift for a franchise known as most tradition-bound franchises.
I must confess my error: A long tenure with Breath of the Wild and recent platformers utterly weakened my instinct to save. I am still wary under specific circumstances — I refuse to chance quitting during a run in something like Hades 2 despite being aware it has a robust save system — however, perhaps due to my extended absence from into a retro-style game, or I’ve just been spoiled, I didn't even think to manually save before redocking. The child I once was would not have made such a mistake so catastrophically.
The Consequences: Starting From Scratch
I have not picked up FireRed since my save debacle. Upon rebooting the game to see I had only my starter Squirtle, a wave of exhaustion hit me. Status condition: Burned.
Maybe I’ll go back… or I could just continue playing the ocean of contemporary releases released constantly that operate under the assumption I am incapable of manual saving. Nevertheless, my fondness for older titles isn’t dead. On occasions when I can convince my daughter away from the modern, auto-saving Pokémon game, we have been cooperatively playing a collection of classic Bomberman games. Those classic titles had no save system at all opting instead for cryptic character strings. Therefore, if I meet an explosive end, the setback is minimal. That provides some small solace.