Merge script (updated)

Merge and reduce ESL and ESP files

A set of scripts for merging mods and/or further merging into Fallout 4's data files to improve performance and reduce the amount of BA2, ESP and ESL.

renew:

• Source merge script V9.0.1

Merge the mod into the source archive.

For upgrade instructions, see the Upgrade Guide article.

• Merge script V7.5.4

Script for merging mod archives.

Upgrade Guide: Merging the mods that generated materials and meshes for BA2 again.

Merge mod scripts

question

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

This idea:

This script is just another one of those automations that can help you package multiple BA2s from other mods into one mod, use load order to override mods with others, eliminate loader plugins, and thus give you some breathing room.

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

feature:

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.

Loader plugin selection - Optional - The loader plugin can be ESP, ESL, ESL-tagged ESP.

Loose Files - Optional - (Optional) Script can skip BA2s generation and pack loose files instead.

Keep optimized source mods - Optional - For higher compression, simplify the structure for faster merging and exclusion of loader plugins later.

Check merge template - Optional - You can enable this option to check it yourself before packaging or modify it according to your terms.

Support for multiple mod file structures - Works with many old, arbitrary, and currently accepted mod file structures.

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

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

source merge script

question

All major Bethesda games have extensive modding capabilities, and the way they implement this has changed little over the years. With it, the engine is also very slow at optimizing.

The game basically went through 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 just 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 to get something from the mod.

This idea:

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

As with many texture overhauls, they involve thousands of files, some even tens of thousands. All that workload capacity is effectively 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 archives, these plugins are removed and you get more mod slots for reuse.

In short, what do I get out of it?

Improved loading performance, game fidelity, more BA2 slots and more ESP slots.

You can also save even more BA2 slots when used with merged mod scripts.

Which mods are best for merging?

Massive replacement mods like texture overhauls or clothing/armor replacers. Essentially, whatever is on the screen has the potential to have the greatest impact.

These are also very subjective, as I myself have a huge impact even in the face of replacements as my settlements have 20-100 settlers each.

To ge …