*core mods only (the one marked green in the step guide)
*all possible core mod files will be indexed
*always follow STEP guide exactly!
*follow the main STEP guide till STEP 2.D
*baseline only (no low or high)
*choose "recommended" where stated
*all DLCs are required
STEP:Core Mods - list of filenames
A list of the downloaded files, necessary for a STEP Core install:
(currently only fixes, interface, graphics)
a new spreadsheet up with more meta-infos: https://docs.google....YlE&usp=sharing
For testing purposes, we need to define a precise setup instruction for the STEP installation we want to achieve.
(can't seem to stress that enough :D)
The current state of the available "Semi-Automatic STEP"-tools is pre-alpha! There isn't any working installer yet (altough mothergoose729 did some great work getting there).
As we are in a proof of concept phase, we just need to decide on some packages what options we choose for a first scripted test-install with no user interaction at all.
The current plan (proof of concept)
Create a one-click script that installs all STEP Core mods. We concentrate on a baseline install and assume the test user has all DLCs. Later there'll be options/profiles for high/low/vanilla installs - just not for our first scripting draft.
That'll simplify things a lot development wise (easier to reach goals). I think adressing too much problems at once doesn't help. We need to set small goals in order to some progress. So basic install support first, options later.
The Core definition we need to make are just done via "rule of thumb" yet. Final decisions on what options a full one-click installer should pick will be made in the relevant mod threads (early dev stage, so no rush here!). We are still assembling a list of all mods that need attention for this - any help with this is highly appreciated of course :)!
And if the STEP team will get to a consensus on the options I will change the script accordingly of course. But then again getting SOMETHING done has a much higher priority than such decisions imho for now! While giving the user the most basic choises (quality setting and DLC support) neither in the design philosophy of a semi-auto installer nor realistic in terms of programming effort (at least for the next months).
Some tools might come in handy in terms of extended package management for STEP 2.3+, but no promises yet ;)
If there are choices in a mod setup please post them here.
We will discuss which option we use (if there isn't already any preference mentioned STEP guide).
For our first proof of concept we'll go with an "easier" option that won't put any unnessesary stones in the way.
reminder: stay cool, this is for testing porpuses only. Things will certainly change along the road.
personal comment: I have a good feeling that we can pull this off. No way can I guarantee some full fledged installer! I'm actually quite happy if anything constructive comes out of this. My hopes are that we'll get the basic tools done so others can build upon that.
STEP:Core Mods that need clarification for POC ASI:
* I'll be adding to the list as I get to them. ~Tech
installer details (MilesTeg):
- We will just add ALL main-options available where there is still no exact recommendation. e.g. DeadBody fix gets both: spell and no-spell-version.
- Nitpick will be included for WryeBash etc. compatibility
- the current list of files (see spreadsheet) uses the wiki and MO for meta information.
- current file order: 1st sort by name, 2nd sort by nexus fileID, 3rd sort by STEP mod-order