In the same way my barely legible teenage penmanship has deteriorated through decades of typing on computers, my natural urge to stop and save a game diminished. The culprit is the advent of automatic saving, checkpoints, Xbox Quick Resume, and experiences where the risk feels so great that I instinctively save constantly just in case disaster strikes. But I’m not perfect. Laziness creeps in. And this week, I discovered an important lesson deep into a session of the newly ported Pokémon FireRed on Nintendo's console: you must still smash that save button.
Many years had gone by since I picked up a classic Pokémon title — having missed the boat on the Game Boy Advance, the Johto region games were likely the last mainline Poké-title I played. Consequently, I was thrilled to pony up twenty dollars for a trip down memory lane to the Kanto region, and a run to catch those classic 151 pocket monsters. I quickly returned to my youth. Across several nights, I captured Bug-types, found a Pikachu in Viridian Forest, knocked out Brock on my first turn, took a chance on purchasing the useless fish from the salesman in the Pokémon Center, and scaled Mt. Moon without a worry in the world.
The critical error: Not once did I save! And never thought to.
Alas, Jigglypuff can never be friends with my Mankey.
Everything went wrong during a session when I wasn't even playing… and when my child grabbed the Switch for a quick half-hour of Pokémon Z-A instead, quitting my application to do so. As any Switch user understands (a fact I foolishly ignored…) starting another application on Switch will close the active game. Your progress is only safe if the game autosaved or if you remembered to save ahead of launching something else. Whoops.
The Development of Game Saves: From Manual to Automatic
One could view automatic saving, now so effortless many gamers take it for granted, 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 pivotal point for alleviating the sensation of being completely screwed by an in-game fail because of persistent memory saves on the classic console. Of course, the onus was still on you to save. (And following a single mistake), you’d never forget. Through the 1990s, save cards for systems such as the PS1 normalized the save process though they were still vulnerable; neglecting to save (or misplacing a memory card) meant losing significant playtime. The survival horror series Resident Evil took it further by transforming saving into a scarce commodity.
Today's automatic saving, that eroded my natural saving reflex my Pokémon adventure so completely, became standard at the dawn of a new century. Halo: Combat Evolved pioneered seamless respawn points whereas later franchises like Call of Duty refined the system to ease frustration and remove unnecessary grinding. As the play grew longer — and increasingly non-linear — programmers mastered the technique on constant background saves and, eventually, the ultimate convenience of suspend/resume.
Pokémon's Own Journey: From Conscious Choice to Unconscious Backup
Funny enough, the Pokémon series serves as a perfect mirror of how saving has changed. For a long time, saving in a Pokémon game was a deliberate choice: fans were taught to manually record their data before closing their Game Boy or DS. The shift began with Pokémon Sword and Shield on the hybrid console, the series introduced an autosave feature (initially optional), signaling a significant philosophical change within one of the industry's most slowest-changing series.
I own up to my blunder: Countless hours spent in Breath of the Wild and modern Mario games completely dulled my manual save reflex. I still know better under specific circumstances — I wouldn't dare risk bailing mid-run in a challenging indie title even knowing it has a robust save system — but whether it’s been my extended absence from older game design, or I'm simply pampered, I didn't even think to manually save before putting the console down. The child I once was would never have fumbled to this degree.
The Result: A Burned-Out Trainer
I have not picked up FireRed following the great progress wipe. When I loaded it back up to find just a lone my starter Squirtle, my motivation evaporated. Status condition: Burned.
Perhaps I'll restart… or maybe I’ll stick with the hundreds of new games released constantly that kindly assume I am incapable of manual saving. Nevertheless, my love for retro gaming isn’t dead. On occasions when I can convince my daughter away from her current favorite, we have been cooperatively playing Switch 2’s Super Bomberman Collection. Those classic titles skipped saving altogether relying purely on lengthy password codes. So, even if I meet an explosive end, the setback is minimal. That provides some small solace.