Similar to how my nearly unreadable schoolboy script has devolved over 25 years of typing on computers, my instincts to stop and save a game faded away. I blame the advent of automatic saving, save points, console quick-resume features, and games with such high stakes that I instinctively save every two seconds in case things blow up. Yet, I am fallible. I become complacent. And this week, I learned a crucial piece of wisdom after significant time invested in the fresh Switch version of Pokémon FireRed for Nintendo Switch: one must always smash that save button.
Many years had gone by since I engaged with a classic Pokémon title — never experiencing the GBA era, the Generation II titles may have been the final core Pokémon game I invested in. Consequently, I was thrilled to pony up $19.99 for the sentimental journey to the land of the original 151, and a quest gathering those first 151 pocket monsters. I quickly returned to my youth. Over a few successive evenings, I was catching bugs, added Pikachu to my team, knocked out Brock with ease, invested in the future Gyarados from a shady character, and journeyed through Mt. Moon carefree and confident.
The problem: I failed to save even once! The idea simply didn't occur to me.
That Jigglypuff shall never be friends with my Mankey.
Everything went wrong during a session when I wasn't even playing… and when my child took the console for a brief session of the newer Pokémon title instead, shutting down my session in the process. As is common knowledge (as I should have known…) starting another application on the console will close any software running. Your data is only preserved if the game autosaved or if you remembered to save prior to changing games. My mistake.
The Evolution of Game Saves: From Deliberate to Seamless
We should regard autosave, now so invisible most players barely notice it, as a true “cutting-edge” breakthrough. Although the classic text game Zork had one of the earliest save functions in a game, the original NES Legend of Zelda is frequently recognized as a milestone moment for not feeling completely screwed after a game over because of persistent memory saves on the classic console. Naturally, the onus was still on you to save. (And after one flub), you’d never forget. Through the 1990s, save cards for systems including the original PlayStation normalized the save process though they were still vulnerable; neglecting to save (or losing a card) meant losing significant playtime. Games like Resident Evil went so far as to make saving into an item to be managed.
Contemporary background saving, the one that subdued my manual save habit my retro gaming session so completely, took hold at the dawn of a new century. The first Halo pioneered seamless respawn points while Call of Duty refined the system to ease frustration and eliminate repetition. As the play grew longer — and more open-world — programmers mastered the technique on constant background saves and, eventually, the pinnacle of suspend/resume.
Pokémon's Own Journey: From Deliberate Action to Automatic Assurance
Funny enough, this iconic franchise offers a clear snapshot of how saving has changed. For years, the act of saving your Pokémon journey was a deliberate choice: fans were taught to select the Save option before closing their handheld console. The shift began with Pokémon Sword and Shield on Switch, Game Freak implemented an autosave feature (which players could turn off), marking a major attitude adjustment for one of gaming’s slowest-changing series.
I must confess my error: A long tenure with Breath of the Wild and modern Mario games utterly weakened my saving discipline. I am still wary with certain games — I won’t even gamble quitting during a run in a challenging indie title despite being aware it saves progress automatically — but be it because the lengthy gap since I last invested into a retro-style game, or modern conveniences have softened me, it didn’t even occur to me to hit save before redocking. Seven-year-old me would have been more diligent so catastrophically.
The Result: A Burned-Out Trainer
I have not opened FireRed following the great progress wipe. When I loaded it back up to see I had only the beginning Squirtle, a wave of exhaustion hit me. My personal status: 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. When I can pry my daughter away from the modern, auto-saving Pokémon game, we have been cooperatively playing a collection of classic Bomberman games. Those early SNES games omitted saving entirely relying purely on old-school passwords. Therefore, if I make a fatal mistake, all is not lost. That provides some small solace.