In the same way my barely legible schoolboy script has deteriorated over 25 years of typing on computers, my natural urge to halt and record progress in a game waned. I blame the rise of automatic saving, save points, console quick-resume features, and experiences where the risk feels so great that I can’t help but save constantly just in case disaster strikes. However, I am human. Laziness creeps in. Recently, I was taught a crucial piece of wisdom deep into a session of the newly ported Pokémon FireRed for Nintendo Switch: one must always smash that save button.
It had been years since I engaged with one of the 2D Pokémon games — as I skipped the Game Boy Advance, 2000’s Pokémon Gold and Silver probably were the most recent traditional Pokémon journey I played. Therefore, I was excited to pay the asking price for a trip down memory lane to the land of the original 151, and an attempt collecting those original 151 creatures. I immediately snapped back to the glory days. During a handful of gaming sessions, I captured Bug-types, picked up an early Pikachu, beat Brock without trouble, took a chance on purchasing the Magikarp from the salesman in the Pokémon Center, and scaled Mt. Moon completely unconcerned.
The problem: Not once did I save! The idea simply didn't occur to me.
That Jigglypuff shall never find love with that Mankey.
The catastrophe occurred one evening when I wasn't even playing… and where my kid picked up the Switch for a brief session of Pokémon Z-A instead, shutting down my session to do so. As is common knowledge (something I temporarily forgot…) opening a new game on the console forces the closure of any software running. Your progress is only safe if the game autosaved or after a manual save ahead of launching something else. Oops.
The Progression of Save Systems: From Manual to Automatic
One could view automatic saving, now so invisible its operation is largely unconscious, as a genuine “next-generation” breakthrough. While PC text adventure Zork implemented a pioneering save functions in a game, 1986’s The Legend of Zelda is widely hailed as a pivotal point for not feeling utterly defeated by an in-game fail due to persistent memory saves in NES games. Naturally, the responsibility remained to save. (And after one flub), the lesson was learned for life. In that decade, save cards for systems like PlayStation normalized the save process but remained precarious; failing to save (or losing a card) meant losing significant playtime. Games like Resident Evil went so far as to make saving into a scarce commodity.
Contemporary background saving, the one that subdued my manual save habit my FireRed run so effectively, became standard around the turn of the millennium. The first Halo pioneered seamless respawn points while Call of Duty refined the system to smooth difficulty and remove unnecessary grinding. As the play grew longer — and increasingly non-linear — programmers mastered the technique for saving without interruption and, finally, the pinnacle of picking up exactly where you left off.
The Pokémon Series' Path: From Deliberate Action to Automatic Assurance
Curiously, this iconic franchise serves as a perfect mirror of that historical progression. For decades, the act of saving your Pokémon journey was a deliberate choice: fans were taught to manually record their data before closing their handheld console. A major change arrived in Pokémon Sword and Shield for the Nintendo Switch, the games added autosave (initially optional), marking a major philosophical change within one of the industry's most staunchest upholders of tradition.
I own up to my blunder: A long tenure with Breath of the Wild and modern Mario games completely dulled my manual save reflex. I still know better with certain games — I won’t even gamble bailing mid-run in a challenging indie title despite being aware it has a robust save system — however, perhaps due to too long since I sank time into a retro-style game, or modern conveniences have softened me, the thought never entered my mind to manually save before redocking. Seven-year-old me would never have fumbled so catastrophically.
The Consequences: A Burned-Out Trainer
I have not returned to FireRed after my data loss incident. Upon rebooting the game and discovered my team consisted solely of the beginning Squirtle, I felt completely drained. The verdict: Burned.
I might give it another shot… or perhaps I'll remain in the hundreds of new games available now which gently presume I can’t remember to save. Still, my fondness for older titles remains alive. When I can pry my child to take a break from her current favorite, we have been cooperatively playing some retro multiplayer mayhem. Those games from a bygone era had no save system at all in favor of lengthy password codes. Thus, when I meet an explosive end, it’s not a total loss. That, at least, is reassuring.