Xaviien

Awesome. Thanks very much everyone!

Either I'm confused, or don't know enough Skyrim (both are more than possible!), but are Nordic & Stalhrim axes the same as Dragonbone axes? From what I can tell, they are 3 different weapon types. It's only the Dragonbone axes that are messed up because of this issue.

As far as I'm aware, that's correct. Does the issue apply to other display cases? Also sorry for not checking if there was alread a thread about this mod, and thanks for moving it, whoever did that.

Discussion thread: Hearthfire Display Case Fix by Krucify Wiki Link Another fix recommend by The USKP Team.

Discussion thread: DG and DB Axe Perk Compatibility fix by Gruftlord Wiki Link Another fix recommend by The USKP Team. I'm not really sure how to test this one. Seems like something that needs to be checked with TES5edit or CK or something. If anyone has any suggestions, I'm all ears!

Discussion thread: Invisibility Glitch - Eyes Fix by KingsGambit Wiki Link Another fix recommend by The USKP Team. Vanilla Before/After taking potion of Invisibility: This mod doesn't completely stop the bug, but fixes it within a few frames after it occurs, as you can see in the following video:

Makes sense to me. Thanks for clearing that up DoubleYou. I'll start posting my changes in the post release section of 2.2.9, remove the pre release section from 2.2.9.1, and it can all be copied over later. EDIT: I have started removing all those LOOT rules from the corresponding mod pages. Do each of those need to be noted on the changelog individually?

Wow. That's what I get for testing and posting at 4am. I was testing the correct mod, and posting in the wrong thread. Thanks for point this out Mos. I've make a new thread for the correct mod.

Yeah, I did. Updated above post. I got confused on how the changelog should go due to it being incomplete (obviously) and slight inconsistencies between 2.2.8 and 2.2.9 changelogs. Discussed further in the 2.2.9.1 dev thread.

Updated mod page and changelog to recommend Vanilla Sounds version as per discussion in Enchanted Reload Fix thread.

Looks like all the lines in green have been added to masterlist.yaml. I have started removing all those LOOT rules from the corresponding mod pages. Does that need to be noted on the changelog? If so, can it just be a general note regarding the removal of LOOT rules? Adding a separate note for each mod seems excessive. EDIT@4:30am: I tried learning how to Changelog, and only ended up removing one LOOT rule. Will correct the rest in around 20 hours. Need sleep. I also updated the recommendation for Animated Weapon Enchants and added that to the Changelog. I was looking at previous Changelog for reference, and there didn't seem to be a section for Pre-Release changes in the 2.2.9.1 Changelog. Should anything that has affected the 2.2.9 guide (such as the above changes) be added here, as well as in the Post-Release section of the 2.2.9 guide? I've started adding my changes here. Let me know if it needs to have dates like 2.2.9 did, or if anything else is way off the mark. In the 2.2.9 Changelog there seems to be 2 different notations regarding modified mod notes. 1. In the Post-Release section they are all noted with a description of the change. 2. The Pre-Release section it only lists the pages that were changed. The 2.2.8 Changelog only lists the pages as in 2. Which way should this be done? Does it matter? And is there a guide somewhere on how to be better at stuff like this so I can stop bothering you guys?

I can probably do that tonight if nobody else gets to it first.

OK, thanks. I'll dig through my wiki edit list and see what I've done that may need noting.

If a Pack Author starves in the woods, does anyone take over? I updated the thread ID on the wiki, but it seems some other things may need updating as well, such as the outdated list of tools.

Hi Smile, Just wanted to say thanks for making this pack. I was looking to add some survival mods on top of Extended, and got overwhelmed with all the options, and this mod recommending that mod, which recommends this other mod. That's when I thought to myself "Hey, I wonder if there is a STEP pack for this stuff". One thing I noticed, the description for Fires hurt says "No special instructions let BOSS sort it." Should BOSS be changed to LOOT? I got worried for a second and thought I'd need to start using yet another utility. Also the forum link on the wiki was old and pointed somewhere random. I updated that for you.

Hmmm, should I be updating the changelogs for all the edits to mod pages I've been doing? I only thought of this recently. If so, I guess I should probably do it now while it's easy enough to track what I've posted.

Sounds like there may have been a small glitch with the launcher. At least you got it sorted.

No, your Skyrim.ini should look similar to mine, which you should be able see here. Obviously I have added some options and edited some values, but if you only have 6 lines in your ini, something has definitely gone wrong. First step would be to run the launcher again, then run the game. You don't need to actually play, just get the launcher to launch the game. Possibly delete the skyrim.ini and skyrimprefs.ini before running the launcher to maximise the chances of it generating correctly. Failing this, I have no idea wht your ini files are so broken, or how to fix them.

Do we need to have a vote to change the options on this to Vanilla sounds?The dragon landing sound when unsheating a weapon is not very immersive, and far from Vanilla.

This thread we are posting in is specifically for that mod. It is the one we are discussing here, and advocating to include in STEP. The video I included above shows what it looks like using this mod.

The SKSE fix being this one?

Seems like a good idea. It seems to be fine for a shock weapon, but the one that causes creatures to flee is a bit excessive.

I figured this mod would be the best fix due to it having been recommended by USKP. Looks like this mod, which combines both script and mesh, and apparently fixes for both issues, on the Player and NPCs might be better. It even has the ability to map to a hotkey to correct any issues that might arise from new effects causing the problem that haven't been covered.

Yeah, my goal at the moment is to get the final few USKP recommended bug fixes into 2.2.9.1, or 2.3 at the VERY latest. They've all been thoroughly tested outside STEP, and there doesn't seem to be any real opposition to their inclusion. If there were any way to add them to USKP, they'd already be in.

Another fix recommend by The USKP Team. Vanilla Before/After taking potion of Invisibility: This mod doesn't completely stop the bug, but fixes it within a few frames after it occurs, as you can see in the following video: Wrong mod Reposted here.