You can try this mod: https://www.nexusmods.com/fallout4/mods/35922 (More like a list of instructions, though it sounds like you already have FO4Edit so it should be simple.)
There's also a script that should be part of the FO4Edit build called "Find ESP plugins which could be turned into ESL" that you run by right-clicking on the name of one of the plugins you have loaded, selecting "Apply Script" and finding it on the dropdown list. Mind you, it will scan *all* the loaded plugins and give results, so maybe run it when you have a few loaded.
The first method identifies esps that can be flagged by simply selecting the "ESL" flag. The second method will find those and the ones that require compacting the formIDs and will give warnings on which ones will break things if you do that.
This mod can be tagged as an .ESL in FO4Edit - it has the FE Form ID. I use it myself. That assumes the user has the -PseudoESL tag at the end of the Target section in Properties when using a desktop shortcut. I suppose I should give an explanation for everyone:
Create a desktop shortcut for the FO4Edit.exe (the application), right-click on the desktop shortcut icon and click on properties at the bottom. In the section that says "Target" go to the very end, which should be this: .exe" Add -PseudoESL to it so the ending looks like this: .exe" -PseudoESL with one space between the end-quotation mark and the hyphen. The user must use the shortcut with -PseudoESL for this process to work...it runs the application through the shortcut, but with an extra option.
Click on the shortcut icon to open FO4Edit. From there, any file that starts with the filename [FE can be changed into an .ESL flagged mod through FO4Edit - changing others will cause the mods to work improperly and cause those saves to become corrupted. I suggest making note of what one changes in FO4Edit. Click on the mod in FO4Edit (one can also use the FO4Edit Auto-Clean to do this, but remember to add -PsedoESL to the Target of its Properties), and then right-click in the blank section next to "Record Flags" to the right where the mod's references are listed. Click on ESL. If one uses a mod manager, be sure to use its "deploy" or "sorting" functions after making changes in FO4Edit.
And, if changing an .ESP to a .ESL, your saves with the .ESP will not recognize it as the same file. I suggest starting a new game after performing such transitions.
Great mod.. specially the fact that the torso and pants uses different slots allowing me to combine with other mods ..good for screenshots but sadly theres a slight clipping while running which really bothering me ..hoping you will look into it
its the base body that clips through..its more noticable when using bright colored nevernude ..personally i dont mind but tweaking the mesh a little bit would be nice ..the clipping most likely because of the shirt using unorthodox equip slot ...heres how its clipping through my SU nevernude https://ibb.co/wzXqBpM
9 comments
https://www.nexusmods.com/fallout4/mods/35922
(More like a list of instructions, though it sounds like you already have FO4Edit so it should be simple.)
There's also a script that should be part of the FO4Edit build called "Find ESP plugins which could be turned into ESL" that you run by right-clicking on the name of one of the plugins you have loaded, selecting "Apply Script" and finding it on the dropdown list. Mind you, it will scan *all* the loaded plugins and give results, so maybe run it when you have a few loaded.
The first method identifies esps that can be flagged by simply selecting the "ESL" flag. The second method will find those and the ones that require compacting the formIDs and will give warnings on which ones will break things if you do that.
Create a desktop shortcut for the FO4Edit.exe (the application), right-click on the desktop shortcut icon and click on properties at the bottom. In the section that says "Target" go to the very end, which should be this: .exe"
Add -PseudoESL to it so the ending looks like this: .exe" -PseudoESL with one space between the end-quotation mark and the hyphen. The user must use the shortcut with -PseudoESL for this process to work...it runs the application through the shortcut, but with an extra option.
Click on the shortcut icon to open FO4Edit. From there, any file that starts with the filename [FE can be changed into an .ESL flagged mod through FO4Edit - changing others will cause the mods to work improperly and cause those saves to become corrupted. I suggest making note of what one changes in FO4Edit. Click on the mod in FO4Edit (one can also use the FO4Edit Auto-Clean to do this, but remember to add -PsedoESL to the Target of its Properties), and then right-click in the blank section next to "Record Flags" to the right where the mod's references are listed. Click on ESL. If one uses a mod manager, be sure to use its "deploy" or "sorting" functions after making changes in FO4Edit.
And, if changing an .ESP to a .ESL, your saves with the .ESP will not recognize it as the same file. I suggest starting a new game after performing such transitions.
Hoping you will add more, including considering a long pants version!
Thanks!