esp master plugin issue

[Deleted2357927User]

I have an .esp mod that has as master another .esp (not an .esm) plugin. When I save the edited .esp on GECK it doesn't have as master the other .esp anymore. Any solution?? Edited May 10, 2012 by Guest

[micalov]

GECK does not like referencing ESP's as masters, only ESM's you need to convert the ESP that is going to be a master to an ESM with Tesnip in FOMM (select the plugin and spells> make master). Perform the edits in geck then use something like tesnip or FNVEdit to flip the master back to the ESP.

[Deleted2357927User]

GECK does not like referencing ESP's as masters, only ESM's you need to convert the ESP that is going to be a master to an ESM with Tesnip in FOMM (select the plugin and spells> make master). Perform the edits in geck then use something like tesnip or FNVEdit to flip the master back to the ESP.

 

Thanks for the answer! I only used Tesnip, I found it better in this situation than fnvedit.

[Cyberlazy]

Geck does not actualy care about if its .esm or .esp, what it really cares about is the esm *flag* in the header of the file that you use as master, you can set that via FNVedit (or tessnip)

 

ie: you can have a .esp as a master to another .esp and load it in geck, but that .esp much have its 'master' (ESM) flag set in its file header or geck ruins your file when you save it by removing the master.

 

Extra fun: FNV does not seem to care about the flag at all. However geck will not even open a file with the .esm flag set. (iirc)

 

Geck will actualy set the flag, if you save the file with a .esm extention and then geck prompty locks up. Best to avoid doing that I think.

 

I think it refuses to open .esm files as well but renaming to .esp and removing the flag fixes that, theres no real other diff between a master and non master.

 

Basicly: Use fnvedit to set/unset the flag (in the file header)

Using geck to edit a master is annoying. Use fnvedit to edit masters, since you need to use fnvedit to set/unset it as master anyway.

If you need geck to edit a master, (for example to make a script or because its GUI is nicer for some record types) Consider editing a mod that uses your master, then using FNVedit to copy the overriden records back to your master. It prevents geck spasing out and ensures you don't end up with unintended edits that are so easy to make in geck.

Edited May 11, 2012 by Cyberlazy