Larian Studios Forums Divinity - Original Sin Divinity - Original Sin - General How do I unpack the .lsv save files so I can edit?

Hi,

Love the game. My favorite part is going around and checking the vendors for purple or legendary gear and pick pocketing them. No really, I could do this for hours. I like the feeling it gives and it helps me min/max my characters gear. I like killing and questing second.

Now as you all probably know... you can only pick pocket someone ONCE (outside of having pickpocket gear and swapping it between your party - DUMB and off flavor imo).

My solution to allow my thief to pick pocket as much as he wants is to edit my saved game files and to erase the fact that my thief has pick pocketed people in the past. I assume the save files is my target, but it's all encrypted/obfuscated/packed. What unpacks it so I can dig through it?

Nvm, found it (second link): http://larian.com/forums/ubbthreads.php?ubb=showflat&Number=572322&page=4

But I could still use some help identifying where the pick pocketing data is stored in lsf files.

Figured it out:

Use that tool to unpack the single saved game file in Documents\Larian Games.... Then use the same tool but the other tab to convert the global.lsf file that was unpacked to global.lsx. Then use a text editor to open the global.lsx file. In there, ctrl + f for "pocket" and delete the lines. I left one line (read: one pick pocket block) for each big pick pocket section (which I assume was for each character that has pick pocketed before) just because I didn't know what completely deleting that data would do. Finally, convert the lsx back to lsf and repack the files.

As a bonus, ctrl + f for id="IsPlayer" value="True" to find each of your characters and modify them if you want.

Currently having trouble packing the lsf files back into a saved game file that doesn't crash the game when trying to load it. Every time I try to load, it says the saved file has been tampered with and then crashes. It even does this when I only changed one number in the entire global.lsf file. There must be a validation check somewhere but I see no mention of hashing inn any of the lsf files.