This module covers how to flag plugins as ESL and compact Form IDs if necessary.
Prerequisite(s): SSEEdit
Before starting to ESL-ify plugins in your load order, I strongly suggest familiarising yourself with the format and when/how it should be used. Refer to the Plugin Basics and ESL Plugins articles.
You can ESL-ify a plugin if:
If a plugin contains new records and the Form IDs use more than the final three characters, they need to be compacted first. Remember that compacting Form IDs will break all dependencies.
You can apply the ESL flag to any ESP or ESM plugin in SSEEdit.
First, you need to find out whether the plugin’s Form IDs are compatible with the ESL format.
If the plugin contains no new Form IDs or only Form IDs that only use the final three characters, SSEEdit will return that there was nothing to do. The plugin can be safely ESL-ified.
If the plugin contains new Form IDs that need to be reformatted (compacted), SSEEdit will notify you about the amount of records that need their Form IDs renumbered and that this will break dependencies. If you are certain that there are no dependencies or that all dependencies are currently active and loaded, go ahead and click Yes to continue.
After compacting Form IDs or ensuring that there are no incompatible Form IDs, you can add the ESL flag.
Adding the ESL flag to an ESP will create an ESP-FE hybrid that loads in ESP space but does not count toward the 256 ESM/ESP plugin limit. If you want to move the plugin into ESM space, you need to rename its file extension from .ESP to .ESL. This will create a full ESL.
If the plugin overwrites references, you must also add the ESM flag in SSEEdit to ensure that the list of Overriden Forms is populated and the plugin works as intended. I would generally recommend ESM-flagging full ESLs as they are all meant to load in ESM space and there is no downside to doing this.