Difference between revisions of "De-Isolation Tutorial"

1,643 bytes added ,  13:11, 24 July 2007
→‎ESM Mastering: details added
imported>Dev akm
(new sections)
imported>Dev akm
(→‎ESM Mastering: details added)
Line 36: Line 36:
== ESM Mastering ==
== ESM Mastering ==


Many large mods use ESM Mastering to get around the limitations of standard plugins. Even though master files are generally supposed to only contain new content, they can in fact use content from other masters, such as Oblivion.esm.  
Many large mods use ESM Mastering to get around the limitations of standard plugins. However, creating your own master files can be tricky in some cases, so it's not generally recommended unless you have a strong need to do so.  


Adding more details here.  
Even though master files are generally supposed to only contain new content, this rule can sometimes be ignored if you really have a need to do so. Master files can in fact both use and modify content from other masters, such as Oblivion.esm, as long as they don't alter any cells (especially exterior cells) in another master.
 
If your mod adds a lot of new content but doesn't alter any standard Oblivion.esm cells, then it can probably be turned into a master. This makes it easy to then offer add-on option modules to extend or tweak your base master. However, you should be careful about such decisions since master files don't have the same load-order flexibility as normal plugins (masters always load before plugins).
 
If your mod adds a lot of new content and needs to alter cells in another master, then you probably need both an ESM (for the new content) and an ESP (to connect your ESM to Oblivion.esm). For example, if you create a new worldspace and place it in a master file, then you should use a separate plugin to connect your mastered worldspace to Tamriel. The '''Split Plugin''' feature in TES4Gecko can help in situations like this.
 
The process for creating a master file is simple using either Wrye Bash or TES4Gecko:
 
* In Wrye Bash, go to the Mods tab, right-click on the plugin you want to convert, and select ''Copy to Master''.
 
* In TES4Gecko, click the ''Convert to Master'' button, select the plugin you want to convert, and click ''Open''.
 
Either of these methods will give you a new file named MyPlugin.esm (assuming the original was MyPlugin.esp).
 
Now you can launch TESCS, select your new master, and start creating plugins based on it.


== ESP Mastering ==
== ESP Mastering ==
Anonymous user