Can't delete master dependency?

[BambiCookies]

I'm trying to merge esps to decrease the plugin limit and this mod Arbitration has 3 plugins that don't conflict and could easily use one plugin.

However when trying to merge them they become dependant, whereas the only Master they need is the Fallout4.esm.

I can't seem to delete the dependencies despite this, could someone help me out as to what I'm doing wrong?

Edited January 11, 2019 by BambiCookies

[Druuler]

Have you tried deleting the dependency at the MAST - Filename line? It has been quite a while since I have done anything like this in xEdit, but I think that is where you are supposed to make the deletion, not the Master File line itself.

[amokrun1]

I actually looked into this yesterday for myself and did it through Creation Kit with CTRL +DEL. Not sure if it works when merging them, I'm sure what I needed was a very basic thing.

[BambiCookies]

Have you tried deleting the dependency at the MAST - Filename line? It has been quite a while since I have done anything like this in xEdit, but I think that is where you are supposed to make the deletion, not the Master File line itself.

 

 

I actually looked into this yesterday for myself and did it through Creation Kit with CTRL +DEL. Not sure if it works when merging them, I'm sure what I needed was a very basic thing.

 

I tried both of these and neither worked. :c

[Druuler]

The only other thing I can think of, is to merge the mods into an .esp instead of an .esl, delete the dependencies, then convert it into an .esl in the FO4 Creation Kit. This assumes that FO4Edit will give you the option to merge into an esp instead of an esl.

[BambiCookies]

The only other thing I can think of, is to merge the mods into an .esp instead of an .esl, delete the dependencies, then convert it into an .esl in the FO4 Creation Kit. This assumes that FO4Edit will give you the option to merge into an esp instead of an esl.

 

Trying to merge them creates the undeletable dependencies, either from creating a new esp and copying over or overriding into one of the already existing plugins.

It's rather frustrating.

[wim95]

You have dependencies

 

1. Object Effect record in your plugin: Right mouse button -> "Change FormId" -> enter FE000800 -> OK -> In pop-up window, select all entries -> click OK

2. Game Setting records in your plugin: select all records (click first, hold shift, click last) -> Right mouse button -> "Change FormId" -> In the pop-up window, select your plugin -> click OK

3. your plugin: Right mouse button -> "Clean Masters"

4. "It Just Works" ©

Edited January 11, 2019 by wim95

[VIitS]

^What he said. Merging involves more than just "Copy as Override". With the addition that removing masters manually when there are still dependencies will break a lot of records.

 

Even if you did remove/renumber all the records pointing at old masters, it can still break things. I don't think there would be a problem if the only master left would be Fallout4.esm (and you actually had all the master-dependent records fixed/removed), but I'm not certain. The reason there can still be a problem even if all the master-dependent records were tweaked/renumbered to be internal to the plugin is that the Master list is basically a mini-load order for records i nthat plugin, and they have internal IDs that you don't see.

 

Clean Masters renumbers those internal IDs properly, just editing the sub-record in the file header doesn't.

 

So basically, that feature was removed for a reason, just use Clean Masters instead. And if Clean Masters doesn't remove a master, there are still dependencies. You can use the "Report Masters" script to tell you what records you need to fix first.

[BambiCookies]

Alrighty, thanks. I'll give that a shot.