STEP Patches for Packs

From STEP Modding Wiki
Revision as of 23:14, February 2, 2014 by EssArrBee (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Pre-Patching checklist:

  1. Make sure you have every mod from STEP Core or STEP Extended that is a master for the patch being loaded into TES5Edit.
    • Check this in Mod Organizer by moving the mouse cursor over the STEP patch plugin and see what is listed in hover text as a missing master.
    • Install the missing mods.
  2. Run BOSS and put the mods in the right order.
    • Mods have to be in the correct load order during patching for the whole mod list to be patched correctly.
  3. It is a good idea to encourage the Bashed Patch usage even if Mod Organizer is the Official STEP Mod Manager now.
    • Open up Wrye Bash through MO and under the Mods tab look for the plugins in green text. Those are mergable to bashed patch.
    • The mergable mods can be ignored in TES5Edit if you know they do not conflict with anything, otherwise load them.
    • The Stats tag in not usuable by STEP because the functionality of that tag is not working correctly for STEP, so stats that conflict will have to be patched.

STEP 1: (Optional) Removing a dependency from the STEP Core Patch. Much more in depth guide here.

  • Open the STEP Core Patch in TES5Edit. When you open TES5Edit, right click the mod list and choose Select None. Now check the mod(s) being removed and the STEP Core Patch.esp and click Okay.
    1. To remove a dependency, find the records that are in both the mod being removed and the Core Patch.
    2. Highlight all the records from the previous step in the STEP Core Patch.esp and right click->Remove.
    3. Right click the STEP Core Patch.esp and choose Clean Masters then right click again and choose Sort Masters.
    4. The dependency for the mod is now gone from the STEP Core Patch.esp.
    5. Repeat the previous steps until all dependencies being removed are gone.
    6. You can close TES5Edit, make sure you save the STEP Core Patch.esp.

STEP 2: Load all STEP Core and your Pack's mods with TES5Edit.

  • If you have mods mergeable to Bashed Patch that will not conflict with anything then ignore those mods.
  • If you removed dependencies from the STEP Core Patch.esp then you can ignore those mods.
  1. First, look through the list of mods that your pack adds and find any patches for those mods. i.e. AOS-COT Patch.esp (Patch for Audio Overhaul for Skyrim and Climates of Tamriel)
    1. These type of patches can be merged into the STEP Core Patch as long as the patch is not a dependency for the Core Patch. TES5Edit will let you know what needs to become a dependency.
    2. To merge a patch into the STEP Core Patch.esp open up the patch in the left pane of TES5Edit to the first level. Highlight everything EXCEPT File Header, right click->Deep copy to override into...
    3. Check the STEP Core Patch.esp and click Okay.
    4. If there is a Message Box that pops up and says a plugin must become a master to the STEP Core Patch.esp then make sure it is not the patch being merged, if it is then click Cancel. If it is any other plugin that is to become a master, click Okay.
      • Any Patch that has to be a master cannot be merged into the STEP Core Patch.esp.
    5. Repeat the previous steps until all patches are merged.
  2. Right click the mod list and select Apply Filter for Cleaning
  3. Wait for TES5Edit to finish, usually the mod list will disappear and then return with red, green, and orange colors for the plugins.
    1. Start either from the top down or the bottom up by opening each record that is red.
    2. Forward any conflicts to the STEP Core Patch.esp to resolve them.
    3. If the mod from the last column has the correct record then no need to patch it. That will be the mod that wins and gets loaded by Skyrim.
    4. If the mod from any column, but the last column, has the correct record then it needs to be patched.
      • Right click the record and select Copy as override into... and check the STEP Core Patch.esp.
    5. If the correct record comes from multiple mods then the record needs to be merged.
      • Right click the record and select Copy as override into... and check the STEP Core Patch.esp.
      • Drag and drop horizontally across until all settings are patched. The STEP Core Patch.esp column will become green or orange.
      • Note: Some patching requires adding in additional lines for items or keywords. usually you can drap the items or keywords across to the same line in the STEP Core Patch.esp. The Count at the first line on top of Keywords and items needs to reflect the number of keywords or items in the STEP Core Patch.esp column.
    6. Do not merge Stats or Keywords from the Unofficial Patches, Weapons and Armor Fixes, and Clothing and Clutter Fixes (not in STEP yet, but will be soon).
    7. Not all conflicts forwarded will turn the column for the STEP Core Patch.esp green, some will be orange. That is okay as long as the correct subrecords were forwarded.
    8. There will be records that remain red for mods that load early, that does not mean that Skyrim will crash because of your patch.
    9. Sometimes even mods that load late will have red subrecords because something had to be forwarded around it or it has different Water Height or Max Height Data.
    10. Ignore any XCLW - Water Height conflicts or MHDT - Max Height Data conflicts. These do not affect anything in game.
    11. Ignore any Leveled Lists LVLI and LVLN records that conflict, these can be merged by Bashed Patch.
  4. Right click on the STEP Core Patch.esp and select Clean Masters then right click again and choose Sort Masters.
  5. You can close TES5Edit, make sure you save the STEP Core Patch.esp.

Final STEP: Rename the STEP Core Patch.esp.

  1. Open the location of the STEP Core Patch.esp in Windows Explorer.
  2. Make a copy of the STEP Core Patch.esp.
  3. Rename the copy following this format: STEP Pack-<Pack Name> Patch.esp
  4. You can now upload your patch for use with your pack.
    • Files must be in .7z format, get 7zip [1].
  5. Go to Toolbox on the top right of the page and select Upload File from the dropdown.
    • After the file is uploaded the top of the page will have the wiki style link you can use for your pack page, or to create a link in your patch wiki page.