Sharlikrans Compatibility Patches

Check out the new banners that http://www.nexusmods.com/skyrim/users/69377" rel="nofollow noopener" target="_blank">Grace Darkling made for me. That was a sweet and appreciated Christmas Gift. I added a few in game Christmas shots of my own.

Useful Links:

http://www.nexusmods.com/skyrim/mods/814" rel="nofollow noopener" target="_blank">Skyrim configurator -- by pfannkuchen_gesicht:

http://www.geforce.com/optimize/guides/the-elder-scrolls-... rel="nofollow noopener" target="_blank">Nvidia: The Elder Scrolls V: Skyrim Tweak Guide

http://boss-developers.github.io/" rel="nofollow noopener" target="_blank">BOSS

http://sourceforge.net/projects/oblivionworks/" rel="nofollow noopener" target="_blank">Wrye Bash

http://www.nexusmods.com/skyrim/mods/25859/" rel="nofollow noopener" target="_blank">TES5Edit

Overview:

The files provided were corrupt because they were made or edited with TESVSnip or, they were made with another utility prior to the the release of the CK on Feb 7 2012. The files have been repaired and cleaned with TES5Edit. Because the files have been repaired they are now more compatible with newer versions of Skyrim. They are more compatible with Wrye Bash, TES5Edit Scripts, SkyRe and other SkyProc patchers.

I will update various mods as time permits. These are not simply loaded into the CK and then saved. Any information the CK does not like, such as out of order subrecords may be striped out of the mod once you save it. So that is not the best way to resolve issues with plugins and just creates more incompatibility with other mods and potential CTDs.

Why I have made these Patches:

Before I made the patches this was the message that was in the BOSS masterlist as show in this commit for https://github.com/boss-developers/skyrim/commit/85c39c79... rel="nofollow noopener" target="_blank">MageFriendlyDragonPriestMasks.esp.

MageFriendlyDragonPriestMasks.esp

WARN: This file was released before the CK (07 Feb. 2012) and is not recommended for use and should be removed.

That lead to people posting in the authors thread, "There was a BOSS message telling me to remove the mod. What gives?" Later I added a message to where you could https://github.com/boss-developers/skyrim/commit/b9b9b03b... rel="nofollow noopener" target="_blank">get the patch.

I leave the files for users to download but closed the comments section. People just kept asking the same questions too often without looking at previous answers. The install questions weren't as bad as what I put in the FAQ. The questions that caused me the most frustration being, what is this patch for, what does it really do, why do I need it.

The out of order records cause those plugins to not work with Mators merge script, SkyProc patchers like the Reproccer, or Wrye Bash. Confirmed for the Merge Script, Reproccer, and DSR as shown in the posts in their threads. Unconfirmed for Wrye Bash because the current version only handles 18 or Skyrim's 120 records but Also, as mentioned because the plugins were made prior to the CK they were never loaded into the CK and thus made with TESVSnip or SkyEdit. The former being the major culprit and not likely the latter since it was written by Dave Humphry.

Requests:

Thanks for all the kind words I am glad to hear that for some this is really relieving some CTDs. You guys are welcome. Sometimes I receive requests to update files in some way. Maybe the request is to add specific DLC support or alter the meshes to work with a weight slider. I do not provide updates to the mods I only repair the corrupt plugin. Please don't ask for a patch if it does not have out of order subrecords. I don't mind requests but I have discovered that if the plugin does not have out of order subrecords loading the plugin into the CK, saving it, and cleaning it with TES5Edit is all it needs.

How To Install:

Unless otherwise specified, download the author's original mod listed below. Then install the esp provided into your data folder and overwrite the old esp or esm files with the ones I have provided.

BOSS or LOOT messages:

Work In Progress: In the past the BOSS and LOOT messages appeared based on the CRC value of the file. BOSS 2. 1 was the current release at the time I started making the patches and it had a bug in it where it would not read the plugin header for version numbers. LOOT and BOSS v2. 3. 0 can use a version number in the plugin header. So over time I will be adding version numbers to the plugins. Then when you make your own personal modifications to the files the BOSS or LOOT message won't appear. Just keep in mind that I may not have changed the file yet because I am busy with other things.

If you install any of my patches and you still see the message then your installer such as ModOrganizer, NMM, or Wrye Bash did not overwrite the file correctly or you modified the file so now the CRC is different. Once the version numbers are added to all the files then you won't see the error message because of CRC differences you will only see it if you didn't overwrite the file correctly.

Troubleshooting BOSS or LOOT messages:

ModOrganizer:

I don't use Mod Organizer because I don't like the files in virtual folders. Because of that I don't have good troubleshooting steps I can suggest. However, when you have installed the original mod then my patch and you see the BOSS or LOOT message then it simply wasn't overwritten correctly or you modified the file. So if you haven't modified the file then you need to talk to other Mod Organizer users and ask them how to properly install two mods so that the second mod overwrites files from a previous mod.

I would guess that installing files for ModOrganizer is similar to Wrye Bash. The original mod should be first or higher in the list then my patch. As long as you install the original mod first and mine second then it should overwrite files correctly. Consult the MO documentation and anything related to overwriting files. The patch is already an installer archive just like the original authors file. Make sure the patch will overwrite the file from the original installer archive. You may have to place it second, after, or lower, whatever th

...