A decent autosave structure

[Bishop149]

Very simple request

Can the persistent save PLEASE NOT update the very split second you load a quicksave. A delay of even a minute or two would suffice.

I just lost 3 days of progress and my entire 10 ship Duna expedition because I accidently pressed ONE wrong sodding button, loaded a 3 day old quicksave and ooops there the last 50 or so persistent files wiped out instantly.

The fact that such mistakes are even possible in a finished game is insane, no warning, no nothing, everything GONE.

Combined with the consistent lack of support for 64bit (for god knows how many updates now) the lack of a solid autosave system to prevent this kind of thing is easily the biggest single problem with KSP and is really the kind of thing that should have been implemented on day 1 of development.

Heres an idea, rather than simply overwriting the persistent why don't you make autosaves write a new file and upon loading KSP delete any of said files over 10 days old.

Or on quitting KSP make a back up of the persistent

I'm sure that either of those would take all of 12.5 seconds to implement.

[Norpo]

I think that when you quickload, a "beforeloading" file would be a good idea. So instead of the flow being

1. get quicksave

2. overwrite persistent file

it should be:

1. copy current persistent file to "lastloaded"

2. do original steps

That way, if you mess up, you can just get rid of the main persistent file, and just rename lastloaded. (and less space taken up, because it's only backing up and keeping one file with this method)

Alternative method, an "are you sure" when the quickload was made longer than 1 hour of real time ago, or just plain combine the two methods.

I agree, it's too easy to erase 3 days of work in one keystroke. (or forgetting to do one keystroke, wherein you thought you made a quicksave 10 minutes ago, but you didn't)

[Higgs]

Agreed 100%