Difference between revisions of "De-Isolation Tutorial"
Jump to navigation
Jump to search
→Esmify (bit-flip) Method: Moved from ESP Mastering
imported>DragoonWraith (moving credit to bottom) |
imported>Haama (→Esmify (bit-flip) Method: Moved from ESP Mastering) |
||
| Line 69: | Line 69: | ||
For example, if you wanted to add new enemies and dungeon levels to the Knights of the Nine DLC mod, then ESP Mastering is the way to go because you're adding a bunch of new content. If you just want to alter the existing enemies and dungeon levels in KotN, then ESP Patching is probably a better solution. | For example, if you wanted to add new enemies and dungeon levels to the Knights of the Nine DLC mod, then ESP Mastering is the way to go because you're adding a bunch of new content. If you just want to alter the existing enemies and dungeon levels in KotN, then ESP Patching is probably a better solution. | ||
=== Esmify (bit-flip) Method === | === Esmify (bit-flip) Method (Wrye Bash) === | ||
There are two ways to use [http://wrye.ufrealms.net/#WryeBash Wrye Bash] to make esp masters. The older way involves creating an esm copy of the esp, then building on top of that, and then, when done, editing the masters list of the mod to point back to the esp instead of the esm. (Oddly, the game itself allows esp-mastering -- it's only TESCS that objects to it.) | |||
The newer Wrye Bash approach doesn't make an esm copy of the mod, but instead flips a bit in the esp file that fools TESCS into treating an "esp" extension file as an esm. This is a bit less messy then the older approach -- but you have to remember to flip the bit back before you play. | |||
Having said all that, the process is actually quite simple: | |||
* If you want to add an esp master to the mod, then (in Wrye Bash): | |||
** Go to Mods tab, right click on the esp you want to act as master (e.g., Alpha.esp), and... | |||
** Select '''Esmify Self''' from the context menu. | |||
* Start TESC in the normal way, and include the esm'ified esp just like you include Oblivion.esm. | |||
** Note that since it's now an "esm" as far as TESCS is concerned, it will appear near the top of the the mod listing in TESCS. | |||
* Mod in the normal way, and save your new mod (e.g. Beta.esp). | |||
** If you've done things correctly, then Beta.esp will have both Oblivion.esm and Alpha.esp as masters -- and they'll both appear in blue text in the masters list for Beta.esp in Wrye Bash. | |||
** ''The blue text is a hint that the mod is still esm'ified!'' | |||
* Before playing, you need to convert the Alpha.esp back to an esp, so... | |||
** On the Mods tab, right click on Alpha.esp and select '''Espify Self''' (the command changes to match the esm/esp state of the mod.) | |||
** '''Or...''' On the mods tab, right click on Beta.esp and select '''Espify Masters'''. This is useful if the mod has more than one esp master. | |||
'''Additional tips:''' | |||
* If a mod already has esp masters then you can quickly flip all of them to esm state by using the '''Esmify Masters''' command. | |||
* In short, you only need to use "Esmify Self" when you're adding esp masters to a mod. If it's already dependent on them, just use the "Esmify Masters" and "Espify Masters" commands on the dependent mod (Beta.esp). | |||
* If you're modding and playtesting, You can actually use "Espify Masters" ''before'' quitting TESCS -- ''so long as you don't reload the esmified esps, TESCS will continue to think that they're esms!'' If you're doing this, be ''sure'' that when you load, esps are esmified -- if they're not, then TESCS will treat them like esps and your mod will be messed up. | |||
** Just to be safe, it's probably a good idea to make backups of your mod on a regular basis. You can do this manually, and/or you can take advantage of Bash's [http://wrye.ufrealms.net/Wrye%20Bash.html#FileCommands Snapshot and Backup] features. | |||
* Not all esps cooperate well with each other. E.g., Martigens Monster Mod defines a "GoldenSaint" editor id which conflicts with the "GoldenSaint" defined by the SI version of Oblivion.esm. You'll need to understand the mods involved and the nature of the particular conflict to know whether you can ignore such warnings or not. | |||
* Unfortunately, the "Espify/Esmify Self" command can't practically be used for editing esm files. While you will be able to load the .espify-self file as a plug-in, the bit will be flipped back on the first save, making it a true .esm file again. A second save will cause a crash, presumably because master files can't be set as active, and thus can't be saved. | |||
=== Bait-and-Switch Method === | === Bait-and-Switch Method === | ||