Bundled XML - Script Merging vs. Mod Merging vs. Game Management
I am a bit confused on how these tools "merge/combine" bundled XML files. A perfect example would be Ghost Mode mod. The author of the mod advises to also use Scabbards for NPC's mod and NitPicker's Patch mod, but advises against merging these 3 mods. I am not actually asking about this particular case - its just a good example. I want to understand how this merging works.
Let's assume those are the only 3 mods installed. All 3 mods have bundles, each with several conflicting XML files for whichever items. There are only a few conflicts between Scabbards for NPC's mod and NitPicker's Patch mod, BUT there is a ton of conflicts between Ghost Mode & Scabbards for NPC's mod, and many between Ghost Mode & NitPicker's Patch mod. What is the most appropriate way to merge them in case merging becomes necessary in the future due to a high number of installed mods with bundles and textures?
I can think of 3 possible methods to deal with these 3 mods:
1. Not merge any of them, simply prioritize by file name or through mods.settings file. In this case, top priority goes to Ghost Mode, second priority to Scabbards for NPC's, and third (lowest) priority is for NitPicker's Patch. What does the game do in this case when it detects conflicts within Bundled XML files? Does the game simply use all of any single prioritized file OR does it combine non-conflicting parts of all XML files from ALL 3 mods and prioritizing only the parts that have conflict?
2. Merge with Script Merger and during conflict detection choose "A (Ghost Mode) over B (Scabbards for NPC's) and/or over C (NitPicker's Patch) for unresolved conflicts". What does Script Merger do in this case? Does it prioritize single whole XML files if it detects conflicts between A&B or A&C or A&B&C or does it COMBINE them?
3. Merge with Mod Merger and simply prioritize based on position. What does Mod Merger do when it detects conflicts - MERGES non-conflicting parts of the same files or does it simply discard de-prioritized files and utilizes all of single XML file from prioritized mod?
I am sorry if it all sounds confusing - I am having a hard time figuring out how to specifically ask what it is I want to ask. English is not my first language...
I am a bit confused on how these tools "merge/combine" bundled XML files. A perfect example would be Ghost Mode mod. The author of the mod advises to also use Scabbards for NPC's mod and NitPicker's Patch mod, but advises against merging these 3 mods. I am not actually asking about this particular case - its just a good example. I want to understand how this merging works.
Let's assume those are the only 3 mods installed. All 3 mods have bundles, each with several conflicting XML files for whichever items. There are only a few conflicts between Scabbards for NPC's mod and NitPicker's Patch mod, BUT there is a ton of conflicts between Ghost Mode & Scabbards for NPC's mod, and many between Ghost Mode & NitPicker's Patch mod. What is the most appropriate way to merge them in case merging becomes necessary in the future due to a high number of installed mods with bundles and textures?
I can think of 3 possible methods to deal with these 3 mods:
1. Not merge any of them, simply prioritize by file name or through mods.settings file. In this case, top priority goes to Ghost Mode, second priority to Scabbards for NPC's, and third (lowest) priority is for NitPicker's Patch. What does the game do in this case when it detects conflicts within Bundled XML files? Does the game simply use all of any single prioritized file OR does it combine non-conflicting parts of all XML files from ALL 3 mods and prioritizing only the parts that have conflict?
2. Merge with Script Merger and during conflict detection choose "A (Ghost Mode) over B (Scabbards for NPC's) and/or over C (NitPicker's Patch) for unresolved conflicts". What does Script Merger do in this case? Does it prioritize single whole XML files if it detects conflicts between A&B or A&C or A&B&C or does it COMBINE them?
3. Merge with Mod Merger and simply prioritize based on position. What does Mod Merger do when it detects conflicts - MERGES non-conflicting parts of the same files or does it simply discard de-prioritized files and utilizes all of single XML file from prioritized mod?
I am sorry if it all sounds confusing - I am having a hard time figuring out how to specifically ask what it is I want to ask. English is not my first language...