Skyrim

File information

Last updated

Original upload

Created by

generalmx

Uploaded by

generalmx

Virus scan

Safe to use

About this mod

Utility for combining files from different mods.

Permissions and credits
Mod Combiner is an advanced batch script which reads configuration files to pick-and-choose textures and other files from other mods, automating adding any number of conflicting mods together.

I was really impressed with both the work of Celestral on Texture Pack Combiner and as well of S.T.E.P. and its community. While I do not have a discerning eye, I am good at scripting, and thus the Mod Combiner was born. This was the first step in my quest to automate S.T.E.P.

This utility relies on user input, and does nothing without configuration files. Using the Mod Combiner, one can now write a very simple configuration file to give us their take on what mods look best with what. Do you like the skin texture from "Dragon Texture Mod #1" but think "Dragon Texture Mod #2" did another part better? Now you can make your own configuration file to combine the two mods and release it on a site like NexusMods.

Usage: Files go in a directory (folder) called "Files", and are copied to a directory called "Combined". Configuration files go in the same directory as the main "ModCombiner.bat" utility, which first looks for a file called "order_modcombiner.txt" to figure out in what order to read the configuration files (if not found, it creates its own order file). All configuration files must end with ".cfg". Once the batch file is finished, look for log_modcombiner.txt.

Example configuration:

HD2K\Textures\actors\dragon priest\dragonpriest.dds,Data\Textures\actors\dragon priest\
HD2K\Textures\actors\dragon priest\dragonpriest_n.dds,Data\Textures\actors\dragon priest\

Here we're copying individual texture files from the HD2K mod to the Combined directory. The syntax is "File to be copied, where to copy", using comma delimitation. If "HD2K\Textures\actors\dragon priest\" only contains the files we need, we could also do this:

HD2K\Textures\actors\dragon priest\*,Data\Textures\actors\dragon priest\

* is a wildcard and will match all files in the directory. We could also do this:

HD2K\Textures\actors\dragon priest\dragonpriest*,Data\Textures\actors\dragon priest\

To get all files starting with "dragonpriest", or this

HD2K\Textures\actors\dragon priest\dragonpriest*.dds,Data\Textures\actors\dragon priest\

To get all files starting with "dragonpriest" that also have the "dds" (texture file) extension.

Now let's say you wanted to include support for extracting mod archive files (.7z, .zip, etc.) that's easy:

<hd2k></hd2k>

Will extract HD2K.zip to the Files directory/folder, and then the batch file will continue on. Remember - the configuration file is read in order, top to bottom (end of file). All you, the configuration file writer, need to tell the utility, is where these files will extract to in the Files directory. So let's say you give the utility the command:

<hd2k></hd2k>

And you see a new folder in the Files folder called "Serious HD 2K Textures", and you want to copy those dragonpriest textures. You'd end up with something like this:

<hd2k></hd2k>Serious HD 2K Textures\Textures\actors\dragon priest\dragonpriest.dds,Data\Textures\actors\dragon priest\
Serious HD 2K Textures\Textures\actors\dragon priest\dragonpriest_n.dds,Data\Textures\actors\dragon priest\

One final note - you can add comments to your configuration files by starting off the line with a semi-colon (;). You can put version info, instructions, whatever. The batch file itself is pretty well-commented, and can even be well re-configured by users.

Some Suggestions:
- Write multiple configuration files for different machine specs. Say Mod #1 may be better for higher-end machines while Mod #2 is better for lower-end machines, and Mod #3 is good for either. You can write two configuration files: Baseline.cfg and Heavy.cfg, with the Baseline being the same as "Light" including files Mod #2 and Mod #3 and the optional downlaod "Heavy.cfg" including files from Mod #1 which overwrite the files from Mod #2. You'd could include a master orderfile (order_modcombiner.txt) to make sure Baseline.cfg gets read before Heavy.cfg.

order_modcombiner.txt:

Baseline.cfg
Heavy.cfg

As simple as that.

Future Plans
- BSA extraction
- ddsopt command-line support
- Direct download support

Let's all help make Skyrim beautiful.