Skyrim How To Remove Master

Contents

• 1 Overview
• 2 Programs and Tools
• 3 Details
  • iii.one Preparation
  • 3.2 Sorting Masters
  • 3.3 Examining records
  • 3.iv Make clean Master
• 4 References

Overview

The term xEdit is used as the generic name for the various game specific versions (aka TES5Edit, FNVEdit, etc.) which are simply renamed copies of the same tool so information technology will correctly determine the correct file structure to employ.

Sorting "main files" is necessary if the creator of a plugin didn't have them in the same "load gild" as you (or xEdit) practise. Fortunately this is easy to set up, simply if y'all don't information technology tin cause issues in your game. It will be covered as part of the more time consuming problem of removing a "master file" from a plugin in this article, just is completely separate and non related. (See the Sorting Masters department if that is all you lot are interested in learning.)

To the all-time of my noesis, xEdit is the simply reliable way to remove "primary files" from a plugin. But it is not an automatic process. Rather it is the finishing verification that yous have manually removed all such references from your plugin.

It is assumed y'all have at least some familiarity with the terminology and use of xEdit to create a "Compatibility" or "Feature" patch. If not, you lot are brash to learn the nuts of that functioning first. They are all described in the FNVEdit Training Manual, but that is not a tutorial style document. It is a "reference manual".

Annotation that a "compatibility patch" is different than a "merge patch" or a "merge plugin". (There are various terms used on the internet to reference each of these types of files, but they remain distinct entities.)

• "Compatibility/Characteristic Patches" make more than i mod work together past resolving specific record level conflicts or incorporating features from another in some called manner desired by the plugin writer. Run across the Making a Feature Patch (6:31 minute video) past Roy Batty. A more lengthy series of "steaming style" tutorials can be found at:

• FNVEdit BIS Compatibility Patch Tutorial 1
• FNVEdit BIS Compatibility Patch Tutorial 2-1
• FNVEdit BIS Compatibility Patch Tutorial two-ii
• FNVEdit BIS Patch Tutorial 2-3

• "Merge Patches" resolve record level conflicts betwixt plugins based upon the last to touch the record in the load lodge winning. This tin exist created either manually (forcing a winner by creating a new "last" plugin) using xEdit, or "algorithmically" using "Wrye Fustigate" or it'southward game specific forks (east.g. "Mash", "Wrye Wink", etc.) to create a "Bash Patch" (which also goes concluding in society to win). These "Bash Patch" algorithm winners can exist mitigated through the utilize of "tags". See the wiki commodity Bash Tags and the Wrye Bash Patch.
• "Merge Plugins" combine more i "not-conflicting" plugin into a single plugin (within certain limits) to reduce the number of overall "active" plugins. These must be "not-conflicting" because the process does Not resolve record level conflicts. Run across the Merged Plugin Guidelines for Personal Use wiki article. (This is not to say y'all tin can't ever merge "conflicting" plugins into a single plugin. Simply that information technology is an avant-garde technique not covered in the referenced article.)

You accept to load your plugin and all it'south "chief files" into xEdit, and and so find everywhere there are records in the plugin using records from the main file yous want to remove. These are not only constitute in those color tagged as "conflicting" (cherry background), though those are the place to starting time. They can also be in any record, even "new ones" (white background).

One time you think you accept removed all the references to records from the primary to be removed, you use the "Make clean Masters" role and check for the presence of the chief in the plugin's file header. IF all references are gone , and so it will accept been removed. If it remains, you still take some references to locate. (Save what you lot have done, reload, and work through it again.) You tin can cease up having to work through every single record in the plugin. But information technology will eventually work.

Programs and Tools

• TESEdit5 v3.1.three+ (generically known as xEdit. Rename downloaded EXE file to lucifer the game, due east.k. FNVEdit.exe for Fallout New Vegas.)
• FNVEdit Training Manual

Annotation: Exercise not employ xEdit with whatever "mod organizer" or other "plugin aware" tool open at the same time. While some might be uniform with sharing the plugin with xEdit, others grab the file with a "write lock" to forestall any other program from changing things. Play it safe and give xEdit exclusive access unless you are absolutely positive they are compatible. According to the TES5Edit Support Forum: "All plugins from the Information folder are sorted into 2 groups by extension (and extension only, ESM flag in plugin's header doesn't matter): *.ESM and *.ESP, then each group is sorted by plugin's file timestamp. Then xEdit loads all ESM, then all ESPs. The order of masters in plugins doesn't bear upon anything." This suggests that whenever possible, you should motion whatsoever "false ESM flagged" ESP files to the bottom of the list of ESM files in your load order if you want xEdit to match your game "load lodge" when information technology loads or sorts a plugin's master files.

Details

To illustrate, let's suppose we want to remove "Fallout New Vegas" (FNV) plugin "EVE FNV - ALL DLC.esp" as a "master file" from the "AWSO-WMX-EVE-ALLDLC-Merged Patch.esp" plugin.

"AWSO" is "All Weapon Sounds Overhaul", a comprehensive replacement of the existing weapon sound files. As such information technology is conflicting with weapon and animation records in other plugins (FalloutNV.esm, the v DLC files, YUP, WMX, WMX-DLCMerged, and EVE). In this instance, presume nosotros exercise not want to use the records from EVE in this "compatibility" file. Nosotros could build our own "compatibility" file, just have decided instead to just remove the EVE records in order to retain the author's choices for the other records. (Information technology should besides be a relatively quicker process involving fewer records.)

Preparation

Seriously consider either moving your game folder elsewhere and installing only the needed plugins, or creating a divide profile for the purposes of this projection (depending upon your "mod manager"). You don't want to accidently change anything your saved game files rely upon by blow.

• Admittedly keep a split up backup of the original "AWSO-WMX-EVE-ALLDLC-Merged Patch.esp" file, just in case y'all decide to start over.

Make certain you lot have installed and "actived" all the "master files" the plugin currently depends upon. For "AWSO-WMX-EVE-ALLDLC-Merged Patch.esp" these are:

• FalloutNV.esm
• DeadMoney.esm
• HonestHearts.esm
• OldWorldBlues.esm
• LonesomeRoad.esm
• GunRunnersArsenal.esm
• YUP - Base of operations Game + All DLC.esm Yukichigai Unofficial Patch - YUP
• WeaponModsExpanded.esp Weapon Mods Expanded - WMX
• WMX-DLCMerged.esp Weapon Mods Expanded - WMX Optional file "WMX-DLC".
• All Weapon Sounds Overhaul .esp All Weapon Sounds Overhaul
• EVE FNV - ALL DLC.esp EVE - Essential Visual Enhancements
• AWSO-WMX-EVE-ALLDLC-Merged Patch.esp All Weapon Sounds Overhaul Optional file "AWSO-WMXEVEYUP-ALLDLC-Merged".

Sort the "load order" as necessary for the proper performance of your game. And so place the "EVE FNV - ALL DLC.esp" plugin just above the "AWSO-WMX-EVE-ALLDLC-Merged Patch.esp" plugin (because nosotros merely added it to remove it as a master, and not considering it is going to be used during play). Placing it there volition brand it easier to notice the records in the latter that come from the former.

Note that this patch was created with the DLC in the incorrect gild for stable game play. We volition be correcting that equally role of this process, using the xEdit "Sort Masters" command.

• Open up xEdit and load the plugin we are going to edit: "AWSO-WMX-EVE-ALLDLC-Merged Patch.esp". (Note the xEdit exclusivity alert under Programs and Tools.) This should automatically load the other "principal files" it depends upon. The "Messages" tab of the correct-hand pane will display "Background Loader: finished" at the bottom when prepare to keep.

Sorting Masters

This only needs to be washed once, upon beginning loading the plugins.

• "<Right-click>" on the "AWSO-WMX-EVE-ALLDLC-Merged Patch.esp" file in the left hand pane and select "Sort Masters" from the popular-up "context menu". This will cause the "master file" sequence in the "File Header" tape to be sorted to that xEdit uses (which is based upon extension and appointment/time stamp simply) and automatically adjust record references.

• 

  SortMasters Fig01

• 

  SortMasters Fig02

• 

  SortMasters Fig03

• 

  SortMasters Fig04

(See SortMasters Figs. 01 thru 04. Click the link/thumbnail to encounter the enlarged epitome. Utilize your browser "<back folio>" control to return to this page.)

• Get out xEdit and ensure that the plugin "AWSO-WMX-EVE-ALLDLC-Merged Patch.esp" is checked to exist saved. (If for some reason you do not want the changes to exist saved, uncheck it's filename first.) Click on the "OK" button.
• Reload the "AWSO-WMX-EVE-ALLDLC-Merged Patch.esp" plugin and it'south masters into xEdit. The "master files" should now be in the correct sequence. Proceed to the next step.

Examining records

• "<Left-click>" on the "+" to the immediate left of the "AWSO-WMX-EVE-ALLDLC-Merged Patch.esp" file in the left mitt pane. This will aggrandize the list of record categories in that plugin. ("<Ctrl+Left-click>" will expand not only the record categories but also all the records themselves. we won't do that as we merely are concerned with a few specific categories.)
• As AWSO is a "sound replacement" modernistic, you might think we would start with the "sounds" record category (and yous could). Simply at that place is only one such record from "EVE" ("0003C943 WPNMissleLauncherFire2D") so instead to illustrate the process in this example we are going to skip to the "Weapons" category, and curlicue downwards to the tape "001251CC VFSWeapPlasmaRifleVanGraff (Van Graff Plasma Rifle)".

CleanMaster Fig. 01-Before

• In the right-hand pane of FNVEdit, the "View" tab should show you the image in "Fig. 01-Earlier". (You volition need to curl downward through the list of records a bit to find the "INAM - Impact DataSet" record.)

• In the figure, the "blood-red" boxes testify that the record in the "AWSO" plugin is that aforementioned equally the one in the "EVE" plugin. This is an example of what makes "AWSO" dependent upon "EVE", and volition forbid the "EVE" principal from being removed by the "Clean Master" command. We have to find every example of such dependencies and replace them.
• The "blue" boxes show the possible replacement records nosotros could employ to supervene upon the "EVE" record in the "AWSO" plugin. Every bit this is intended equally a merge of other plugins, we should choose a tape from one of those merging plugins. In this instance, it doesn't matter every bit they are all using the same tape. If more than ane other plugin's tape was suitable, that would be your choice.

CleanMaster Fig. 01-Afterwards

• To supercede the "EVE" record in "AWSO" simply "<Left-Click" and concur the mouse button on the replacement record nether another plugin, and drag it over to the "AWSO" record, and release the mouse button. The replaced record should look as shown in the upper tape of "Fig. 01-Afterwards".
• (See CleanMaster Figs. 01-Earlier and 01-After. Click the link/thumbnail to see the enlarged image. Use your browser "<back folio>" command to return to this page.)

• This is the basic procedure. There is one variation: removal of a record in the "merged plugin" (eastward.chiliad. "AWSO") from the "master plugin" in question (e.g. "EVE") for which there is no suitable replacement from a plugin existence merged. In the example this is the case with the "World Model" record, "MOD4 - Model Filename" sub-record.

• To delete the record from "AWSO", simply "<Right-Click>" on the tape, select "Edit" (or "Remove") from the context card that appears. ("Remove" does non always appear equally an option, but performs the same actions as follow for "Edit" from a single mouse click.)
• When "Edit is selected, it will display a window with the content of the record as text. Y'all tin can either hit the "<Delete>" key or remove the contents past backspacing. Once the displayed window is empty, click on the "OK" button to save the changes. Figure 01-After shows 1 tape in the lower area of the paradigm which has already been deleted, and the second is most to be "edited".
• (See CleanMaster Fig. 01-Later. Click the link/thumbnail to see the enlarged image. Use your browser "<back page>" control to render to this page.)

• Repeat the process for EVERY record in the plugin existence "cleaned" (e.g. "AWSO"), whether it appears to have a conflict or not. For example, "sound" tape "0003C943 WPNMissleLauncherFire2D" is a "yellow" groundwork with "dark-green" text, indicating it is an "override without conflict". At that place is no way to tell it is using a sound from "EVE" without looking at the tape straight. You can save the file later on editing just office of it if you lot need to intermission up the process into several sessions. When you practice load information technology back into xEdit, exist sure to attempt to "Clean Master".

• If it fails to remove the target master file (e.chiliad. "EVE" in our case), and then you lot all the same have records you need to edit.
• If it succeeds, then proceed to the Clean Master section.

Clean Master

• If you lot haven't already, salve your edited plugin (east.thousand. "AWSO-WMX-EVE-ALLDLC-Merged Patch.esp").
• Reload the "AWSO-WMX-EVE-ALLDLC-Merged Patch.esp" plugin and it'due south masters into xEdit.
• "<Right-click>" on the plugin file proper noun (eastward.g. "AWSO-WMX-EVE-ALLDLC-Merged Patch.esp") and select "Make clean Main" from the context menu that is displayed.
• When the "Letters" tab indicates the process is done, or the filename is displayed in "bold text", aggrandize the "+" next to the filename so you tin select the "File Header" tape.

If y'all have successfully edited out all the record dependencies upon the master to exist removed (due east.g. "EVE"), then the list of "master files" volition not longer contain that file (e.k. "EVE FNV - ALL DLC.esp"). Salvage the effect immediately and employ Windows Explorer rename the plugin to reflect your new version (east.g. "AWSO-YUP-WMX-ALLDLC-Merged Patch.esp").

If the main file is still present, then there are however references to exist removed. Resume from the get-go of the Examining records section.

• Package your new plugin and add it to your "downloaded mods" drove so you can instll it as normal.
• If you intend to publish your mod:

• Cheque the original mod permissions first,
• Then see the 'Packaging Mods for Installation' section of the wiki [1]Getting started creating mods using GECK] commodity.

References

• Making a Characteristic Patch (Video) by Roy Derailed (six:31 min) video.

A streaming series of compatibility patching tutorials can exist found at:

• FNVEdit BIS Compatibility Patch Tutorial 1
• FNVEdit BIS Compatibility Patch Tutorial two-1
• FNVEdit BIS Compatibility Patch Tutorial two-two
• FNVEdit BIS Patch Tutorial 2-3

• Bash Tags and the Wrye Bash Patch (Wiki)
• Merged Plugin Guidelines for Personal Use (Wiki)
• TESEdit5 v3.1.3+ (Freeware)
• FNVEdit Training Manual (PDF)
• Yukichigai Unofficial Patch - YUP
• Weapon Mods Expanded - WMX
• All Weapon Sounds Overhaul
• EVE - Essential Visual Enhancements
• All Weapon Sounds Overhaul Optional file "AWSO-WMXEVEYUP-ALLDLC-Merged".
• [1]Getting started creating mods using GECK]

Source: https://wiki.nexusmods.com/index.php/XEdit_-_Sort_&_Clean_%27master_files%27_from_a_plugin

Share this post