- WHAT FOLDER DO I PUT THE UNOFFICIAL OBLIVION PATCH IN MOD
- WHAT FOLDER DO I PUT THE UNOFFICIAL OBLIVION PATCH IN MODS
If you see a mod is not in the usual area, check the merged mod out with TES4View to see if it can be safely loaded in the position of the latest loading mod that was merged into it. They are usually in the same place in a correct load order.
WHAT FOLDER DO I PUT THE UNOFFICIAL OBLIVION PATCH IN MODS
In order to avoid load order issues, merge groups of similar mods together. Wrye Bash and TESCS can be helpful as well, when extra tweaking is needed to smooth out the merging process. The utilities used for merging mods are TES4Gecko, TESSnip and TES4Edit. Otherwise, when TES4Gecko prompts you to change names to resolve conflicts for issues other than scripts or cells, saying yes is normally okay. You need to first go into TES4Edit and append an X or some other distinguishing suffix to the editor IDs of overlapping scripts in one of the plugins. Example issue: and that would be script conflicts with Adonnay's weapon mods.I typically try to keep merged plugins categorized to a specific load order group.TES4Gecko would rename all of the sound files to match the name of the merged plugin, which would not correspond to any files in the data folder. Use TES4Gecko if merging patches for mods with different voice files.For example, if you merge all of the unofficial official mod patches together, including USIP, you need to change the "Unofficial Shivering Isles Patch.esp" folder in the Sound\Voice folder (Data\Sound\Voice\) to "." Make sure to check out records with dependencies with TES4View after making these types of merges. When the merged plugin is originally created with the out of order information, some references may be messed up. Merging mods with multiple masters is sometimes a little more complicated that just sorting the masters after merging with TES4Gecko.This is also, yet another, reason not to merge the Unique Landscapes mods. This is another reason why it is usually not advisable to merge quest mods (i.e., the Lost Spires or Gates to Aesgaard.) Double-check the mods you are merging to see if other mods are "looking out for them" before creating the merged plugin. If formIDs were preserved in the merge, the patch's dependency can be changed from "mod XXX.esp" to the name of the merge containing "mod XXX.esp." However, formIDs are often not preserved that well and patching done by scripts (dynamic patching) does not allow for that name changing. Caution!!! Ī few things of which you should be aware. If it is being updated frequently, it is time to find a different group of mods to merge. Maintaining patches is like maintaining a load order, but, once created, a merged plugin should not be updated as frequently. Regardless of the reason, merging is a practice that requires care and attention. For others, fewer plugins is neater and better all around. Why merge? First of all, some people want to use more than 255 plugins or 400 plugins and BSAs.