how do i tell what mods can be converted to esl sse

Principal Table Of Contents

xEdit Managing Mod Files

Contents...

•  8.1 Overview

•  8.ii Calculation Master Files to a Plugin

•  8.3 Calculation ESL flag to a Plugin

•  8.4 Adding ESM flag to a Plugin

•  8.5 Changing Mod FormIDs

•  viii.6 Merging a Plugin into another Plugin or Master

•  8.7 Converting a Plugin into a Main

•  8.8 Splitting a Plugin into a Plugin/Chief Pair

•  8.9 Comparison Two Versions of a Mod

•  viii.x The ESL Flag

•  8.10.1 Important dangers when compacting FormIDs

•  8.x.1.1 Kickoff Important danger when compacting FormIDs

•  8.10.i.2 Second important danger when compacting FormIDs

•  8.10.1.3 Third Of import danger when compacting FormIDs

•  viii.10.ii When it is safe or not safe to add the ESL Flag

•  eight.x.3 Calculation the ESL flag

•  8.ten.four Adding the ESL flag for mod users

•  8.xi How ESL enabled games handle FormIDs for ESL flagged files

•  8.11.1 How ESL enabled games address records within plugins

•  eight.eleven.2 The ESL address format

•  8.xi.iii The Downside

•  8.xi.3.1 Example 1

•  8.11.3.ii Example 2

•  8.11.iv Example iii

•  8.xi.4.1 ESLifying plugins

•  viii.11.4.two ESLifying Plugins the piece of cake way

•  8.eleven.five Compacting plugins

•  eight.12 Credits

This chapter is dedicated to modernistic authors, and describes a number of functions and actions that xEdit provides to make mod authors lives easier and their products more standardized. Like the chapter on Modern Cleaning and Error Checking, these functions hole mod authors produce products that volition be less conflicting with other mods, and will open doors to possibilities that modern authors may not have known existed. Actions similar merging mods, splitting them apart into Plugin/Chief pairs, adding Principal file references and more than are documented in the sections below.

To reference a record from ExampleMaster.ESM in Plugin.esp you need to add ExampleMaster.ESM to the Principal list in the File Header of Plugin.esp. This allows the plugin to add together/change items plant in the ExampleMaster.ESM. xEdit does this by calculation a new master to the MAST sub tape in the file header and correctly renumbering the FormIDs in the module. This can exist very handy for mod authors, as it simplifies the process downward to a few mouse clicks, so the mod author can focus on more important things like modding!

In this example nosotros showcase Saiden Tempest'south Weapon Furnishings mod and the taylorsd'due south Better Frag Grenade Physics mods, 2 fantabulous enhancements to Fallout3. Here we volition add the SS Weapon Effects.esm Principal file to the Better Frag Grenade Physics plugin, then that we can add together i of Saiden Storm'due south cool plasma blasts to a frag grenade for kicks! To starting time the activeness, select "Add Masters" from the context menu as shown:

This volition nowadays the File selection menu, from which you lot can Cheque the Chief file(s) that yous desire to add together every bit references in the Plugin's header equally shown:

In one case xEdit adds the master file as a reference in the Plugin, you see results similar to the screenshot below showing the Letters Tab log-entry:

Note that "SS Weapon Effects.esm" has at present be added to RealFragGrenade3.esp, making information technology possible to adhere one of Saiden Tempest's Weapon Effects explosions to the grenade issue in Better Frag Grenade Physics. The View Tab shows the specific entry:

Annotation: If you plan to release a mod to the public, then you lot should ONLY do this with permission from the modauthor, in this case Saiden Storm. If you wanted to employ his weapon effects in a mod of your own and release it, yous demand permission!

Below Elminster describes why this office is important for mod authors wanting to add main file references to their own mods:

Elminster

"With FormIDs information technology's important to realize that the FormIDs that xEdit shows you are Non the ones that are really written into the module file. The FormIDs that xEdit shows you are "load order corrected" ones, while the FormIDs in the file itself are "file specific" ones.

FormIDs are made up of ii parts, the first byte (2 characters) is the "module index", the concluding 3 bytes (half dozen characters) are the "module specific ID".

Mapping from "file specific" to "load social club corrected" FormIDs and dorsum only affects the "module index" and leaves the "module specific ID" untouched.

An instance, suppose you got a bunch of modules loaded:

•  [00] Fallout3.esm

•  [04] MasterA.esm

•  [x] MasterB.esm

•  [15] MasterC.esm

•  [20] Plugin.esp

And lets suppose the MAST sub record in the File Header of Plugin.esp lists:

•  Fallout3.esm

•  MasterB.esm

•  MasterA.esm

If you now see a tape in Plugin.esp that overrides a record from Fallout3.esm, then you would meet a FormID like 00123456 for information technology. In this particular case that tape would as well accept the aforementioned (00123456) FormID inside the Plugin.esp module file.

But if you have a record that overrides a record from MasterA.esm, eastward.g. with a FormID like 04ABCDEF (you can see the 04 equally "module alphabetize" matches the load society of MasterA.esm) then it would be saved equally 02ABCDEF in the Plugin.esp module file, because 02 is the index of MasterA.esm in the list of MASTer files in the File Header of Plugin.esp.

And an override for a record in MasterB.esm (e.m. 10654321) would exist saved equally 01654321 in the Plugin.esp module file because 01 is the index of MasterB.esm in the list of MASTer files in the File Header.

Last just not least, a NEW record in Plugin.esp which belongs to Plugin.esp and which xEdit would show you lot e.g. as 20FEDCBA gets stored as 03FEDCBA in the file (because 03 is equal to the number of entries in the Main list, as indices into that list start at 00, 03 is 1 higher then the highest valid index into that list).

You will besides discover that it'south not possible to have an override record for a record from Master3.esm in Plugin.esp or in any other form reference such a record, considering there is no way to map a load order corrected FormID of 15A1B2C3 to a file specific one that'southward valid in Plugin.esp.

To reference a record from Master3.esm in Plugin.esp you demand to add Master3.esm to the MASTer listing in the File Header of Plugin.esp. But if you just go there and do that manually, then you've just added Master3.esm with the index 03 to the file. Which means that all the records that used to vest to Plugin.esp are of a sudden considered override records for records from Master3.esm and will show upwards with 15xxxxxx FormIDs instead of 20xxxxxx FormIDs! A real mess.

If you instead use the Add together Masters function, so xEdit will not only add together then new entry into the Principal list, it will also renumber all (file specific) 03xxxxxx FormIDs into 04xxxxxx FormIDs first to preserve their meaning (which is "this tape belongs to this file").

There are rare cases where editing the MAST list directly is what you actually desire. e.thousand. when splitting an .esp into an .esm/.esp pair. In that case you would make a copy of the .esp, rename it to .esm, load it lonely into xEdit to set the ESM flag in it's header, then restart xEdit to load both the .esm and the .esp and modify the MAST sub tape in the File Header of the .esp by calculation the .esm as final entry. After restarting xEdit and loading both files you will come across that all records in the .esp are now considered overrides for the same records from the .esm"

Load the module yous would like to add together the ESL flag to and click the plus by the filename to expand the contents. Click File Header, right click in the View Treeview and choose Edit to exist presented with a list of Flags.

Cheque the box next to the ESL flag and click Ok.

Click okay to save the plugin.

Check the box next to the ESM flag and click Ok.

Click okay to salvage the plugin.

In that location are times in which you may demand to renumber the FormIDs for all records in a plugin to avert conflicts. This tin become necessary if 2 plugins share the same FormIDs (or some of them), which tin can result in bad conflicts in-game. Renumbering FormIDs from will alter all FormIDs of records belonging to the Modern-file (but not any override records which might be independent in that mod file) so that they start at the specified value.

This Function is useful if you have multiple modules that you plan to update in the future, but also want to ever provide a merged version (e.g. using FO3Plugin). By assigning non overlapping FormIDs to the dissimilar modules, you can make certain that no FormID reassignment of conflicting FormIDs has to take place when merging.

To renumber the FormIDs of a Mod file, Right-click on that mod file in the Navigation Tree to present the main context card (A). Then select, "Renumber FormIDs from…" from the carte du jour as shown in the screenshot below:

When selected, the function will present a, "Starting time from…" window request you what number you want to offset the renumbering at as shown below.

Normally a FormID is 8 characters long, with the first two representing the mod file's alphabetize and the final six the reference's specific index inside that specific mod. Thus pick a number between 100000 and FFFFFF in hex:

Once the new module specific start FormID (in hex) has been input (A) and the OK button selected (B), xEdit will brainstorm changing the FormIDs and present the output in the Letters Tab every bit shown in the screenshot below:

When changing the FormIDs of a huge modernistic like Reykjavik past Alexander Sigurðsson, the process took 3-4 minutes on a high-end computer. The results shown in the Messges Tab reveal simply a few examples of xEdit renumbering a FormID, discovering all references to it in all modernistic files, and correcting the numbering to foreclose conflicts.

Note: Changing the FormIDs of an existing module will brand it SaveGame incompatible and volition suspension whatever other module that uses this module as master! If you accept whatsoever dependant modules, you need to have them all loaded into xEdit at the time y'all change to FormIDs so that they will all be updated appropriately.

One of the common tasks that many mod authors face is the demand to merge modernistic files together into a unmarried plugin or primary file. Many mod players too like to merge all of their favorite plugins into a single primary file (one modder affectionately calls information technology, "BORG.esm"). xEdit tin can exist used to accomplish both of these needs, and will ensure that the resulting plugin is synchronized correctly confronting it'southward combined references, and that the load orders are correct. The procedure is illustrated below, starting with loading FOMM and ordering the files correctly as shown below:

In this instance we will exist merging Skykappa's Destructible Building Materials 3000 ( WIPz) (here-later referred to equally DBM 3000) into the 500 Rads Bar (WIPz), so that the Bar can use the destructible building materials. Note that Skykappa's DBM 3000 is a modders resource, and was released past the author to exist used in other mods for the low cost of mentioning in the mod's credits.

Load society is important when merging mods together, mainly because xEdit is very precise about the numbering and society of FormIDs and references amidst mods. Its is Very piece of cake to conflict the FromIDs of mods being merged together (as is discussed at depth below). Every bit such xEdit requires u.s.a. to identify the mod that is receiving the content (A) Below the mod being alloyed (B) in the load order of FOMM. This is of import, only if you go it wrong don't worry, xEdit volition warn you nigh it (too shown below).

You can also merge many mods into 1 at once, you don't have to exercise it 1-by-one if you lot happen to have several mods that needs to be combined together (equally in when a modder lumps everything into one giant BORG.esm). The only requirement is that the assimilator (BORG.esm) is at the bottom, below the assimilates. In one case you accept the load order correct, leave FOMM to save the load order.

Now launch xEdit, which should offer the list of mods in the correct gild with the assimilator at the lesser as shown below:

Notation the load order is exactly as nosotros specified in FOMM. If everything is checked, you can always Right-click in the Master/Plugin Selection window and click, "Select None" to clear all the checks. And then select the assimilator and assimilatees (A). Click okay to load the mods into xEdit (B), which yields the following output:

Note how the just files loaded are the main Fallout3 master files and the modernistic files nosotros are merging together (B and C). Nosotros are now in a position to merge the DBM 3000 into the 500 Rads Bar!

To execute the merger, first open the assimilatee's (mod existence copied) by Left-clicking on its plus sign (A), and then selecting all of the record headings within the mod (B) using the mouse and the shift-key. Next Right-click at (B) to render the context menu, and select, "Deep copy as override into…" (C) Equally shown beneath:

This action performs our traditional, "Copy" of the material we want to merge, and volition nowadays you with a carte option where you can select the file you want to merge these records into (our traditional, "Paste"):

When presented with the, "Which files do…" menu, select the mod that you desire to Paste the content into (A), and select OK to perform the merge (B). You may be prompted to add the copying mod as a principal, select, "Yes" to this (C).

You will now be presented with the output, which can be seen in the Messages Tab:

Notation how the 500 Rads Bar now has Bold text over its proper name, indicating that new records take been copied into to and that it is marked as modified (A). The Letters Tab displays the output of any master connections we made during the process (B), and any errors that may have occurred (none in this example).

If you now open the two mods, you lot will run across how the references from DBM 3000 are duplicated into 500 Rads Bar. Each tape can be seen in the View Tab downwards to the variable and reference level, as shown beneath:

Each record tin exist compared in the View Tab as desired; showing that each has been copied into the 500 Rads Bar and will now salvage as office of that plugin. Whatever errors that occur will show up in the Letters Tab, and may likely prevent a merger from taking place. If you lot encounter errors in the Messages Tab, you should assume that the mods did non merge and you lot'll demand to address the errors noted.

With the merger complete, it'south time to save our newly-combined mod file! This is washed nigh conveniently by hit, "Alt-South" or closing xEdit. Either will present you with the Save Changed Files window as shown below:

Simply ensure the mod you just merged together is Checked for saving (A), and click "OK" to relieve the mod. Also notation that the only file xEdit wants us to save is 500 Rads Bar, while DBM 3000 is not shown. This is correct beliefs, indicating that nosotros copied stuff into 500 Rads Bar and effectively did cipher to DBM 3000.

If you get the load club wrong in FOMM when trying to merge 2 modern files, xEdit will present yous with the following fault:

Note that the error is very specific about the load order issue, in an attempt to better guide you into the right load guild for whichever mods you are trying to merge. If you run into this error, exit xEdit, right the mod load order in FOMM, re-launch xEdit and perform the merger operation again.

If you don't run across any errors through the procedure or after saving, get out xEdit and either test the combined mod file or load it upward in the GECK and so yous can offset adding destructible edifice materials to your mod! Take a nice day, thank you for playing.

Converting a Plugin (ESP) into a Master (ESM) file is a unproblematic process that tin can be doing using xEdit in less than five minutes. The file extension of a Plugin as well equally the ESM flag within its file header must be changed in gild to make the transition to a Master file. The screenshot below starts the activeness by launching xEdit:

First yous need to de-select all of the mods using Right-click in the Master/Plugin Choice window (A). And so click/check just the modernistic your converting (B), in this example we're converting Antistar'south Weapon Mod Kits plugin into a principal file. Click "OK" (C) to load xEdit with just the mod being changed as shown:

Note that Weapon Modernistic Kits is successfully loaded into xEdit (B), and that it is the only file listed bated from the Fallout3 master files (A). You lot are now prepare to convert the Plugin into a Master file.

To make the conversion, all we take to do is modify i flag in the File Header, which tin be accessed by Left-clicking open the Weapon Modern Kits record in the Navigation Tree. Immediately beneath proper noun of the mod is the File Header row (A) as shown beneath. Yous will so see the File Header data printed into the View Tab (B):

The File Header tape is divided into dissimilar sub-headings and variables, including the Record Flags, Version, Author, mod Description and any Principal file references that the plugin requires. We volition exist changing the Record Flags variable by Correct-clicking into the open infinite next to information technology (C), which will return a small context card. You tin can then click, "Edit" (D) to modify the values. Doing and then will present a alarm window as shown below:

This window is a default/standard in xEdit, and exists to make certain that anytime you are about to change a mod file for the get-go fourth dimension, you lot know nearly it. It may seem annoying to some, simply often the worst conflicts betwixt mods come from changes that a mod author did non intend to brand. Merely select, "Yes" (A) to move along.

You will next be nowadays with a menu of bachelor/known flags that yous can select:

Note that many of the flags are blank or unknown, because literally the customs does not know what those flag values hateful. Fortunately the flag we need is the first ane on the listing (A), simply Left-click it and so click, "OK" to save the flag settings.

With that you are done! Note the File Header text is now Assuming (A) indicating a change, and the Record Flags in the View Tab (C) show that the ESM flag is fix (B).

Once done with xEdit, you volition want to modify the file extension from Weapon Mod Kits.esp to Weapon Mod Kits.esm and then that the extension matches the File Header flagging. The GECK and Fallout3 don't actually care nearly the file extension (ESP/ESM), what matters is that File Header flag. The Extension is for humans to go along them sorted correctly! Now all yous need to do is leave xEdit or press, "Alt-South" and Salve your new Main file as shown below:

It is also possible to change a Plugin to a Master using merely FOMM or other tools, but at that place is always the potential of problems with ONAM records. ONAM records are special records created that allow Master files to communicate with one-some other when references need to exist passed. xEdit ensures that as part of the conversion process, these ONAM records are built and correctly ordered. This is why it is improve to make the Plugin to Main conversion using xEdit.

Splitting a single Plugin (ESP) into a Master (ESM)/Plugin (ESP) pair can be useful in many situations, especially when a modernistic author wants to share resources from one Plugin with other Plugins. The just way to share resources between Plugins is to catechumen those resources into a Master file. The split is a two-role operation in which yous first split the single Plugin into a indistinguishable Plugin and Primary at the file (windows explorer) level. You then change the Flagging on one of the two duplicates to turn information technology into a Master, and alter the flagging on the Plugin copy to make reference its new master file. The action begins in windows explorer as shown below:

With the mod copied, the next screenshot shows the paste:

This will create a duplicate of the WeaponModKits.esp Plugin. This may seem a very basic part of the process to duplicate, but was done for thoroughness and for those who can't read English and depend on the diagrams for the process.

At present we need to re-proper name the copy to brand information technology our Chief file version.

You will be presented with a alarm about changing the file extension, which is a mutual windows warning. Simply select, "Yep" when prompted. The screenshot below shows the last part of the duplication procedure:

You will then be presented with the output; both a Plugin and Master file that are identical at this point. The screenshot below shows the Master (A) and Plugin (B):

With the file duplication office done, information technology'southward time to launch the Fallout Mod Manager ( FOMM) to prepare our loading order for the new Master file equally shown below:

Once FOMM is loaded, observe the WeaponModKits.ESP (B) and WeaponModKits.ESM (A) versions of the mod in the list and ensure that both of them are Checked/Selected to load. The screenshot shows how FOMM will look when beginning loaded after the divide, showing the ESP (B) is all the same checked (every bit it was before), while the new Master we just created is not yet checked (A) every bit shown below:

Here you must also ensure that the Master (ESM) version loads Before the Plugin (ESP) version every bit this is a Fallout3 requirement. The recommendation is to movement the Master (ESM) higher-up in the load order before all other Plugins, and load the Plugin (ESP) version of Weapon Mod Kits somewhere below the Masters. With that done, close FOMM and load xEdit. Your new load order with the Weapon Mod Kits.esm loading before the Weapon Mod Kits.esp should be visible in xEdits as shown below:

To load just the Principal and Plugin, first Correct-click in open space (A) and select, "None" from the context carte as shown above, and so check-off just the Weapon Mod Kits.esp and Weapon Mod Kits.esm files (C), and click, "OK" to load them into xEdit. This volition load just the 2 Weapon Modern Kits files and the Fallout3 masters into xEdit as shown below:

Note that both our Chief and Plugin version of Weapon Mod Kits is loaded and ready for conversion (A). The loader confirms a successful boot-upward in the Letters Tab (B), indicating we are good to go for the conversions. Adjacent we demand to set the Record Flags to ESM (or Primary) equally shown below:

With the File Header block of Weapon Modern Kits.esp selected (A), Right –click in the open space adjacent to the, "Record Flags" section (C) which will render a small context Menu. Select, "Edit" (D) from this small-scale carte du jour to add the ESM Primary flag, which effectively converts the Plugin into a Master. Before you lot tin proceed however, you will go a warning bulletin from xEdit nearly irresolute the mod'south contents. This is normal and provided for your protection. Only select, "Yes" (A) to continue.

The screenshot below shows you the Flags menu that is rendered:

This, "Edit Value" menu shows you all of the known (and unknown) flags available for setting in a Fallout3 mod file for Record Flags. Many of the flags are known and tin be selected, while a few still remain unknown. The simply flag we care about is the, "ESM" flag (A), which y'all should check-off then click, "OK" (B) to accept the new flag values.

Once done you will be presented with the outcome every bit shown below, which now has the Weapon Mod Kits.esp entry and its File Header in Bold text (A) in the View Tab, indicating the change. In the Right-mitt View Tab (C), the Tape Flag row is now also in Bold text with the new, "ESM" flag now populated with it (B) as shown below:

Next we need to add the new Main version of Weapon Mod Kits (ESM) into the Plugin version (ESP) as a master file reference, so that the Plugin references the Master. This will allow the Plugin (ESP) to use the Master (ESM) records going forrad. The screenshot below shows you the showtime step in the process of adding a Main reference:

Note that we're changing the File Header section only as we did when adding the ESM master flag, merely this fourth dimension we Right-click in the Master Files row (B), so selecting, "Add" from the context menu.

This will create a new, blank Primary File reference in the Weapon Modern Kits Plugin that y'all tin can now assign to our new Chief file as shown below (D), which we can so modify as needed. For our example we need to assign the new master file entry to Weapon Mod Kits.esp. To make the modify simply Right-click in open up space to the right of the, "MAST – Filename" entry (B), which volition return a small-scale context carte du jour. Then select, "Edit" (C) equally shown below:

Clicking Edit volition open a, "Edit Value" window, allowing you to blazon-in the name of the Master file you want to assign as the reference (A). Click, "OK" when washed (B) to save the reference, which will take yous back to the View Tab.

You should employ the same example that the chief file does, in this case, "WeaponModKits.esm" to ensure that there are no conflicts. And with that we're done! Annotation that the WeaponModKits.esm is listed next to the, "MAST – Filename" entry (B), and that the File Header also has Bold text (A) indicating the change as shown below:

And for the final step, you need to save the changes. Apply, "Alt-South" or shut xEdit to present the Save Files window equally shown below:

With this, you now have a Chief/Plugin version of Weapon Mod Kits, and the procedure works exactly the aforementioned for whatsoever mod that you want to split. You lot can modify the esp file extension to ESM, and so open and save information technology with the GECK and it volition tick the ESM flag on, just won't produce ONAM'south like xEdit will which are needed for whatsoever overrides to Fallout3.ESM's references. Unless your Plugin has no CELL and/or WRLD group, you lot're better off using xEdit.

Note: An .esp tin be the master of some other .esp.

Note: If yous accept a Plugin with multiple masters, you'll have to edit your GeckCustom.ini "bAllowMultipleMasterLoads=i"

Note: The GECK won't edit .esm's, so yous accept to ESP'ify, edit in GECK, and so ESM'ify.

1 of the common tasks that mod authors face is to compare two versions of their own mods, either during construction or in subsequent updates. There are too times when modernistic authors encounter difficult to solve problems with a new version of a mod, and need to revert back to a previous backup. The xEdit compare function tin can provide a valuable and convenient style of copying information from one version of a modernistic to another, without having to sort through records that don't belong to their mods. Whatsoever the case may exist, this department is devoted to teaching you how to compare two versions of a mod file, and how to copy records over if the demand arises.

For this section nosotros feature Quarn's Unofficial Fallout3 Patch, which has helped to resolve countless bugs in Fallout3 and has improved the gaming experience for thousands of modders. To starting time the action, launch xEdit and select 1 of the 2 modernistic files that you wish to compare as shown below:

As shown above, by Right-clicking in open up-space in the Master/Plugin choice window (A), y'all will render the selection bill of fare (B) where you lot tin, "Select None". This will un-check everything on the list. Then select just Ane of the two mods (C) and Click "OK" to load it (D). The screenshot below shows the result:

Here nosotros accept simply One of the ii modern files loaded along with the Fallout3 master files it depends on. We will need to hide these main files from view so that we are Simply looking at the modernistic file that we want to compare.

To hide the master file references from view, we need to select each one of them in-plough with a Correct-mouse click (A), which will present the main context card. There you can select, "Hidden" (B), which is the last option on the list every bit shown beneath:

You won't see any outward-change in the in the xEdit view afterwards, simply you tin confirm that they are marked every bit hidden by Right-clicking on them over again – you volition see a Bank check-mark side by side to, "Subconscious" menu option indicating that they are subconscious (from filters).

Next we need to load the other version of the Unofficial Fallout3 Patch mod file we're comparison (the new/current version). You can do this by Right-clicking on the loaded-version of the modern (A), which will nowadays the master context card. Select, "Compare to…" from the context menu (B) as shown below:

Selecting "Compare To" volition present the, "Open" window as shown below, where you can select the electric current version of Unofficial Fallout3 Patch (A), and then, "Open" (B) to load it into xEdit as shown below:

The "Compare To" version of the mod is loaded as read-only into xEdit, then you will not be able to make any changes to it, only you tin can re-create from information technology into the version of Unofficial Fallout3 Patch that we loaded into xEdit at boot time. Y'all can alter the order and load either/any version of the mod first, so that you can edit/copy records into whatsoever version you loaded.

Once the Compare To office loads the other version of the modern as read-only into xEdit, yous will come across a view similar to the i below. Notation the two versions that announced together in the Navigation Tree (A), and no errors noted in the Messages Tab (B):

With both versions of the mod now loaded with the Compare To function, the concluding step is to apply a Filter to find the inverse records betwixt them. Note that with the Fallout3 master files now listed as, "Hidden", they will not show up at all after we use the filter – which is exactly what we want.

To apply a Filter Correct-click in open-space (A) in the Left-side Panel to render the master context card. Click, "Apply Filter" (B) to open up the Filter menu every bit shown below:

The principal Filter window volition render, where you lot can select the Modern Comparison Filter Settings as shown in the screenshot below:

Selecting the, "By conflict status for this item record" (A), "Identical to Master" (B), "Override without Conflict" (C) and "Conflict status inherited by Parent" (D) sets the Modernistic Comparison Filters. You lot can then select, "Filter" (Due east) to utilize the filter.

The Mod Comparison Filter should process quite chop-chop in well-nigh cases, unless y'all're working with a very big mod file. The screenshot below highlights the status bar, which will tell you how far along the filter operation are towards completion:

Once done, the screenshot below illustrates the result. Both versions of the modern (at the height level) have Yellow backgrounds in the Navigation Tree (A), indicating that they are not identical (of class). In the Bulletin Tab we see that now errors were encountered past the Filter (B), along with some statistics:

Opening 1 of the mods in the Navigation Tree and selecting a record highlights the similarities where they are identical betwixt the two mods with Green backgrounds (A) and records that are different with Xanthous backgrounds (B).

At this point we are done with the comparison. You can scan through the Unofficial Fallout3 Patch records between the new and one-time versions, and compare the differences at will. If you don't need to make changes, yous tin can only close xEdit when done.

If notwithstanding there is a demand to copy records from one version of the mod to the other, the process beneath will guide you through the steps. In that location are a few limitations to be aware of, such as you lot can't drag-northward-drop records from the version you loaded at kicking time into the version you loaded with the "Compare To" function, but y'all tin still re-create from that version as shown beneath:

Here we Left-click-and-hold the record we desire to copy with the mouse (A), and drag it horizontally to the mod we loaded when xEdit booted-up (B). Dropping the record into the row will copy that record (and all of its attributers) into the other mod. The screenshot below shows the results, with both sides now identical (A) and the background of both now Green (B) indicating they are indeed duplicates:

The screenshot below illustrates how xEdit will preclude you from elevate-due north-dropping records from the loaded version of Unofficial Fallout3 Patch into the "Compare To" version (which is loaded read-only). Note how when trying the drag-n-drib, you lot get a blocked-circumvolve (B), indicating that you can't driblet records into the read-only version:

When you're done making changes, you'll need to save them. You lot tin either close xEdit or printing, "Alt-S" to render the Salvage Changed Files window:

With that, nosotros're done with mod comparisons and updates! Of grade you should not alter the Unofficial Fallout3 Patch equally that is for Quarn to practise, but there is no impairment in experimenting with the mods to learn the procedure (just make sure to take a backup of the files before yous do!).

8.10.1.1 - Offset Important danger when compacting FormIDs

Before you consider compacting a file whether or non you are a modern writer or user understand compacting a modern changes the FormIDs. Once the FormIDs have changed that is the same as uninstalling the mod. Making certain changes may not impact anything while other changes will have a serious bear upon on the game and your relieve game.

The range of FormIDs is express for ESL flagged files. Since there isn't much to work with equally the FormIDs are renumbered y'all should consider this. They are renumbered sequentially. Once the process finishes you could cease up with a FormID that is the same equally the previous version, merely the tape is an entirely different record blazon then it was previously. Which may not just cause issues only render the save game unusable considering of the changes unless you revert back to the version of the modern prior to compacting it.

The bottom portion is blurred out because it is part of a 2 part question. The first being the result and support of uninstalling a mod and the second the result of changing a script and continuing to utilize the same save game. Smkviper is a Bethesda employee and Papyrus specialist for Bethesda having written in part of fully written the Papyrus engine.

While many people do uninstall mods and go along with a save game and it usually works fine, once yous do, no matter what happens, whatever farther testing is invalid and before reporting whatever outcome to any modern writer you lot should make a new save game. Flow.

8.10.ane.2 - Second important danger when compacting FormIDs

Patches to the mod will no longer be uniform because the FormID inverse. It is not good modding exercise to modify FormIDs and then crave other mod authors to create new patches. This is inconvenient for both mod authors and mod users. Case 2 below shows how a FormID that would not qualify for an ESL flagged file changes. This is what would happen for patches. Once the FormID is renumbered the patch can not notice the old FormID anymore.

viii.10.1.3 - Third Important danger when compacting FormIDs

You should not compact FormIDs if the modernistic uses GetFormFromFile(). The script will non be able to find the Grade used by the mod author when he created the script. Below is an example from GetFormFromFile - Game in the CK Wiki. This is another example of how a FormID that does not qualify for an ESL flagged file could be renumbered every bit shown in Example 2 and cause the script to malfunction.

; Obtain class 0400ABCD nosotros expect to be added by the KillerBees plugin ; Note the top most byte in the given ID is unused and then 0400ABCD FormList beekillerlist = Game.GetFormFromFile(0x0400ABCD, "KillerBees.esp") as FormList ; If "KillerBees.esp" is non loaded the form will exist NONE. Otherwise, add our weapon to the list. if ( beekillerlist )   beekillerlist.AddForm( WeapBeeSlayer ) endif        

In the above example 0400ABCD would not qualify to be in a file with the ESL flag. It would be renumbered and would be given the adjacent available number in sequence equally mentioned. For example information technology could be changed from 0400ABCD to [FE:004][005].

Sometimes mods apply Bethesda Archive Files or .bsa or .ba2 files. Some mod authors do not provide the source for their scripts. To look for the GetFormFromFile() function you will need to extract the script files and if the source is not provided you volition need to decompile the .pex files first.

This is non practical for users to wait for in a mod. At that place are no utilities that volition automatically expect at the plugin, search for all the scripts used, and then go through a process of finding this function for the user and alert them of the dangers of compacting the file.

8.x.3 - Adding the ESL flag

•  When an ESL flagged file also has the ESM flag and contains a new CELL or WRLD tape, whatsoever modernistic (patch or otherwise) besides altering the new CELL or WRLD record can cause items to disappear.

•  Whatever file with the .esl extension will take the ESM flag forced at runtime. Files with the .esl extension will too take the same issue with CELL or WRLD records equally mentioned previously.

•  Compacting a modernistic and adding the ESL flag that has non been released to the public is safe.

•  Compacting a mod and adding the ESL flag that has already been released to the public is non safe because compacting changes the FormIDs. Refer to Important dangers when compacting FormIDs.

•  After compacting a modernistic with NPCs you will need to generate the FaceGen data for the NPCs with the Cosmos Kit because the FormIDs changed.

•  Afterwards compacting a mod with custom voiced actors or NPCs, y'all will need to rename the Voice files because the FormIDs changed. Call up the file proper name for vocalisation files is non contained in the plugin. You have to know what it is already or brand a bare empty file with the CK in club to see what the CK will name it. After you know the name the CK has called then you lot can rename the vocalism files accordingly.

•  For mods that use xEdit or zEdit scripts. Adding the ESL flag to modernistic files you lot volition be processing with xEdit type scripts can impact how the script works. You should process the files without the ESL flag. You should be able add the ESL flag later on the procedure completes. If you are required to run whatsoever xEdit type scripts each time you lot add together or remove files in the Data binder this can impact how the script functions. You may need to remove the flag and add together the flag prior to and after running the script which could exist tedious.

The effect having both the ESM and ESL falg (or .esl extension) and CELL or WRLD records does not seem to affect Fallout 4. There is no word on whether or non this will be addressed by Bethesda for Skyrim SE.

8.10.4 - Adding the ESL flag for mod users

•  Normally adding the ESL flag to simple weapon or armor mods is safe because they normally do not accept patches and are not masters of other files.

•  Adding the ESL flag to patches is safe considering the patch merely affects its masters.

•  Adding the ESL flag to a mod that has a patch should not affair unless you compacted the FormIDs. If you did refer to Important dangers when compacting FormIDs.

•  When calculation a new mod to your load order and if you review Of import dangers when compacting FormIDs first prior to compacting FormIDs and so you should exist able to meaty the mod and add the ESL flag.

Adding an ESL flag to any .esp file that qualifies to take the flag is non safe to do when you lot practice not know how that will bear upon the modern. In that location is no listing of mods safe to flag and information technology is not appropriate to constantly ask modernistic authors whether or not it is safe to add the ESL flag to their modernistic. If you read through the department Adding the ESL flag and do not understand what any of that means so you should exist cautious of calculation the ESL flag to your mods.

If you lot feel you must add the ESL flag and have no other resources telling you whether or not information technology is safe then it is recommended to flag one file at a fourth dimension and exam it in game. If the mod malfunctions then you can remove the flag and revert to a previous salvage game.

8.xi - How ESL enabled games handle FormIDs for ESL flagged files

You might accept already noticed FormIDs in some tutorial (for example removing cities from JKs Skyrim), while getting items via console cheat (role player.additem) or somewhere else merely dont know what they actually are. Heres one example:

The interesting part is on the far right side: Base Grade and Ref Class.

Lets stick with the tree that Ive marked in the screenshot for a moment. The Base Form (00051126) is an entry in Skyrim.esm and stands for TreePineForest05. Information technology doesnt say annihilation about where the tree is located, about the size of the tree, its rotation or anything else. The entry in Skyrim.esm just defines a few basic parameters of that tree blazon like the blazon of the entry (TREE) and where the 3D model of that tree is located in the meshes folder of the game (Mural\Copse\TreePineForest05.nif).

At present, if y'all got a modern (or the vanilla game) that places this kind of tree somewhere in the game world, that specific tree (like the one that is clipping through the floor in my screenshot) gets a Ref Grade, which in this example is 0D00517E. For this you can define its position in the world, its size, its rotation and lots of other properties. The Ref Course is the FormID well be looking at. Information technology can be divided into two parts:

[0D] [00517E]

The first part might look familiar for anyone using Mod Organizer ii or any other modern manager that shows the load order of plugins like MO2 does. It defines where in the load society a mod is located using a two digits hexadecimal number. The mod with the lowest number gets loaded commencement, the higher ones are loaded later and overwrite the earlier ones. Your typical load order would look like this:

┌─[00] Skyrim.esm ├─[01] Update.esm ├─[02] Dawnguard.esm ├─[03] HearthFires.esm ├─[04] Dragonborn.esm ├─[05] SomeMod.esm ├─[06] SomeOtherMod.esm │ [Other Files] ├─[0C] AnotherMod.esp ├─[0D] Enhanced Landscapes.esp (the i from our example screenshot) │ [Other Files]        

Every bit hexadecimal digits go from 0 to F (F stands for xv) and equally we got two digits, the largest number you can put together is FF = 255, just like the largest number for the decimal arrangement would be 99. This is where Skyrims theoretical plugin limit of 255 comes from. Its actually a bit less than that just that shouldnt bother us here. This limit is what forces people to stop adding mods to their game or commencement merging them which gets trickier the more than mods you want to add together.

Now, what well-nigh the other 6 digits?

Those are used equally addresses for entries (records) within plugins. The tree from the screenshot got 00517E, some other tree might have 00517F, some NPC added by the same modern could have 077F20 and then on. These addresses within plugins are hexadecimal too, so the last address and highest amount of objects in ane plugin would exist FFFFFF, which is sixteen,777,215 in decimal. This means that a mod writer could theoretically stuff over 16 meg things (TREEs, NPCs, BOOKs, ACTIvators,...) into one single esp file. More than that isnt possible as nosotros would be running out of addresses again but who needs that many objects within one plugin anyhow.

So, were maniacs who already added as many mods as possible to our game and already kickoff to become Too many plugins errors from various tools and the game itself. But, of form, theres at least twenty more immersion mods out at that place that NEED to be added to our mod listing. And then theres those fifty patches for all our mods we forgot to install earlier.

In the past this would have been the point where we would have fired up the (undoubtedly cool) tool MergePlugins and trial-and-fault our way through our modlist in society to combine as many mods every bit possible, just so we stay below the magical FF/255 mark. But now theres an alternative. Skyrim Special Edition does not only sympathize master files (those .ESM files from the main game and big mods) and regular ESP plugins (any other mod) that all count towards that 256 plugins limit but likewise ESL files (I believe the Creation Lodge mods come with these) and ESP files with the so called ESL flag. And while pure ESL files suck equally theyre always loaded first and cant really exist sorted, those ESP files with the ESL flags are gold and exactly what nosotros demand. They acquit just like regular ESP plugins and even look the aforementioned from exterior but theyre not loaded in a regular load order spot like [A4] or [0D] but theyre all squished into the [Fe] spot, which now is a whole new accost space past itself.

[Fe:0A8]

├─[FB] RandomMod1.esp ├─[FC] RandomMod2.esp ├─[FD] RandomMod3.esp ├─[FE:000] RandomESLFlaggedMod1.esp ├─[FE:001] RandomESLFlaggedMod2.esp ├─[Atomic number 26:002] RandomESLFlaggedMod3.esp │ [Other Files] ├─[Atomic number 26:0C3] RandomESLFlaggedMod196.esp ├─[FE:0C4] RandomESLFlaggedMod197.esp │ [Other Files] ├─[FE:FA9] RandomESLFlaggedMod4009.esp ├─[FE:FAA] RandomESLFlaggedMod4010.esp ├─[FE:FAB] RandomESLFlaggedMod4011.esp        

This is what the load order address of an ESL flagged plugin looks similar. And this is what a bunch of ESL flagged plugins in your load order would await similar:

Wait, what? Mod 4011?

Every bit [Fe:FFF] would be the highest address for an ESL flagged plugin and as the FE-part always stays the same as thats the position of the whole bunch of ESL flagged plugins in the regular load gild, FFF is the maximum corporeality of plugins we tin accept in this accost space. And thats a whopping 4096 of them!

This effectively means we're not express to 256 plugins anymore but to 254 (as the Iron-slot is blocked) plus 4096 = 4351 plugins!

As yous might take guessed there has to be a downside. And of course you are right. As the accost of the plugin itself in the load guild now takes upwards five instead of just two digits, theres less digits left to address stuff inside the plugin. Instead of half dozen digits (000000-FFFFFF = over sixteen one thousand thousand) for records we can utilize for NPCs, TREEs and other things inside our plugin nosotros merely got 3 digits (000-FFF = 4096) left. This gets articulate when we compare them side to side:

Regular:  [0D]  [000012] ESL-flag: [Atomic number 26:00D] [012]        

At a first glance this doesnt seam besides bad every bit 4096 is yet a large amount of records within a plugin. But theres a few problems that might be in the way. Let me demonstrate with three examples:

The hypothetical plugin in position [A4] we want to flag as ESL has three records 000001, 000002 and 000003.

[A4] [000001] [A4] [000002] [A4] [000003]        

A plugin like that can be easily flagged every bit ESL as theres less than 4096 records and the records would however fit well into the ESL accost space. In that location would be no issues and apart from setting the flag null else would have to be done. The result would expect like this:

[FE:001] [001] [Fe:001] [002] [Fe:001] [003]        

As the addresses inside the plugin would not change, any patches or addons with that plugin as a master would yet find the records inside theyre trying to reference to. In case you're wondering if the game notices the missing zeros, it does not. Leading zeros are ignored. Yous tin examination this by setting the weather via the ingame console with fw 0010a243 and with fw 10a243. The result will be the same.

The hypothetical plugin in position [A4] nosotros want to flag as ESL got three records: 000001, 000002 and 0FA322

[A4] [000001] [A4] [000002] [A4] [0FA322]        

A plugin similar that cannot be flagged as ESL just like that. The records 000001 and 000002 would be fine just like in Example 1 but 0FA322 does non fit into the iii digits address space of an ESL flagged ESP. The consequence of this: nosotros demand to compact the plugin to be able to fit in all its records. Theres a characteristic in xEdit that does only that. If we did that, the following would happen:

[A4] [000001] -> no further action [A4] [000002] -> no further action [A4] [0FA322] -> changed to [A4] [000003]        

Once again resulting in

[FE:001] [001] [FE:001] [002] [Iron:001] [003]        

Now all records fit into the three digits and the ESL flag would be set. You tin can exercise this to modest patches and other simple mods that got no patches or addons themselves. Once such a compacted plugin got another plugin thats referencing to it we got a problem tho. Something in the other plugin could try to reference to 0FA322 but it would not find annihilation at that address anymore every bit that record was inverse to 003. This could lead to diverse annoyances or even crashes. In the end, we would take to manually edit the patch/addon and change all entries of 0FA322 inside them to 003. Which would be really annoying every bit even pocket-sized plugins non only got iii records but dozens or hundreds of them. Still, if we know exactly that a plugin got no patches or addons that rely on information technology, compacting is still a viable way.

The hypothetical plugin in position [A4] we want to flag as ESL got more than 4096 records. This is normally the case for quest mods, big actor homes and compilations like Immersive Armors. As our address infinite within an ESL flagged plugin is limited to 4096 entries we merely cannot set the flag or compact the plugin. Bad luck.

viii.11.4.1 - ESLifying plugins

Now, what do we have to do to brand apply of ESL flags? Outset, we should ESLify all plugins that can be flagged without whatsoever farther changes. For this we volition demand xEdit, just become the latest version from github. With xEdit at that place is an piece of cake mode to scan your load order for plugins that are modest enough and dont need to be changed in social club to get the ESL flag.

eight.xi.four.2 - ESLifying Plugins the piece of cake way

This can be done for all plugins that are similar in our Case 1 to a higher place. Youll need to start xEdit with the arguments -PseudoESL and -autoload. PseudoESL will brandish all flaggable plugins, no thing if they already got the flag or not, with [Iron:30] load order numbers. This will be useful in a minute. Autoload skips the initial dialogue where xEdit asks you which plugins to load.

In Mod Organizer 2 you would go to the executables menu (the gear icon top left) and add SSEEdit.exe as a new executable similar displayed on the left paw side. In Vortex it would look like on the right side.

Now showtime xEdit with those arguments. For MO2 this works by starting QuickESLCheck from the dropdown menu, in the Vortex example information technology would be named SSEEdit-eslcheck but its really up to you how you name the link. After loading has finished were presented with our load order. Nosotros volition at present see three types of plugins:

•  Plugins similar CFTO-Lanterns.esp arent interesting to the states equally -PseudoESL didnt requite them a [FE:Thirty] load club number. This means they cant exist just flagged equally ESL.

•  Plugins like JKs Windhelm Relighting Skyrim Patch.esp got an [Fe:XXX] load order number only they also got the <ESL> tag. This ways theyre already flagged as ESL.

•  Plugins like Higher Compensation Rewards are what we need. They got the [FE:XXX] load club number cheers to -PseudoESL but dont have the actual ESL flag notwithstanding.

We volition modify that. Click on Higher Bounty Rewards.esp (or whatever plugins like that show upwards for you). On the right side of xEdit you will at present see some backdrop of that plugin like the Form Version, Version and Writer. What were looking for is the Record Flag line. The one of Higher Bounty Rewards is currently empty. Correct click the empty infinite and choose Edit. xEdit will present you with a couple of record flags you lot tin can set. Of course we will choose the ESL flag and hitting OK.

You can now do this to all plugins that got [Fe:XXX] load order numbers but no <ESL> flag yet. If y'all got a large modernistic listing already type [FE into the search bar at the lesser to hibernate all the regular non flaggable plugins like [86] CFTO-Lanterns.esp, and then you will only demand to look for lines without the <ESL> flag.

One time you are done merely close xEdit. It will show a window with all plugins you have changed. Make certain all of them are checked and hit OK.

Thats really it, theres nix more to it.

I re-practise this check once in a while after adding a bunch of new mods to continue my modlist every bit ESLified as possible.

Since the functionality to compact FormIDs is bachelor from xEdit the process will be shown. However, it is not recommended for end users that are unaware of the dangers of compacting FormIDs. For more information encounter Important dangers when compacting FormIDs

Once you have flagged all possible plugins with the easy method above you should be fine for a while. At some point if you see Skyrims plugin limit again, what you can do is a chip more dangerous so really think about the plugins you do this to. Again review Important dangers when compacting FormIDs.

Start xEdit the regular manner, correct click any plugin and choose Compact FormIDs for ESL. Now iii things can happen:

•  If you try to do this to a plugin that already got the ESL flag the option wont even show upwardly

•  If you try to do this to a plugin too big to exist flagged as ESL youll become an fault saying The file contains too many new records for this operation and nothing happens

•  If you try to practise this to a plugin with few plenty records y'all will get a alarm

If yous get this you have constitute a plugin that tin be compacted. The showtime line only tells you how many records will be inverse. Nonetheless, you should pay close attention to the second line of that warning. This tells you what kind of records will be changed and thats really of import as some kinds of records volition somehow break if y'all try to compact them. Co-ordinate to ElminsterAU you should really avoid compacting plugins when 1 of the following tape types would be touched:

•  INFO

•  NPC_

If that is not the instance for your plugin make certain the file you are compacting is not a master of other modules. Because afterward compacting the plugin the FormIDs will have inverse and other modules that depend on this file as a master will non discover the records they are looking for anymore.

If you lot are sure about everything striking yes. xEdit will compact the plugin and lists all changes in the correct side of the window, looking similar this:

[00:02] Changing FormID [3300B865] in file "JKs Whiterun exterior.esp" to [33000CA3] [00:02] Changing FormID [3300B867] in file "JKs Whiterun exterior.esp" to [33000CA4] [00:02] Changing FormID [3300B868] in file "JKs Whiterun outside.esp" to [33000CA5]        

At present, if y'all are actually thorough you lot could write down all the changes that take been made. And then you could compact plugins that are reference the module as a master. You could also cheque all patches for the plugin and update the FormIDs like 00B868 in the above example to what they were inverse to during the compacting process. If you lot are diligent and knowledgeable plenty you lot could meaty whatever plugin that qualifies and save even more space in your load order.

Every update to the compacted plugin or plugins related to it will break everything for your current save game.

• elwaps , for creating the additional data well-nigh .esl files

smithalings.blogspot.com

Source: https://tes5edit.github.io/docs/8-managing-mod-files.html

Share this post