ESLify Split ‐ Directions - Michael-wigontherun/ESLifyEverything GitHub Wiki

Overview

ESLify Split is for splitting records out of the plugin to a new plugin and allowing ESLify Everything to resolve any possible references to them inside data files or plugins requiring the mod.

  • This can not be done to any record at any time.
  • This can actually be fairly dangerous
  • Please only use this feature if you are an advanced mod user who knows how to check errors, problem solve, and already know how to do this manually
  • This is really only meant to take away the tedious process of fixing every patch for the records, this is not a life hack like the rest of ESLify Everything

Do not ever split merges. Always redo them with less mods if you want it to load it as a ESPFE in light plugin space.

This I feel is worth while tool because of mods that are just above 2048, so they are just outside the range of being turned into a ESPFE.

I have included a few new xEdit Scrips

  • _CountFormsForHeader.pas
  • _ESLifyModSplit_Step1.pas
  • _ESLifyModSplit_Step2.pas
  • _ESLifyModSplit_Step3.pas

What to look for and when to try this

Firstly, The same criteria for ESLify is applied minus the 2048 new record limit. Anything with new Cells or Worldspace's can not and should not be eslified unless it adds a cell that will never be added to by another mod.

If the mod can already be compacted into an ESPFE there is no reason to split the mod.

Secondly, the script "_CountFormsForHeader.pas" will count how many new records are in each plugin. This can be helpful for both this and creating Merges that will sit in esl space. After running "_CountFormsForHeader.pas" if its more then 2500 I wouldn't proceed with trying to split the mod. Now if it is a mod that only adds objects to cells and world space and you know what you are doing go wild with how many records exist.

Next check what can be split off and what can not be. anything that is not referenced by something else in the plugin is usually safe to split off. A few things that are usually safe to split off from most safe to least safe:

  1. Load Screen, Absolutely 98% sure nothing will reference these for anything other then overriding inside of plugins and even if you mess up it will just have a duplicate Load Screen that you probably won't notice there are 2
  2. Constructible Objects, usually nothing will reference these unless its a Crafting Overhaul
  3. Placed objects inside of Cells and Worldspace Cells, These can be dangerous you just have to be more careful on what you are splitting.
  4. Dialog Topics and Dialog Responses, These can be dangerous if you do it wrong or mess up a step.

As I stated previously only try this if you are already capable of doing this process manually.

Directions

  1. Find the mod you want to Eslify. and determine what can be split and what can not be split off of the main plugin.
  2. Run the xEdit script "_ESLifyModSplit_Step1.pas" on the plugin, this will set a unique EDID modifier on each record and output a csv filled with the original FormIDs.
  3. Highlight all the records you know you can split from the original mod and Right Click -> "Copy as new record into..." into the new plugin you wish to split them to.

This can be done all at once or one by one it does not matter

  1. Run the xEdit script "_ESLifyModSplit_Step2.pas" on the plugin you moved the records too. This will output the new record data to a csv filled with the new FormIDs.
  2. Now run the "ESLifySplitModInterpreter.exe", from MO2 if your using it.
  3. Once you are satisfied run "_ESLifyModSplit_Step3.pas" on both the original plugin and the plugin you split to. This will remove the unique identifier from the EDIDs. Save and further compact the Original mod and set the ESL flag on both plugin headers. xEdit should already compact the records you used "Copy as new record into..." on so no need to further compact the plugins with split mod data.