Jump to content

Masterfiles Pros and Cons


Zorkaz

Recommended Posts

Can anybode name a reason not to put a big standalone mod into a masterfile

(Esls are excluded)

 

Pros of Masters

-Easy to build patches upon

-Not everything is persistent, thus load time is improved

 

 

 

Cons

-Direct edit is prohibited (But it's possible to revert it into an .esp)

-Cannot be loaded after .esps and therefore can cause issues if the mod's not very independent

Link to comment
Share on other sites

  • 3 weeks later...

I like using .esm flagged .esp files for "big" mods (at least 3000 records).

 

 

I just need to remove the .esm flag in FO4Edit before I can edit it in CK and when I tested it thoroughly I can convert it back to an .esm. I don't know why should anyone avoid using .esm files for this purpose.

Link to comment
Share on other sites

The cons aren't really cons, it's the way its designed.
You cannot directly edit records and you shouldn't be doing it. esm is master file where changes should be made only by merging .esp into it using version control system that's built in into creation kit.
And because of this, of course they are always loaded before .esps

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...