I agree, that the SMC as it is now, might not be totally S.T.E.P compatible, but the idea behind it could possibly make semi-automation of STEP reality. It is much easier for user to just download all the mods trhat are part of S.T.E.P and run an automated process, that would combine them in one installation file, in the intended order. I'm not sure if the TES5Edit -steps could be automated also at it's current version, but I do think that with co-operation, batch projects could be implemented in TES5Edit and updated with ease within a single .BAT file on STEP wiki, as the project evolves. The installation order and automatically removed files can be easily kept up to date with the latest S.T.E.P specifications, as the same kind of installation order list can be used for both, the automation process and the S.T.E.P instruction wiki. Also making a switch in the combiner program, to determine if the user wants to combine a HQ or the LQ version, would be possible. A smart switch within the program could determine, that when the HQ option is enbaled, but some HQ packages are missing, LQ versions could be used instead, which adds flexibility for people, who might not be able to run the HQ version of STEP. Basic functionality for a simple version of this kind of combiner could be something like this; -Examine the original mod packages and extract the required folders and files into a unified folder structure. Some mods might not have the \Data folder at the root of the package, so the program needs to be able to look for the \Data folder from within the packages file strtucture. -Only extract files that are required by the STEP configuration, exactly in the required order. -OPTIONALLY, STEP could be updated with an updated FOMOD, that could be inserted in the combined mod package, with which the proper installation order could be managed. Keeping the mods up to date coudl also be handled in a following manner; -Make different profiles for the STEP mod list and the combined STEP mods. For example, the list that is meant to keep the mods updated could be called "STEP Mod List" and the STEP installation profile could be called "STEP Installation". -STEP Mod Combiner -program keeps a list of all the extracted files - what files belong to what mod and what mods overwrite which mod's files, so the Combiner can keep track of every file's installation order, that it extracts and the final order/structure of the combined mods. -STEP mod combiner could this way have an option to update single mods within this large package, so updating the combined mod package wouldn't take too much time. For example, the program checks from the MO's downloaded mods folder, what mods has two different versions and compares the newer one with the older one. After this, the program determines if other mods down the installation order overwrite some of the updated files and only copies the new files, that are not being overwritten by any mod, that is later installed in the list. -OPTIONALLY the STEP mod combiner could delete the older version of the mod after combining, if the user so chooses. Taking into account, that this automated process installs only the files that STEP specifications recommend, it can take less time or at least simplify the process of installing STEP precisely as intended, without requireing the user to read further instructions mod by mod basis from the STEP installation instructions. This kind of software could be coded with quite much any programming language, easiest of which might be python and/or java/C Sharp. The basic structure of how this can be done is simple, but the actual coding part could be tricky - which I don't know anything about. Which is why this is only intended as brainstorming about the required processes that the automated combiner would need. I must stress, that this is only a simplified explanation of what the program must be able to do, to achieve the kind of usability and flexibility in order to not need too heavy micro managing from the STEP community.
