Difference between revisions of "Creating Custom Master Files"
Jump to navigation
Jump to search
Removed info related to the now-defunct TESVSnip tool
imported>David Brasher (→Referencing the Master File: TESVSnip danger warning.) |
imported>ShadeMe (Removed info related to the now-defunct TESVSnip tool) |
||
| Line 17: | Line 17: | ||
==Referencing the Master File== | ==Referencing the Master File== | ||
If you expect to have a Plugin reference the Master File: open both the Master File and Plugin (as active) and simply re-save your Plugin. It is strongly recommended that you back up your original Plugin in case you do something wrong. Like if you realize you did not want your .esp to reference a particular Master File. | If you expect to have a Plugin reference the Master File: open both the Master File and Plugin (as active) and simply re-save your Plugin. It is strongly recommended that you back up your original Plugin in case you do something wrong. Like if you realize you did not want your .esp to reference a particular Master File. | ||
==Removing a Mod's Dependency on a Master File== | ==Removing a Mod's Dependency on a Master File== | ||
| Line 45: | Line 42: | ||
*To remove the connection to an .esp master, one can simply load up the mod in the CK without .esmifying the .esp master in Wrye Bash, and then save the mod in the CK. (This action can be performed by accident and is a leading cause of ruined mods with .esp masters.) | *To remove the connection to an .esp master, one can simply load up the mod in the CK without .esmifying the .esp master in Wrye Bash, and then save the mod in the CK. (This action can be performed by accident and is a leading cause of ruined mods with .esp masters.) | ||