Difference between revisions of "Template:Multi-file Merge Up Procedure-10"

From Nexus Mods Wiki
Jump to: navigation, search
(Multi-file Merge Up Procedure: update)
(Multi-file Merge Up Procedure)
Line 22: Line 22:
 
<onlyinclude>
 
<onlyinclude>
 
Step 10. Save the Result.
 
Step 10. Save the Result.
* Save the resulting ModA as the original ModA's filename (or the "new file" name selected in Step 6 as the target of the "Copy as Override").  This is now our 'patched parent plugin'.
+
* Save the resulting ModA as the original ModA's filename (or the "new file" name selected in Step 6 as the target of the "Copy as Override").  This is now our 'patched parent plugin'. [[File:MfMUP_Fig1-10.jpg|thumbnail|100px|MfMUP Fig. 1-10]]
 
* Save any other modified plugins as well.  These will usually be those un-merged plugins that had one or more of the ModB plugins as masters that should now be gone and replaced with ModA.  Some may have have some records updated with new FormIDs from the ModA plugin as well.
 
* Save any other modified plugins as well.  These will usually be those un-merged plugins that had one or more of the ModB plugins as masters that should now be gone and replaced with ModA.  Some may have have some records updated with new FormIDs from the ModA plugin as well.
* Take a screenshot of this window or otherwise note which files have changed.  You will need to know these file names in the next step.
+
: (See Fig. 1-10.  {{Thumbnail_enlargement_message}})
 +
* Take a screenshot of this window or otherwise note which files have changed.  You will need to know these file names in the next (Cleanup) step.
 
</onlyinclude>
 
</onlyinclude>
  

Revision as of 02:54, 17 February 2017

Template:Multi-file_Merge_Up_Procedure-10


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

Detail

Multi-file Merge Up Procedure

Step 10. Save the Result.

  • Save the resulting ModA as the original ModA's filename (or the "new file" name selected in Step 6 as the target of the "Copy as Override"). This is now our 'patched parent plugin'.
    MfMUP Fig. 1-10
  • Save any other modified plugins as well. These will usually be those un-merged plugins that had one or more of the ModB plugins as masters that should now be gone and replaced with ModA. Some may have have some records updated with new FormIDs from the ModA plugin as well.
(See Fig. 1-10. Click the link/thumbnail to see the enlarged image. Use your browser "<back page>" control to return to this page.)
  • Take a screenshot of this window or otherwise note which files have changed. You will need to know these file names in the next (Cleanup) step.


References

Nexus wiki articles referred to by this article:

Nexus wiki articles that refer to this article: