Merge script (updated)

A set of scripts for creating ba2, merging mods, merging mods into original ba2, and creating switchable texture templates.

Author's words:

Merge Mods Scripts

question

In this day and age, there are millions of mods available for Fallout 4, and whether it's in terms of the limits of ESP or BA2, or even ESL in extreme cases, it's common to hit the limits of what the game can handle. Therefore, there must be many tools available for merging these files to move further away from such limitations.

This script is just another version of this automation that helps you package multiple BA2s from other mods into one mod, using load order to overwrite the mod with other mods, eliminating loader plugins and thus giving you some breathing room.

The script also accepts loose files in a folder, so you can use it to create BA2 from scratch as well. It automatically sorts and places files in BA2 using the appropriate configuration.

Many options allow you to customize various aspects of this process, even allowing you to review the final merge template before archiving.

feature

Create BA2 - Folders based on load order can be merged into BA2 together with loader plugins.

Merge Mods - Mods based on load order will be merged into a new mod containing the loader plugin of your choice. Reduce BA2 and/or any virtual loader plugin.

Loader Plugin Selection - Optional - The Loader plugin can be ESP with ESP, ESL, ESL tags.

Loose Files - Optional - (Optional) Skip BA2 generation and keep loose files.

Using 7z Archive Mod - Optional - Package the mod into a compressed 7z archive for use with your mod manager.

Customizable texture archive size limit - Texture archive size limits can be set based on the behavior of the game, and multiple archives can be generated if needed.

Keep Optimized Source Mods - Optional - for faster subsequent merges.

Check merged templates - Optional - Enable this option to check or modify merged templates before packaging.

High Performance - Leverage the high IO capabilities of SSDs and multiple CPU cores to reduce time requirements from hours to minutes.

Repair Mode - If you have changed/upgraded your hardware, you can run the included installation script to repair the package structure and rebuild the configuration.

source merge script

question

The game basically browses all of its own files (~500k) and mods. It constructs a set of tables to solve the problem based on loading order. This happens every time you start the game, load a save, or simply go to a new area. The bigger your mod is, the slower it will be and the more lag you will experience. Also contrary to common sense, once this table is built, the engine is still much slower at getting stuff out of the mod.

The idea: This pack basically circumvents this problem by merging your mods into the game's own archive, i.e. your mod status becomes the new vanilla. It's like playing the game with your mods, but with the smoothness of the original.

As with many texture overhauls, they involve thousands of files, some even tens of thousands. All that workload capacity is actually freed up for more content you want to add to your game. Likewise, many mods have plugins that simply tell the game to load the relevant resource files, these plugins will be removed and you'll get more mod slots for reuse.

Which mods are best for merging?

Large-scale replacement mods, such as texture overhauls or clothing/armor replacements. Essentially, anything that's on screen in excess has the potential to have the greatest impact.

These are also very subjective, and like myself, even face replacers have a big impact since my settlement has hundreds of settlers.

feature

Templates - Make templates with your favorite texture combinations and switch between them almost instantly. *

Handling Extra Assets - Extra assets not found in the source are packaged into a merged mod.

High Performance - Leverage the high IO capabilities of SSDs and multiple CPU cores to reduce time requirements fro …