Probably ask "Are you serious?!" to no-one in particular, then emit a loud "NOOOOOOOOOOOOOOOOOO!!"
Afterwards I'd probably start a new game, save it quickly to make sure it still saves, then continue on a brand new journey :D
This and sob sessions. I've had it happen to be thrice with 2 copies of Sapphire and 1 save file session.
The 2 Sapphire "deletions" were due to losing the actual, physical cartridges. When I lost my first Sapphire, I retrieved a second copy. When I lost my second copy of Sapphire, I got Emerald later on.
In Emerald, I was saving to do a Secret Base battle, the kind that occur after you mix records with someone. The cartridge slightly shifted during saving, so the game froze. I turned the GBASP off and on, only to find the following message:
The save file has been erased due to corruption or damage. By the way, I didn't exploit any glitches or use any external devices on
Pokemon Emerald. I figured, "Previous save file should be loaded, right?" WRONG. My entire savefile got deleted, and I was greeted only with a
New-Game/Option screen, with the "Continue" box nowhere to be found. :cer_cry: Later on, I deliberately turned off while saving, and to my partial anger, the game did the traditional
"The save file is corrupted. The previous save file will be loaded." message. Only one time have I ever gotten the "file-erased" message as opposed to the "previous save file will be loaded" message.
In all three data deletions, I've had
several Level 100 Pokemon and
many hours of playtime. I almost lost the Emerald cartridge as well, but thankfully it ended up in a drawer rather than being Lost Forever. Somehow, I've kept on trucking, and now my Emerald cartridge probably holds the record for "most replayed game ever" in my game collection, with
Super Smash Brothers Brawl inching its way toward that status.
Hopefully, if this incident should ever happen again (and I
really hope it never does occur), the traditional "previous save file will be loaded" will take precedence. Having a whole legit file erased with no alternative files for loading is just
wrong :cer_no:, and it's one of the few legitimate reasons I see for using PokeSav (backup purposes).