Merging Mods with TES4Gecko

MERGING MODS WITH TES4GECKO By David Brasher Version 1. 0 5/28/11 This pictorial tutorial shows you how to merge Oblivion mods using TES4Gecko. People want to merge mods for a variety of reasons. Here are some of them: (1) Their load orders are too full and they can\'t install any more mods. (2) They still have space for more mods, but want to keep things simple or have a certain organizational system. (3) They are building or editing a mod and need content from two or more mods in one place so they can reconcile it and include it in the final mod in the desired form. ----------------------- IMAGE BELONGS HERE. READ THE WORD PROCESSOR VERSION OF THE DOCUMENT TO VIEW IT. ----------------------- WHAT MODS CAN YOU MERGE? It is best to only merge compatible mods. Mods that do not conflict with each other. Things get more complicated when you merge mods that conflict, because you have to be sure that the mods you want to win the conflicts do win them. You may have to go into the CS and do a bunch of manual editing after you merge the conflicting mods in TES4Gecko. This tutorial only deals with simple mod merges that can be done completely in TES4Gecko and is aimed more at a gamer audience than a modder audience. Author Permissions: You may not share or upload any mods that contain content you do not have modding rights to. You can share and upload mods that contain: (1) Content you created yourself. (2) Content from files that are modders resources. (3) Content made by other authors if you asked for and received permission to use their work. In most cases, you are required to list their name, the name of their mod, and its download location in your credits. If your mod is for personal use and never leaves your computer, you can merge anything you want. This is what you will be doing if you have more than 255 mods and are trying to get them to run all at once on your computer. It is best to only merge clean mods. You should clean them in TES4Edit, and in some cases TES CS too before merging them. One common approach people use when they have too many mods or are trying to simplify their mod list is to merge mods into categories. Some common categories are: (1) Armor Mods (2) Clothing Mods (3) Weapon Mods This has the advantage of merging mods that generally don\'t conflict and makes organization easy. You have to be very careful if you want to merge things like dungeon mods and quest mods. You should avoid doing this unless you are good at using TES CS and really know what you are doing. If you merge mods with dialog, all the dialog will be lost when the name of the file changes. If it is voiced dialog it is a huge task to reconnect it all. If it is silent dialog, you can use the TES4Gecko function to \"Create Silent Voice Files.\" Unless you really know what you are doing, you should stick to just merging mods that are easy and automatic to merge like the armor mods. For