Step SSE Guide 2.2.0 Notes

[jeda21]

These are items I noticed and things which could make it helpful for a noob user:

Skyrim SE 2.2.0 https://stepmodifications.org/wiki/SkyrimSE:2.2.0

• System Setup Guide continued section
  • Step 2 Tool Configuration
  • BethINI setup
    • Change Bethini with Bethini pie
  • MO2 initialization section
• Mod installation considerations section - first bullet point is not helpful, instead, write out on each mod what to download and install since most instructions do already, make it consistent
• Move separators section to earlier in guide - example numbered lists in guide should include numbering based on separators
• New to modding section - add link to mandate page https://stepmodifications.org/wiki/STEP:Mandate
• Remove repetitive message: “Installing additional files not under Nexus' "Main Files" section as separate mods preserves their version tracking to keep pace with updates.”
• Links to mods should go to description, some go to download button
• Simple drop lit torches, why? we can already assign a number key to torches so no need for hotkey
• Make visible hud options available - enemy health bar, time, etc
• Enb - note to clarify how to brighten/darken interiors/night, etc. tweaks to taste
• Final sorting and cleaning - list a summary of the plugins that need to be unticked
• Shorter output mod names, to more easily view from drop down when selecting in executables window
• Remove since it’s not supported
  • XP32 
  • WACCF
• Flag/Color code as optional - this would affect copy under “Step 4” section
  • Unequip quiver - only for archer characters
  • Raven Rock Horse Exit - only for riders, no horses on Solstheim
  • Faction mods (e.g., thieves guild) 
  • Difficulty mods (fizzle, enemy revolution, smart npc potions, etc.) 
  • CACO, CCOR, TCIY
  • third person mods (e.g.,run sprint and jump, stronger swimming animation) as optional, and add options for first person also as optional
  • race specific mods (Masque of Argonian Vile) as optional, and add options for other races also as optional (e.g., Feral - Claw Unarmed Attacks for Beast Races - Vampires - Werewolves; Vampires Fight With Claws SE)
  • Immersive HUD
• When to generate lod - add acmos
• Add section when to generate nemesis - like "when to generate lod" section

System Setup Guide https://stepmodifications.org/wiki/Guide:System_Setup_Guide

• add versioning and date to this page/doc
• list all games that refer to this page
• Add acmos install instruction section?

Misc - guides for:

• managing different characters 
• player home mods
• follower mods
• weather mods
• different enb setups
• Parallax
• races: khajiit, argonian, vampires, werewolves
• Nemesis
• Make printable versions of guides
• Difference between hiding plugin vs unchecking

[Mercury71]

A few first comments...

Bethini Pie will be used in next version off the guide.

Final sorting and cleaning - No plugins are need to be unticked.

XP32: We use the meshes

WACCF: What do you mean not supported?

Flag/color code as optional: Guide should be keept simple. You should not have to change what mods to activate due to playstyle. There are in my opinion in some cases already to many "options". Keeping up more possible "versions off the guide within the guide" creates a lot off work for the guide devs.

Misc - guides for: Pleas feel free to create additional guides, would be great! Most people uses STEP as a base and then adds a few mods, so i think the actuall guide should be kept basic and simple. For example i never personal use followers or homes when i play, so i dont want to much added stuff like that in the guide.

[jeda21]

Final Sorting and Cleaning: if a user follows the step guide, there are a bunch of plugins that shouldn't be ticked, having a list at the bottom to help a user double check they unselected the  correct ones could be helpful vs having to scroll up or CTRL+F

XP32: needs to state we use meshes, it doesn't say anything now, except to post any issues in the forum

WACCF: Under Step Patches section, it says 

• The "Step Patch - WACCF.esp" plugin is a component of the CR patch files and is maintained separately for more advanced guide followers that don't want to use WACCF (which is NOT officially supported.)

[z929669]

1 hour ago, jeda21 said:

Final Sorting and Cleaning: if a user follows the step guide, there are a bunch of plugins that shouldn't be ticked, having a list at the bottom to help a user double check they unselected the  correct ones could be helpful vs having to scroll up or CTRL+F

XP32: needs to state we use meshes, it doesn't say anything now, except to post any issues in the forum

It says lots, IMO:

Hide or don't hide. Post on the forums with any info on the difference.

1 hour ago, jeda21 said:

WACCF: Under Step Patches section, it says 

 

• The "Step Patch - WACCF.esp" plugin is a component of the CR patch files and is maintained separately for more advanced guide followers that don't want to use WACCF (which is NOT officially supported.)

So, what's your point?

We're not updating the guide for the play-by-play of BGS and related mod updates. Many mods are likely holding off for the traditional post-release hotfix. Things need time to settle and stabilize.

Not using WACCF or any other component of required patches is not supported.

[DoubleYou]

It's a grammatical thing. It is unclear what "which" is referring to, as typically it should follow immediately after the item, which it is referring to, in this case WACCF. Probably the easiest way to clarify this is to substitute your statement instead. 

[z929669]

8 hours ago, DoubleYou said:

It's a grammatical thing. It is unclear what "which" is referring to, as typically it should follow immediately after the item, which it is referring to, in this case WACCF. Probably the easiest way to clarify this is to substitute your statement instead. 

Ahh, yes I see. I'll replace 'which' with WACCF.

 

Actually, that^ would still be unclear. I think the change resolves the ambiguity:

Quote

The "Step Patch - WACCF.esp" plugin is a component of the CR patch files and is maintained independently. This way, WACCF can be disabled by advanced guide followers that don't want to use it. (disabling WACCF is NOT officially supported.)

 

[DoubleYou]

40 minutes ago, z929669 said:

Ahh, yes I see. I'll replace 'which' with WACCF.

 

Actually, that^ would still be unclear. I think the change resolves the ambiguity:

 

Perfect. 

[jeda21]

Thanks for welcoming feedback peeps, I appreciate it.

On 12/23/2023 at 10:25 PM, z929669 said:

It says lots, IMO:

Hide or don't hide. Post on the forums with any info on the difference.

So, what's your point?

We're not updating the guide for the play-by-play of BGS and related mod updates. Many mods are likely holding off for the traditional post-release hotfix. Things need time to settle and stabilize.

Not using WACCF or any other component of required patches is not supported.

A link to "how to disable plugins" is not = to "which plugins need to be disabled in this guide"

Edited December 26, 2023 by jeda21

[Mercury71]

11 minutes ago, jeda21 said:

Thanks for welcoming feedback peeps, I appreciate it.

A link to "how to disable plugins" is not = to "which plugins need to be disabled in this guide"

If a plugin should be disabled, the guide tells it in the installation instructions for that specific mod. No need to list them in the final sorting and cleaning step, since they should have been disabled when the mod was installed and activated. If you have plugins activated that are not suposed to be after finsihed the guide... you have not followd the guide.

[jeda21]

I'm spoiled, at my company we have a Scrum agile pre-prod and prod checklist to double check things

[z929669]

10 hours ago, jeda21 said:

Thanks for welcoming feedback peeps, I appreciate it.

A link to "how to disable plugins" is not = to "which plugins need to be disabled in this guide"

As Greg mentioned, we don't summarize information already included in the previous mod-specific instructions. That would be redundant and increase maintenance burden, leading to higher risk of things getting out of sync between guide instructions and mod-specific instructions. These are two distinct instruction sets or this reason.

On 12/23/2023 at 9:18 PM, jeda21 said:

XP32: needs to state we use meshes, it doesn't say anything now, except to post any issues in the forum

This was your comment I was responding to. It's just not true as it is written. The XP32 mod instructions state that the XPMSE.esp plugin can be hidden at user's discretion. We haven't tested if it has any impact or not. We don't really know what issues it is addressing if any. We're awaiting feedback from users, as testing it is not a priority at this time.