Jump to content
  • 0
Sign in to follow this  
junglejudas

STEP 2.2.9 1.C Utilities clarification question

Question

perception check, please!

if one wants to incorporate all of the utilities in this list (not just Core):

 

 - DDSopt can be installed more or less anywhere and run all by itself;

 

 - Skyrim Performance Monitor should be

    - installed away from /Program Files/;

    - the initial .exe for running the game (at least when wanting SPM to be engaged at all), and directed at Mod Organizer as main program and launcher paths;

 

 - Mod Organizer should be

    - installed in its own folder under /common/Skyrim/;

    - run via Skyrim Performance Monitor (except when/if SPM is unwanted);

    - the primary 'gateway' to running the Skyrim launcher or the game itself;

 

 - TES5Edit and Wrye Bash should be

    - installed in their own folders under /common/Skyrim/;

    - run through Mod Organizer;

 

 - LOOT should be

    - installed wherever;

    - run through Wrye-Bash[-through-Mod-Organizer],

    - but only through MO when/if WB isn't necessary for an operation?

 

 

and if I have all/most of that correct, further down the line, is SKSE going to be starting the game [or launcher] via Mod Organizer?  my previous mod-up was pathetically simple and SKSE was meant to be in charge of either skyrim.exe or launcher.exe...

Share this post


Link to post
Share on other sites

6 answers to this question

Recommended Posts

  • 0

Mod Organizer: For convenience, yes installed in a sub-folder of Skyrim, or whatever game you're running. Although it can easily be installed anywhere.

It is also the only way to run your game as the installed mods exist only when MO has been run, which then informs Skyrim where to look and thus load them into the game. No MO to run your game == no mods.

 

xEdit (TES5Edit): As for MO so to for xEdit. It can be run from anywhere but it is easier if it is in a sub-folder. At least it is easier to provide support if all users have it installed the same way.

As for the game executable so to with all the tools that manipulate the mods. Unless run through MO they will not see them.

 

LOOT: There is no reason I can see why you would run LOOT via Wrye Bash via MO. Makes no sense to me. Just install these tools as executables in MO and they will all happily work together in the belief the mods they are seeing actually are in the system filetree instead of in MO's magic world!

 

SKSE: Definitely must be run from MO for all the above reasons. It should be automatically recognised by MO if you have installed it correctly.

 

In addition to reading through the STEP guide, there is also an in-depth MO wiki that you should look at.

  • Upvote 1

Share this post


Link to post
Share on other sites
  • 0

thanks, I am still soaking up the MO wiki bit by bit...

 

the bit about LOOT was because I had seen one instruction to add it to MO's executables (which makes perfect sense, as you indicate, but which I can't find at the moment), but in the Wrye Bash guide it says to run LOOT through WB...  so i figured since we're supposed to run WB through MO...


and they will all happily work together in the belief the mods they are seeing actually are in the system filetree instead of in MO's magic world!

i definitely appreciate the inherent :ninja: ness of the logistics!

Edited by junglejudas

Share this post


Link to post
Share on other sites
  • 0

I believe you'd run LOOT through WB if you were using Bash as your mod organizer of choice. Otherwise adding as an Exe to MO is totally the right idea.

  • Upvote 1

Share this post


Link to post
Share on other sites
  • 0

Actually I'm still unclear (and I realize that I still have the option of 'keeping it simple', but to hell with that ... for now) ...

 

  if one elects to use Wrye Bash "as a helper application to Mod Organizer exclusively for the functionality of the Bashed Patch" (quoth the main page), I'm worried that I'm overlooking (or searching in vain) for instructions on the configuration/interaction of MO's and WB's directories:

  does running WB via MO, and only for the bashed patch, mean there's no need for WB's own mod & bash install directories (i.e. that editing bash.ini is largely irrelevant)?  or does WB need to be pointed at MO's directory(s) instead of its own?  (or is that already worked out just by making it one of MO's executables in the first place?)

 

  or i may very well be overthinking the "STEP only supports MO as primary manager"; it just seems like there's an abundance of explanation for each manager alone, but no explicit clarifications/dismissals for using 'WB-under-MO' (other than to add WB to MO's executables)...

Edited by junglejudas

Share this post


Link to post
Share on other sites
  • 0

or perhaps this is putting it more succinctly:

 

are all WB instructions below 'BAIN Installers' either unnecessary or essential for someone who is using MO for as Chief Management Utility?  (i.e. does 'BAIN Installers' mean 'those who will be installing everything through WB rather than MO'?)

Share this post


Link to post
Share on other sites
  • 0

all right... finally got to the Wrye Bash section of the MO Guide, getting sidetracked by most of the other Notable Applications...

 

so it looks like we hook WB up to MO and then don't need to touch it until all the mods for a given profile are in.

 

now i have to look into my ddsopt anxieties...

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.