Difference between revisions of "Mod Merging"

From the CreationKit Wiki
Jump to navigation Jump to search
imported>DreamKing
(Added note on using the CK's Version Control for merging .esps into an .esm & note on forthcoming TESVGecko.)
imported>DreamKing
Line 26: Line 26:
== Use the Creation Kit's Version Control ==
== Use the Creation Kit's Version Control ==


For merging multiple .esp files into an .esm, the Creation Kit's [[Version control]] system may be of use. See also the tutorial on [http://www.sureai.de/development/tutorials/skyrim-creation-kit-version-control/?lang=en setting up Version Control at the SureAI website].
For merging an .esp file into a pre-existing .esm file, the Creation Kit's [[Version control]] system may be of use (with Wrye Bash perhaps assisting in turning an .esp into an .esm). See also the tutorial on [http://www.sureai.de/development/tutorials/skyrim-creation-kit-version-control/?lang=en setting up Version Control at the SureAI website].
 


== Round-Robin Work/Taking Turns ==
== Round-Robin Work/Taking Turns ==

Revision as of 09:42, 15 June 2012


There is currently no tool available for easily merging Skyrim mods, as the TES4Gecko tool provides for Oblivion. As of this writing a TESVGecko tool is in development; its official discussion forum is at the Dark Creations website.

Current options:

Manually Merge in the CK

Open up two or more mods in the CK at the same time, with the file you want to merge the data to being the active file. Select an item you want to copy and give it a new name. When asked if you want to create a new object, say yes. Be sure to copy every little detail that you want to merge. Let's say you want to merge your NPC into another mod. You may not be able to just copy the actor object into the other mod and get away with it. Your actor might arrive naked, confused, broken, and helpless. If your actor has custom armor, custom AI packages, custom dialog in a custom quest, carries a custom sword, and belongs to a custom faction, you better copy all of those objects into your mod too.

This merging approach is rather time-consuming.


Use the Creation Kit's Version Control

For merging an .esp file into a pre-existing .esm file, the Creation Kit's Version control system may be of use (with Wrye Bash perhaps assisting in turning an .esp into an .esm). See also the tutorial on setting up Version Control at the SureAI website.

Round-Robin Work/Taking Turns

If you are working on a modding project with multiple modders and your mod is very complex and does not merge easily using the existing methods, you may consider taking turns working on the file. One modder at a time would work on it while the others would refrain from working on it since anything they built would be very hard to merge in. Alternately, you may figure out what types of work you are doing that are easy to merge. One modder at a time would work on the main file with all of its difficult-to-merge content, and the other modders would build pieces of the mod that you had proven were easy to merge to the main file.



The section on TESVSnip has been removed - the utility is NOT safe to use on your mod at ANY time for anything other than read-only lookups of data. DO NOT USE IT to save data you intend to keep in a live project.

See this topic and this one at Bethesda forums.