Difference between revisions of "Mod Cleaning Tutorial"
Jump to navigation
Jump to search
→Using an External Utility: added TES4Edit
imported>ShadowDancer m (→TES4Gecko: formatting 690px is exact width) |
imported>Dev akm (→Using an External Utility: added TES4Edit) |
||
Line 45: | Line 45: | ||
== Using an External Utility == | == Using an External Utility == | ||
There are several utilities that can make it a lot easier to remove things from a plugin. | There are several utilities that can make it a lot easier to remove things from a plugin. | ||
=== TES4Edit === | |||
TES4Edit makes it very easy to examine the details of a mod's record structure, compare it with other mods in your load order, and tweak any of them to clean out problem records. | |||
By far the best way to do this is to perform a thorough examination of your mod looking for unintentional or problematic changes. The huge advantage here is that you can tell exactly what changes were made to each record, which lets you make an informed decision about whether the record should be removed or not. In other words, you can verify your work by examining the plugin record structure in TES4Edit and removing any records that are not intentional changes. | |||
To remove a single record or range of records in TES4Edit, select them and right-click->Remove. | |||
You can also use TES4Edit's "Remove identical to master records" function, which automates the process for any records that are unchanged from the master. This doesn't catch records which have minor accidental changes, but it can still help. When you do this, make a copy of your mod, use TES4Edit's "Remove identical to master records" on it, then load your original "dirty" mod and use TES4Edit's "Compare to" function to compare it with the cleaned copy. | |||
Wiki link:[[TES4Edit]] | |||
=== TESsnip === | === TESsnip === |