In the same way my scrawling teenage penmanship has deteriorated across a quarter-century of typing on computers, so too have stop and save a game diminished. The culprit is the rise of automatic saving, checkpoints, console quick-resume features, and games with such high stakes that I can’t help but save constantly for fear of catastrophic failure. Yet, I am fallible. Laziness creeps in. Recently, I was taught a vital reminder eight hours into the newly ported Pokémon FireRed on Nintendo's console: you still gotta smash that save button.
A long time had passed since I last played a classic Pokémon title — having missed the boat on the Game Boy Advance, the Generation II titles probably were the most recent traditional Pokémon journey I played. Consequently, I was thrilled to spend twenty dollars for the sentimental journey back to Kanto, and an attempt gathering those first 151 creatures. I was instantly transported to a simpler time. Over a few successive evenings, I snagged Caterpie and Weedle, added Pikachu to my team, defeated the first Gym Leader with ease, took a chance on purchasing the Magikarp from a shady character, and traversed Mt. Moon completely unconcerned.
The critical error: Not once did I save! And it never crossed my mind.
Alas, Jigglypuff can never find love with my Mankey.
The catastrophe occurred during a session where I didn’t play FireRed… and as my daughter took the console for a quick half-hour of the latest game instead, shutting down my session to do so. As is common knowledge (something I temporarily forgot…) opening a new game on the system will close your current game. Your progress is only safe following an automatic save or if you remembered to save prior to changing games. My mistake.
The Progression of Save Systems: From Deliberate to Seamless
One could view automatic saving, now so seamless many gamers take it for granted, as a bona fide “cutting-edge” breakthrough. Whereas the early computer game Zork featured among the first save functions in a game, the original NES Legend of Zelda is often credited as a milestone moment because players no longer felt utterly defeated after a game over thanks to persistent memory saves on NES cartridges. Obviously, the responsibility remained to save. (And following a single mistake), it was a mistake made only once. Through the 1990s, save cards for systems including the original PlayStation made saving more common but remained precarious; forgetting to save (or losing a card) could erase countless hours. The survival horror series Resident Evil took it further by transforming saving into a scarce commodity.
Contemporary background saving, that eroded my natural saving reflex my Pokémon adventure so effectively, took hold in the early 2000s. Halo: Combat Evolved introduced checkpoint saving while Call of Duty honed the approach to ease frustration and eliminate repetition. As the play grew longer — and increasingly non-linear — devs cracked the code for saving without interruption and, finally, the pinnacle of instant on/off.
Pokémon's Own Journey: From Conscious Choice to Unconscious Backup
Interestingly, this iconic franchise offers a clear snapshot of how saving has changed. For decades, saving in a Pokémon game was manual: fans were taught to manually record their data ahead of powering down their Game Boy or DS. The shift began with Pokémon Sword and Shield for the Nintendo Switch, the series introduced autosave (at first as a toggleable option), representing a substantial philosophical change for one of gaming’s slowest-changing series.
I own up to my blunder: Countless hours spent in Breath of the Wild and recent platformers utterly weakened my instinct to save. I am still wary in some cases — I refuse to chance exiting prematurely in a challenging indie title although I know full well it autosaves after chambers — but be it because the lengthy gap since I last invested into a retro-style game, or I’ve just been spoiled, it didn’t even occur to me to hit save when I stopped playing. Seven-year-old me would not have made such a mistake this badly.
The Aftermath: A Burned-Out Trainer
I have not returned to FireRed after my data loss incident. When I saw the title screen again and discovered my team consisted solely of Squirtle on my roster, a wave of exhaustion hit me. Status condition: Burned.
I might give it another shot… or maybe I’ll stick with the ocean of contemporary releases dropping every day that operate under the assumption I am incapable of manual saving. Still, my fondness for older titles isn’t dead. On occasions when I can convince my kid to pause the modern, auto-saving Pokémon game, we have been cooperatively playing some retro multiplayer mayhem. Those games from a bygone era skipped saving altogether in favor of cryptic character strings. Thus, when I meet an explosive end, all is not lost. That provides some small solace.