This wiki is a copy of the original Oblivion CS wiki created and maintained by the UESP.net. See CSwiki:Copy Notice for more info.

Difference between revisions of "TES4Edit Cleaning Guide"

Jump to navigation Jump to search
2 bytes removed ,  19:08, 6 August 2011
m
Grammar: "you're" -> "your"
imported>XJDHDR
(→‎List of Mods Needing Cleaning: Added a few mods from the BOSS thread.)
imported>Kivan
m (Grammar: "you're" -> "your")
Line 214: Line 214:
It is also highly advisable to '''only add one mod at a time''' to your game. This means download and install a mod and then play for a period of time before adding another mod. This can help determine if the mod you just added is problematic. But now we are delving into the realm of mod conflicts, which is way too large a subject to cover here, so only a few other points will be mentioned.
It is also highly advisable to '''only add one mod at a time''' to your game. This means download and install a mod and then play for a period of time before adding another mod. This can help determine if the mod you just added is problematic. But now we are delving into the realm of mod conflicts, which is way too large a subject to cover here, so only a few other points will be mentioned.


Adding mods slowly can be helpful, but it in '''no way''' is a perfect way to detect mod problems. Sometimes you'll add a mod and you're game will start crashing. You might want to blame the new mod. Maybe you are right. But also, it may be that another mod you are currently using contains either dirty (not if you already cleaned it, mind you) or wild edits, which by itself didn't cause problems (sort of like a dormant virus). However, adding the new mod, which may be totally clean, caused the prior mod to now wreak havoc on your game. The details of this type of scenario won’t be explained here but just know that this type of thing happens often, which makes it challenging to find the real culprit when your game goes wacky.
Adding mods slowly can be helpful, but it in '''no way''' is a perfect way to detect mod problems. Sometimes you'll add a mod and your game will start crashing. You might want to blame the new mod. Maybe you are right. But also, it may be that another mod you are currently using contains either dirty (not if you already cleaned it, mind you) or wild edits, which by itself didn't cause problems (sort of like a dormant virus). However, adding the new mod, which may be totally clean, caused the prior mod to now wreak havoc on your game. The details of this type of scenario won’t be explained here but just know that this type of thing happens often, which makes it challenging to find the real culprit when your game goes wacky.


But truthfully, most users won't ever know if a mod they are using has wild edits in it unless they put in a lot of effort reading about the mod and looking at it in TES4Edit. Therefore, the average user should take the above-mentioned precautionary measures and not worry about things as long as their game runs ''pretty well'' and is ''fairly stable'', by whatever definition you wish to use.
But truthfully, most users won't ever know if a mod they are using has wild edits in it unless they put in a lot of effort reading about the mod and looking at it in TES4Edit. Therefore, the average user should take the above-mentioned precautionary measures and not worry about things as long as their game runs ''pretty well'' and is ''fairly stable'', by whatever definition you wish to use.
Anonymous user

Navigation menu