Restoring Game Under Steam
Vreejack
Member Posts: 60
Steam has a nice feature in which it checks the integrity of game files and redownloads/reinstalls as necessary. What needs to be deleted in order to reset an install in preparation for a new set of mod installations?
What I know so far:
1. Empty the override folder .
2. Delete the weidu.log
3. Empty the script folder, or at least delete the new ones, sorted by date.
4. (finally) Validate the install files.
Anything else?
What I know so far:
1. Empty the override folder .
2. Delete the weidu.log
3. Empty the script folder, or at least delete the new ones, sorted by date.
4. (finally) Validate the install files.
Anything else?
Post edited by Vreejack on
0
Comments
There are two ways I know of to completely reset your game. The first, and likely easiest, is to simply reinstall the game; giving you a fresh install.
The second is a 2 step procedure as follows:
1. Uninstall all weidu mods by running the setup for each mod you installed and tell it to uninstall. Do not do step 2 until this is done.
2. Once step 1 is completed you can empty the override folder to remove any non weidu mods.
Once these steps are completed you should have an unmodded game with one slight exception: any strings added to dialog.tlk will remain to prevent issues with existing saved games. This should not affect gameplay if you start a new game with no mods installed. If you truly want a game without a trace of modding then you will need to do method one and make a fresh install of the game.
My concern is that there are other files and folders that behave like an override even though the game was not otherwise told about them. All expected files should get checked by Steam. Actually, I wish I had thought of that sort of installation check years ago when I experimented with big mod installs. Installing a bare BGT used to take like an hour.
In any event I was looking for a quick way to uninstall everything, as even if weidu worked for that purpose I think you can imagine how long it would take to uninstall a dozen mods.
Now I just need to write an install script so that I don't have to keep redoing the same installs by hand.
@Tresset that isn't necessary if you want to delete every single WeiDU mod, unless one of them edits an executable/chitin.key (by adding biffs)/baldur.ini/portraits/whatever. And the strings remaining on the dialog.tlk don't affect anything, and leaving them and installing the same mods will cause WeiDU to use the existing strings. If a mod doesn't uninstall via WeiDU it's because:
1) the mod is bugged
2) the mod requires to be marked as NO_LOG_RECORD but hasn't
3) the mod is tagged as NO_LOG_RECORD intentionally
4) you've deleted the mod's .tp2 file or backup folder
5) you've updated the mod and the .tp2 is very different from the old one
6) ???
Ooops sorry, should have been in the conspiracy thread
Okay, that's a facetious question. Most bugs will not prevent uninstallation, but those that do generally do not get reported, and so they accumulate. I estimate that between 10 and 20 percent of mods can royally screw with your install when you try to back them out. And those are just the ones that tell you something is screwed up. I prefer deleting the whole mess and starting over.
I see that some stuff gets left behind, though. Like old scripts. Steam will restore the original scripts but you can probably see the others in customization. That's not a big issue, but I am wondering how mod installs react when (if) they see these residual scripts lying around. I can clear the entire folder and let Steam repair it but now I am wondering what else I missed.