vault75 Posted August 17, 2017 Share Posted August 17, 2017 Hi everyone I am the author of the Pepper Companion mod on Nexus, but I have an issue. Since the file was flagged as an ESM before I uploaded it, it's now classed as a Master File in GECK. When I made edits to it, it prompted me to save it out under a different name - so I opened the ESP in FNVEdit to try and change the flag again but now it seems to have become a slave of the original Master file, which is causing conflicts in LOOT, according to some users. I've attached a snapshot of my FNVEdit - as you can see the PepperCompanion2.esp has my extra stuff and changes, but it's implementing the original PepperCompanion.esp as its master - ideally I just want to merge them so it's one file, not two. How is this possible? Link to comment Share on other sites More sharing options...
JagMaker Posted August 17, 2017 Share Posted August 17, 2017 load Creation kit, click ur 'PepperCompanion2.esp' but don't load it.in right-up corner find 'PepperCompanion.esm'., click on it, press ctrl-del Link to comment Share on other sites More sharing options...
vault75 Posted August 17, 2017 Author Share Posted August 17, 2017 If I do that, though, won't that delete the original data in the master file?? Link to comment Share on other sites More sharing options...
JagMaker Posted August 17, 2017 Share Posted August 17, 2017 sure it will) if u want 1 file without master - copy all data u need and untie it from master Link to comment Share on other sites More sharing options...
dubiousintent Posted August 17, 2017 Share Posted August 17, 2017 I'm not an expert on this, but I have always been told that simply deleting a master file from a plugin will break it. You need to use xEdit/FNVEdit's "Clean Master" command, but it won't succeed unless all record references to the "master" have been resolved. What I believe you need is to follow the "Merge Up Procedure" section of the wiki "Merged Plugin Guidelines for Personal Use" article to inject and "copy as override" your changes in 'PepperCompanion2.esp' (as the ModB) into 'PepperCompanion.esp' (as the ModA). That should get you down to just one ESP. I have successfully done this when creating custom versions of other plugins. -Dubious- Link to comment Share on other sites More sharing options...
Recommended Posts