"Don't work directly on the save file"

[cloudropis]

This is recommended a lot when working with tools that change the save folder, "work directly on a backup copy of the saves".

How do you do that exactly, since Steam automatically loads the one contained in the Steam folder? And even if you point Steam to a new backup folder... Wouldn't it make THAT folder the new one that shouldn't be touched?

[jakeypearce]

Make a folder outside of your save directory and call it "backup". Then copy and paste the save from your Steam folder to the backup folder you just created.

[cloudropis]

Make a folder outside of your save directory and call it "backup". Then copy and paste the save from your Steam folder to the backup folder you just created.

that's just making a backup though, not what people mean when saying "don't work on the save file directly".

[jakeypearce]

Don't use the save the game uses in 385730\remote.

[cloudropis]

Don't use the save the game uses in 385730\remote.

so I have to change the active savefile to the one in the backup folder?

I don't get it. If I switch to that savefile and do all my modding there, what has changed compared to just doing everything in the default save location?

[jakeypearce]

I'll tag tekken into this post, so he can chime in.

[The Brand]

I have been able to back up saves and use the Steam cloud save corrupt trick well but the issue I've bumped into is that,  injecting into the backup causes whoever I am injecting to over write whoever I added last.  Does this have something to do with bak etc files being around?  I use X Packer and its up to date far as I can tell, I've had it about a  month.  I injected into my main save and it allowed me to add wrestlers via X Packer as normal, but for some reason my back up no longer works in this fashion.  Doesn't completely kill my experience, but it has forced me to use my direct save to install the last two wrestlers and obviously this makes me very nervous, lol