Template:Multi-file Merge Up Procedure-9

Template:Multi-file_Merge_Up_Procedure-9

Multi-file_Merge_Up_Procedure-9 is a template.

Include for this template: {{Multi-file_Merge_Up_Procedure-9}}
Only the portion of the "Details" section in "onlyinclude" tags is included when called.

Overview

This procedure is separated into several templates so it may be included in several instances in the article "Multiple-file Merge Up Procedure", with intervening commentary at the various steps.

Programs and Tools

TESEdit5 v3.1.3+ (rename downloaded EXE to FNVEdit.exe)
FNVEdit Training Manual
Gribbleshnibit8's Merge Up Guide (MUG)

Detail

Multi-file Merge Up Procedure

Step 9. Check All Plugins for Errors.

Note that some plugins will not be in Bold Italics (indicating they were changed) prior to this step. The xEdit "check for errors" process will flag them as changed, so you may want to take a screenshot of this window first or otherwise note which files have changed by this point. You will need to know these file names in Step 11, the "Verify and Cleanup" step for copying to their own project folders.

Check for errors by right-clicking on each plugin, and selecting "check for errors" from the context menu that then appears.
Check in the 'File Header' for unexpected 'master files'.
The other loaded but unmerged plugins may have some of the ModB files we merged into ModA as 'masters'. As those records have now been injected into ModA, we have to make sure each unmerged plugin has ModA as a 'master' instead or it is added as needed, and then that we "clean masters" so the merged ModB plugins get removed. If they do not, it means we missed updating some record FormID, likely at step 6 - "copy as overrides" and have to start over.
If there are any remaining dependencies (evidenced by a master you expected to be dropped still being present in the plugin's "File Header" record) you can use the script "List records referencing specific plugin.pas" on that plugin to list them in the log window so you can fix them.
Once corrected, "sort" masters on that plugin.
"Clean masters" again on the ModA plugin, and re-check all plugins for errors.

If you are unable to remove an unexpected master dependency by "clean masters", then you will need to start over from scratch, by restoring all files modified by this procedure from your backups and beginning from Step 1 of this Stage again. Rethink the master files that you add to the plugin(s) having the problem.