Separate progression and vessels into separate files

[dlrk]

Dealing with save-breaking updates would be a lot easier if progression was saved separately from vessels. I'd like to suggest that future versions of KSP separate vessels  and other more easily broken information into a separate save file from progression, contract completion, etc. This would allow a game to be resumed at the same point tech and progression wise

[Alshain]

How would it be easier?

[dlrk]

When a breaking update comes out, you could carry over your progress, instead of completely starting over

[mattinoz]

I do believe Squad have committed to non-breaking updates from now on and have built a system for file translators between versions.

So unless breaking the files is going to improve game speed or file stability I don't see the point.

[Alshain]

On 5/7/2016 at 3:36 AM, dlrk said:

When a breaking update comes out, you could carry over your progress, instead of completely starting over

How would you be able to carry over your progress any different than you can now?  If you load a game with incompatible craft, the craft is simply deleted, that is no different than if you don't copy over the craft file, in fact it is better because some craft might survive.

Edited May 9, 2016 by Alshain