Difference between revisions of "Mod Merging"

   

   

This utility is easy to install, and fairly easy to use once you figure out how the interface works.  This process is not fully automated.  After loading up two or more mods in the window and expanding all the branches, you still have to select branches or individual edits to copy to the other mod.  You have to be careful about creating duplicate FormIDs within the merged mod.  You can edit the FormIDs so that they are no longer duplicates.  There is a spell that you can use to locate duplicate FormIDs before saving.  You can save your mod with a new name, or save it on top of one of the mods you are merging to preserve its name and protect dialog that may be attached to it.

This utility is easy to install, and fairly easy to use once you figure out how the interface works.  This process is not fully automated.  After loading up two or more mods in the window and expanding all the branches, you still have to select branches or individual edits to copy to the other mod.  You have to be careful about creating duplicate FormIDs within the merged mod.  You can edit the FormIDs so that they are no longer duplicates.  There is a spell that you can use to locate duplicate FormIDs before saving.  You can save your mod with a new name, or save it on top of one of the mods you are merging to preserve its name and protect dialog that may be attached to it.

Merging mods this way can still be slow and problem-prone, but it is faster than using the CK.  TESVSnip was used for some pretty heavy-duty modding in the days before the CK was released.  It can do many of the things that TES4Edit could do for Oblivion.

Merging mods this way can still be slow and problem-prone, but it is faster than using the CK.  TESVSnip was used for some pretty heavy-duty modding in the days before the CK was released.  It can do many of the things that TES4Edit could do for Oblivion.