Similar to how my barely legible schoolboy script has degraded across a quarter-century of digital document creation, my instincts to pause and save a game diminished. I attribute this to the emergence of automatic saving, checkpoints, Xbox Quick Resume, and titles where the tension is so high that I can’t help but save constantly in case things blow up. However, I am human. I become complacent. Recently, I was taught an important lesson deep into a session of the recently released Pokémon FireRed on Nintendo's console: one must always manually hit save.
It had been years since I last played one of the 2D Pokémon games — as I skipped the GBA era, the Johto region games may have been the last mainline Poké-title I completed. Therefore, I was excited to pay the asking price for a trip down memory lane back to Kanto, and an attempt collecting those original 151 creatures. I was instantly transported to my youth. Over a few successive evenings, I captured Bug-types, picked up an early Pikachu, beat Brock with ease, invested in the Magikarp from the Man at the Pokémon Center, and journeyed through Mt. Moon without a worry in the world.
The fatal flaw: I never saved my game! The idea simply didn't occur to me.
Alas, Jigglypuff can never form a bond with my Mankey.
Everything went wrong during a session where I didn’t play FireRed… and as my daughter grabbed the Switch for a swift 30 minutes of Pokémon Z-A instead, shutting down my session to do so. As we all know (something I temporarily forgot…) starting another application on the console forces the closure of any software running. Your progress is only safe following an automatic save or after a manual save before switching. Whoops.
The Evolution of Saving Progress: From Intentional to Invisible
It's fair to consider automatic saving, now so invisible its operation is largely unconscious, as a bona fide “next-generation” innovation. While PC text adventure Zork featured among the first save systems in gaming, 1986’s The Legend of Zelda is frequently recognized as a landmark achievement because players no longer felt utterly defeated by an in-game fail because of battery-backed saving in NES games. Naturally, the responsibility remained to save. (And after one flub), you’d never forget. During the nineties, memory cards on consoles including the original PlayStation made saving more common but remained precarious; failing to save (or misplacing a memory card) could erase countless hours. Titles such as Resident Evil took it further by transforming saving into an item to be managed.
Modern autosave, the one that subdued my manual save habit my Pokémon adventure so effectively, gained prominence in the early 2000s. Halo: Combat Evolved had its automatic checkpoints whereas later franchises like Call of Duty perfected the mechanic to smooth difficulty and reduce tedious replay. As the play grew longer — and increasingly non-linear — devs cracked the code of persistent, invisible saving and, finally, the holy grail of instant on/off.
A Franchise's Adaptation: From Conscious Choice to Unconscious Backup
Funny enough, this iconic franchise is a great reflection of that historical progression. For years, the act of saving your Pokémon journey required a manual command: gamers were conditioned to select the Save option before closing their handheld console. The shift began with Pokémon Sword and Shield on Switch, the series introduced an autosave feature (which players could turn off), representing a substantial design shift for a franchise known as most tradition-bound franchises.
I own up to my blunder: Years of playing Breath of the Wild and recent platformers utterly weakened my instinct to save. I am still wary under specific circumstances — I refuse to chance exiting prematurely in something like Hades 2 even knowing it has a robust save system — but be it because too long since I sank time into a retro-style game, or I'm simply pampered, the thought never entered my mind to preserve my progress when I stopped playing. Seven-year-old me would not have made such a mistake so catastrophically.
The Consequences: A Burned-Out Trainer
I have not returned to FireRed after my data loss incident. When I loaded it back up to see I had only my starter Squirtle, I felt completely drained. Status condition: Burned.
I might give it another shot… or I could just continue playing the ocean of contemporary releases available now that kindly assume I am incapable of manual saving. Still, my affection for classic games remains alive. On occasions when I can convince my kid to pause auto-saving Pokémon Legends: Z-A, we have been cooperatively playing some retro multiplayer mayhem. Those classic titles skipped saving altogether in favor of old-school passwords. Therefore, if I meet an explosive end, the setback is minimal. That, at least, is reassuring.