Plugin conflict checker (updated)
The plug-in conflict checker scans each plug-in in the load order for existing FormIDs and then checks each other for conflicting IDs.
About this mod Machine translation
The plugin conflict checker scans each plugin in the load order for existing FormIDs and then checks each other for conflicting IDs.
Update V1.5
Add zMerge support
Installation and use
Install the .Net 6 desktop runtime (address:
Unzip the latest build into a folder outside of Skyrim or Fallout 4's data folder. You should create two instances for Skyrim and one for Fallout 4.
Run the program once to generate "PluginConflictChecker_AppSettings.json" or download the basic PluginConflictChecker_AppSettings.json file;
Open "PluginConflictChecker_AppSettings.json" and change the path to "Data Folder" to Skyrim or Fallout 4's data folder;
Change "PluginTXTPath" to the path of the plugin.txt, which can be plguins.txt in "AppData\Local\Skyrim Special Edition\plugins.txt" or the plugin.txt in the MO2 configuration file;
Make sure all \ are doubled in JSON. Example: "AppData\\Local\\Skyrim Special Edition\\plugins.txt";
If the instance is for Fallout 4, change "Fallout 4": false to "Fallout 4": true
Run Plugin Conflict Checker.exe and let it generate the file for you to read
The file will be generated in the Reports folder **PluginConflictChecker_CreateZMergeInstance**
This will create additional instance configuration for PluginConflictChecker based on zMerge merge.json.
- It needs to be configured from installation and use.
- Edit PluginConflictChecker_CreateZMergeInstance.bat.
- Set the first parameter to the full path of zMerge’s merge.json.
- If you want it to automatically generate a merge conflict report, please set it to the second parameter -run.
- Run "PluginConflictChecker_CreateZMergeInstance.bat".
PluginConflictChecker_LocateMergeJson
This will find and run PluginConflictChecker_CreateZMergeInstance for all zMerges in the data folder
- Need to configure from installation and use
- Run "PluginConflictChecker_LocateMergeJson.exe"
- If you want it to automatically generate a report of merge conflicts, run "PluginConflictChecker_LocateMergeJson.bat" instead
Other uses
If you want everything to run quickly, you can run "_GenerateAllConflictsReports.bat". This will generate a report.txt for all merged reports and plugins
Other settings
"FilterOutMasterOverrides" True will ignore conflicts between a 2 plugins if one requires the other
"OutputToSeparateFiles" True will output the main list of plugins and separated files for each plugin that conflicts with something
"OutputName" Is a string to output extra name data for the conflict reports, not needed for regular reports of your load order. It is used mainly for zMerge support
"Explorer" True will open the output folder in Windows Explorer
"MinCountToOutput" Is a integer changing the number will require plugins to have more then the value to be output
"TypeFilter" Is a string list, add Mutegen Major Record interface types to this list to remove them from the conflict count, See Major Record Interfaces.txt for a list, Cell and Worldspace Records are already added
"OnlyIncludeTypeFilter" True will make "TypeFilter" only register conflicts of conflicts of of that particular type or types
Install & use Install: follow the bundled instructions
- Unzip the archive from playbuff and read the bundled readme / instructions first.
- There is no universal mod manager for this game: some mods replace game files directly, some go into a game-specific Mods folder, and some need a game-specific community loader or tool first — follow the bundled readme.
- Place the files exactly as the readme says; mods with listed dependencies need those installed too.
- Launch the game to confirm it loaded; some games require enabling mods in settings or an in-game mod menu.
Install locations vary a lot between games and mods — the bundled readme is the most reliable guide.