Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

Axu

An open-world graphical roguelike. Still in development. · By Cynapse

Way to prevent the save data being lost due to any bug

A topic by Failnaught created May 19, 2018 Views: 252 Replies: 1
Viewing posts 1 to 2
(1 edit)

So I played again the game with the 0.63 version, and it really improved greatly since last time (0.53 or 0.55 IIRC), however, one thing that still bother me since the 0.53 version is the save file getting corrupted due to some bug while playing, making it impossible to retrieve your saved profile, and forcing you do start a new.  So I would like to suggest that there was some way to prevent such thing from happening while the game is still in development.

I thought of creating an autosave function with double(or more) slots. I know the autosave function was already suggested, but I don't know if it was implemented (on 0.53 it wasn't), still the idea that I'm proposing would need 2 or more autosave slots,  the 1st for the current place the player is, and the 2nd for the place he was previously. That way if the place the player triggers a bug and corrupt the data of the 1st slot, there will be a 2nd point to return.

The reason autosaves weren't implemented was due to a few factors: 

A) At the time, manual saves were the best way to do a non-permadeath run. Since then, the new difficulty options made going back to an old save relatively pointless, as you can continue playing right after death, moving forwards rather than back.

B) It's extremely hard to track down a specific reason why a save file won't load. The only way I can reasonably get rid of them all is if people report it to me. So it's not as simple as checking to see if the save file is cool or not. This is the same reason why I don't allow cross-version save files (for now).

C) Time cost that could be spent on more enjoyable tasks. Axu is still in Alpha, and being developed in my spare time. I put my effort towards facets that pique my interest at the time rather than what absolutely needs to be done at that time. If I were developing Axu full-time, my priorities would be much different.

The best short-term remedy I can offer is to have some kind of "Save without quitting" option as a last resort. For now, autosaves aren't something I can afford to put time into.