Closed airbreather closed 7 years ago
Hmm... a mostly sequential XML file that just did these things would actually cut out like 80% of the work from a hypothetical AutoIt / AutoHotkey script, and even some of the overall work too:
Honestly, the only scary parts of this are the things marked AHK, and it also happens to be the simplest stuff I can imagine automation tools doing: launch a process with these arguments and "click" these controls once the appropriate window pops up.
Directly launching the Mod Organizer application itself would be a little bit spooky because of the non-deterministic messages, but we could INI-tweak those away if we needed to... and we don't need to in the first place because we just rewrite the internal data ourselves.
After installing STEP Extended through the automated tool but before running it, in order to have a complete and correct setup, the user still has to do all these things:
A significant fraction of these steps (everything except 11-17, 24, and 34) apply to STEP Core as well, though you can probably get away with skipping DynDOLOD setup if you don't tell anyone.
That's a lot of things. Too many things, in my opinion. If we can automate it "behind-the-scenes" without all that clicking around through the applications, then that's the best thing possible, but if not, then it's still reasonable to allow a "pack" to run an AutoIt / AutoHotKey script that goes through everything so that the user can idle their way to a complete setup.
At the very least, we should provide an AutoIt / AutoHotKey script that the user can run themselves so that they're not left completely hanging. That list is way too many steps, even for STEP Core, and it's way too easy to screw it up.