"ReflectedLight;c-17327084" wrote:
"DeKay;c-17327069" wrote:
Backing up saves just mean you copy the saves folder to somewhere else. So in case after the update, the original one gets corrupted, you have the copied folder to put back inside. Saving as in the game is not backing it up.
Yes, but consider: if the moment the game loads, before I do anything I do a "save as", creating a NEW save file, no longer using the old one, how is it possible for my old save to get corrupted if I no longer save "over" it, is the curiosity.
In effect I've made sure the last save that worked does not get overwritten.
So I find the "backup your saves" (plural) a bit curious as it seems simply making a brand new save file for each unique game you have going would have a similar effect.
I'm talking about the patch corrupting all the saves in the saves folder.
For example, you have Save A and you do a save as and call it Save B. But then the patch corrupts both Save A and Save B. You won't be able to use them anymore.
However, if you have both Save A and B, and then make a copy of that and put it outside so the patch doesn't corrupt it, let's call it Save A.2 and Save B.2, it is a backup. So if Save A and B are corrupted after the patch, you can delete those and just paste back A.2 and B.2 which is the same as A and B before it got corrupted. Makes sense?
By your definition of making a save as, I would not call it backing up. Yes, it is a copy of the first save game and if only the first save game is corrupted by any means "within the game", at least you have this other copy. Or vice versa, meaning if the new one you copied gets corrupted within the game, at least you have the original one that is untouched. But if both files get corrupted from outside, then you won't be able to use both.
Either way, when the devs tell us to back up our saves and mods before patching, they mean to copy the saves and mods folder to some place else, just in case.
