injection blocker

F4SE plugin that allows you to prevent scriptable injection of LeveledLists. Configurable via .ini

Prefix:

F4SE：

Address Library for F4SE Plugins：

Microsoft Visual C++ Redistributable for Visual Studio 2019

information

Why:

I (GELUXRUM, the original author, the same below) absolutely despise script injections because of how much of a headache they can be if you want to control what gets spawned where; not to mention how their primary users (i.e. weapon mods) don't use the same LeveledLists, so you end up with some weapons polluting all LeveledLists, and another weapon that only exists in a single random LeveledList that you rarely encounter. Here's a good summary from Jonathan Ostrus:

Ugh script injection annoys me. The only way to remove them is to reset the entire debug list and core all script injections. This also makes conflict resolution a pain, since it's not easy to identify at a glance whether a mod injects a list. You must look at any script references for this mod. Then maybe decompile the script.

Instead of making small patches and fiddling with scripts/tasks to do the above, you can block them automatically using this plugin. Ability to choose to block specific ammo, armor, NPCs, weapons, or all items from being injected via .ini file.

If by any chance you wish to whitelist an NPC or item, you can also choose to do so by listing their FormID in a custom .ini file.

.ini file configuration

GLXRM_InjectionBlocker.ini：

This file is used by the plugin to control the types of injections blocked by default by setting these values ​​to 1/0 to enable/disable blocking for the corresponding categories:

bBlockAllItems=1

bBlockAmmo=1

bBlockArmor=1

bBlockNPCs=1

bBlockWeapons=1

Custom .ini file:

The plugin also enables you to create custom .ini files that will be read to build a list of whitelisted forms. This allows you to have specific forms bypass the block set above if you happen to wish to inject items or NPCs in the context of quest rewards, CC content, your own mods, etc.

All you have to do is create an .ini file with any name in the DataInjectionBlocker folder. The plugin will then read the files in that folder and output which files have been loaded into a .log along with the form it is trying to whitelist:

---> Loaded file: DataInjectionBlockerMyWhitelist.ini

---> Try whitelisting 1DB4C~Fallout4.esm

--->Success

---> Trying to whitelist 1F276~Fallout4.esm

--->Success

---> Trying to whitelist 1F669~Fallout4.esm

--->Success

To add a form to the whitelist, you must write the following entry in the new .ini you create:

1F669~Fallout4.esm=1

1F276~Fallout4.esm=0

1D95A~Fallout4.esm=0

1DB4C~Fallout4.esm=1

The form's FormID does not include the load order index. For example, Nuka World's Commie Whacker has FormID 06052926, so you would just write the last 6 numbers next to the file name it comes from (while also removing any leading zeros). You need to set this line equal to 1 or 0 as it allows you to control what is whitelisted without removing the entire line:

52926~DLCNukaWorld.esm=1