Skyrim Revisited Pre-Release Feedback

[Darth_mathias]

I would like to recommend these two small mods for including with SRLE there small and should be compatible but they also make sense to me.

 

Farmers Sell Produce
https://www.nexusmods.com/skyrim/mods/...

Mine Foreman Sell Ore
https://www.nexusmods.com/skyrim/mods/...

[darkside]

@Neo

 

I found this information on WAF mod page regarding Weapons & Armor_TrueWeaponsLvlLists.esp. I agree with you that this file may not be needed.

 

---------------

 

- Weapons & Armor_TrueWeaponsLvlLists.esp (this should be at the very bottom of your load order)

If using any of the optional patches, load the patch last, after both Weapons & Armor Fixes and the other mod that is being patched.

If using any of the optional "True Weapons" files, load them just after the main WAF file.  The True Weapon versions also include an additional file called Weapons & Armor_TrueWeaponsLvlLists.esp.  This file should be placed at the very end of your load order.  It contains a copy of the leveled list edits from WAF and is basically a "helper" file for creating a Bashed Patch.  The reason for this is that the Bashed Patch doesn't do a great job at combining the type of edits that the True Weapons files make to the leveled lists.  Often, if you have another mod that edits the same leveled list, the Bashed Patch will end up reverting the leveled list changes from WAF's True Weapons.  By loading this helper file last, it will make help ensure your Bashed Patch contains the correct edits.

Edited March 14, 2015 by darkside

[statmonster]

"Weapons & Armor_TrueWeaponsLvlLists.esp (Changes appear identical to main plugin. Possible error in installer.)"

 

I thought this was not so much a mistake but rather a file to help make sure the bashed patch worked right.  Since WAF is high in the load order its leveled lists will tend to get overwritten by other mods.  This auxiliary .esp is a file top load late in the order to make sure those changes are carried over in the basked patch's leveled lists - thus they are identical.  Of course if you are going in and building patches in TES5Edit this is unnecessary - but krypto' wanted something useable by people who don;t know how to use TES5Edit - or so I assume.

 

Of course with CCOR 1.6, it looks like CCO Compatibility Patch for WAF True Weapons (where CCO_WAFTrueWeapons_Patch.esp has been renamed as Weapons & Armor_TrueWeaponsLvlLists.esp) replaces this anyway so you neither need to hide via optionals nor delete it.

 

PS - Moving into an optional ESP with MO achieves much the same thing (as deleting it) without having to delete the file (in case you want it back later).

 

Thanks again for all your work on SRLE!

Edited March 14, 2015 by statmonster

[statmonster]

In CCOR the instruictioins say not to install:

 

• meshes/armor/AmuletsandRings/EbonyRing*.nif (Gemling Queen Jewelry is superior.)
• meshes/armor/AmuletsandRings/GoldRing*.nif (Gemling Queen Jewelry is superior.)
• meshes/armor/AmuletsandRings/JadeRing*.nif (Gemling Queen Jewelry is superior.)
• meshes/armor/AmuletsandRings/SilverRing*.nif (Gemling Queen Jewelry is superior.)

Does capitalization matter?  That is should we install goldringamethyst_1.nif (which does not appear to be in Gemling) for example? 

 

I assume it does matter for your instructions... (to avoid issues with missing meshes).

Edited March 14, 2015 by statmonster

[kryptopyr]

 

I thought this was not so much a mistake but rather a file to help make sure the bashed patch worked right.  Since WAF is high in the load order its leveled lists will tend to get overwritten by other mods.  This auxiliary .esp is a file top load late in the order to make sure those changes are carried over in the basked patch's leveled lists - thus they are identical.  Of course if you are going in and building patches in TES5Edit this is unnecessary - but krypto' wanted something useable by people who don;t know how to use TES5Edit - or so I assume.

Yep, this is exactly it.

[danielleonyett]

In CCOR the instruictioins say not to install:

 

• meshes/armor/AmuletsandRings/EbonyRing*.nif (Gemling Queen Jewelry is superior.)
• meshes/armor/AmuletsandRings/GoldRing*.nif (Gemling Queen Jewelry is superior.)
• meshes/armor/AmuletsandRings/JadeRing*.nif (Gemling Queen Jewelry is superior.)
• meshes/armor/AmuletsandRings/SilverRing*.nif (Gemling Queen Jewelry is superior.)

Does capitalization matter?  That is should we install goldringamethyst_1.nif (which does not appear to be in Gemling) for example? 

 

I assume it does matter for your instructions...

I highly doubt that Neo differentiates between uppercase and lowercase when specifying file names, so I would assume that you would not install goldringamethyst_1.nif according to Neo's instructions. However, if you are saying that file is not actually included in Gemling, then that may be an oversight in the guide. I'm not that far into the guide right now, so I can't concur.

Edited March 14, 2015 by danielleonyett

[statmonster]

I highly doubt that Neo differentiates between uppercase and lowercase when specifying file names, so I would assume that you would not install goldringamethyst_1.nif according to Neo's instructions. However, if you are saying that file is not actually included in Gemling, then that may be an oversight in the guide. I'm not that far into the guide right now, so I can't concur.

I made the same assumption but upon review capitalization does seem to matter - I think the pure lower case items are meshes newly added by this mod.

[Darth_mathias]

"Weapons & Armor_TrueWeaponsLvlLists.esp (Changes appear identical to main plugin. Possible error in installer.)"

 

I thought this was not so much a mistake but rather a file to help make sure the bashed patch worked right.  Since WAF is high in the load order its leveled lists will tend to get overwritten by other mods.  This auxiliary .esp is a file top load late in the order to make sure those changes are carried over in the basked patch's leveled lists - thus they are identical.  Of course if you are going in and building patches in TES5Edit this is unnecessary - but krypto' wanted something useable by people who don;t know how to use TES5Edit - or so I assume.

 

Of course with CCOR 1.6, it looks like CCO Compatibility Patch for WAF True Weapons (where CCO_WAFTrueWeapons_Patch.esp has been renamed as Weapons & Armor_TrueWeaponsLvlLists.esp) replaces this anyway so you neither need to hide via optionals nor delete it.

 

PS - Moving into an optional ESP with MO achieves much the same thing (as deleting it) without having to delete the file (in case you want it back later).

 

Thanks again for all your work on SRLE!

 

 

Yep, this is exactly it.

so the advice it is actually keep Weapons & Armor_TrueWeaponsLvlLists.esp and place near bottom of load order.

 

maybe create a boss rule something like Bottom of "Extra Late" for this ESP.

[DanimalTwo]

In CCOR the instruictioins say not to install:

 

• meshes/armor/AmuletsandRings/EbonyRing*.nif (Gemling Queen Jewelry is superior.)
• meshes/armor/AmuletsandRings/GoldRing*.nif (Gemling Queen Jewelry is superior.)
• meshes/armor/AmuletsandRings/JadeRing*.nif (Gemling Queen Jewelry is superior.)
• meshes/armor/AmuletsandRings/SilverRing*.nif (Gemling Queen Jewelry is superior.)

Does capitalization matter?  That is should we install goldringamethyst_1.nif (which does not appear to be in Gemling) for example? 

 

I assume it does matter for your instructions... (to avoid issues with missing meshes).

Being a Unix guy, capitalization does matter (Gold* and gold* are different), however in Windows capitalization does not matter (Gold* and gold* are the same). But because the way the guide was written, like you I assumed GoldRing* and goldring* are different and thought to also ask this very question to be sure. I only did not install if capitalization was the same.

[GrantSP]

Using MO to verify the status of overwritten files shows that capitalisation doesn't matter.

As an example, SMIM & CCOR both use goldringamethyst_1.nif but one is capitalised (actually CamelCase) and the other lowercase. MO correctly shows them as the same file and appear in the conflicts tab.

[statmonster]

so the advice it is actually keep Weapons & Armor_TrueWeaponsLvlLists.esp and place near bottom of load order.

 

maybe create a boss rule something like Bottom of "Extra Late" for this ESP.

I think it is just replacing CCO_WAFTrueWeapons_Patch.esp, which already has BUM instructions: BOTTOM Compatibility Patches.

[statmonster]

Using MO to verify the status of overwritten files shows that capitalisation doesn't matter.

As an example, SMIM & CCOR both use goldringamethyst_1.nif but one is capitalised (actually CamelCase) and the other lowercase. MO correctly shows them as the same file and appear in the conflicts tab.

It's not an issue of how MO works but which meshes are available in the different mods.  The capitalized ones do not exist in Gemling (they do in SMIM though), thus there is no need to remove them to allow Gamling's superior meshes to be used.

Edited March 15, 2015 by statmonster

[GrantSP]

Sorry I must have misunderstood what was asked. I took it that the question was whether or not the filenames make a difference if they are capitalised or lowercase.

I only used the MO example to answer that aspect of the discussion, not to show how MO works.

 

I used SMIM simply because I don't have Gemling Queen installed.

[Jverv]

Can I just go a bit off topic for a sec and point out that Kryptopyr reads this post... Kryptopyr; your a god!! And Bethesda owes you some profits of skyrim because you fixed their game for them!

[Neovalen]

Capitalization doesn't seem to matter. Updates made for today's changes.