Automated STEP Installer - Now in Beta
Posted 21 November 2013 - 04:08 PM
You already are familiar with those programs as you wrote/ported them. Good luck and I hope you find the time. Please keep us informed.
Posted 21 November 2013 - 04:42 PM
Posted 21 November 2013 - 06:48 PM
1st my test configuration (hopefully easy to replicate):
ASI (Automated STEP Installer) Beta 1.0 from https://www.mediafir...32b9o9ivop1tg5a
C++ sourcecode): https://github.com/m.../master/Beta1.0
Config File (for steps "fixes" and "interface")
move the included "config" file into /source directory
all archives need to be placed in the program root dir (beside the STEPAutomatedInstaller.exe)
probably just a small bug for now?
I only used the interface mods: fast download, better overview (only 18 archives).
Better Dialogue Controls
Better MessageBox Controls
SKIPPED: Disease Descriptions
Dungeon Quest Awareness
High Quality 3D Map ---- download "BCF Available (Baseline)" direct link
Interface Key Tweaks ----- download "Normal Tweaks"
Lockpicking Interface ----- download ""v1.2 (Without wings)"
Lore-Based Loading Screens
Main Font Replacement ---- download "Fertigo Pro"
No Boring Wait Menu
No Menu & Loading Smoke
SKIPPED: Skill Interface
Not Another Colored Map Icon Mod ---- download the optional "NACMIM - Full" only
Smaller Cursor "Standard"
Spinning Skyrim Emblem "Average"
Time On Loading Screen
SKIPPED: Unknown Enchants
My download manager (firefox addon downthemall) renamed my files to *2.* e.g.
Better Dialogue Controls v1_2-27371-1-2.zip
Better Dialogue Controls v1_2-27371-1-22.zip
The tool did not recognize them and I had to rename them. Maybe s.th. like this would circumvent such cases:
Better Dialogue Controls v1_2-27371-1-2*.zip
But I'm not sure if thats really necessary at all...
some suggestions from my first glance:
-> make mutiple config files (one for each step)
that would probably be easier to maintain, keep track, test and bugfix. This way you could also delegate the workload to more people.
--> add comments in config file (eases the documentation)
e.g. simply ignore a line beginning with "#"
--> put a "debug" command in your code to check the result - e.g.:
dir Skyrim /a-d /b /s > debug.txt
(right before add everything in a 7zip)
That way everyone testing it can post it here if s.th. goes wrong.
Aaaand finally: YES! It seems to work for me :D
My final 7zip:
Posted 21 November 2013 - 06:55 PM
Posted 21 November 2013 - 07:28 PM
Posted 21 November 2013 - 07:51 PM
Posted 21 November 2013 - 09:33 PM
Posted 21 November 2013 - 10:13 PM
Posted 21 November 2013 - 10:19 PM
Posted 22 November 2013 - 09:30 AM
Changed my mind. I will simply follow the current concept:
- all possible mods and optionals will be used
- user has to take care of choosing the right ones for his setup
anyway, the current state:
(everything core only = the green ones)
2.D. Fixes - DONE -> testing
2.E. Interface - DONE -> testing
2.F. Conflicting Graphics - ~20% WIP (easy NMM-links first)
2.G. Landscape & Environment - ~20% WIP (easy NMM-links first)
2.H. Characters & Creatures - ~20% WIP (easy NMM-links first)
2.I. Clothing & Equipment - skipped
2.J. Animations & Effects - ~10% WIP (easy NMM-links first)
2.K. Clutter & Miscellaneous - ~10% WIP (easy NMM-links first)
2.L. Sound - ~10% WIP (easy NMM-links first)
2.M. Gameplay -~20% WIP (easy NMM-links first)
Currently I'm simply downloading the archives from nexus and document details (filenames etc.). This might come in handy later on (or for the wiki).
I start with the one-click download files and work my way up till it gets more complicated.
Posted 22 November 2013 - 01:49 PM
Posted 23 November 2013 - 02:27 AM
see also this thread
Any help with this would be highly appreciated
just some ideas flying through my head (pretty much build upon recent activity here)
still done by hand via Mod Organizer Browser - from what I can see the fastest way to download, right? (aside from the not viable autodownload)
You still need to click your way through to all necessary files though.
More user friendly STEP
idea for another STEP structure:
Modname - Modname file 1, Modname file 2
There could be several STEP lists that are tailored for dlcs(DG, DB, HF available?) and system power (baseline, lower, higher)
To keep maintanance low those lists will be generated from the up-to-date info in the wiki
Give the user a bit more choice
When you've got all files in one dir there are two ways to approach next:
1) Prepare for MO:
A small tool (a variant of AutomaticSTEPInstaller by mothergoose729 ? )
- will go through all files and extract them (each mod gets it's own subdir)
- will adjust the directory structure of the mods
- create new archives - one for each mod
- create a csv filelist of all archives (in correct installation order) for MO
Those updated archives will then be fed by MO.
Start the (experimental) batch installer in MO and your STEP is done.
2) Create one big STEP mod file
The AutomaticSTEPInstaller basically does his job:
- extract all files
- order them
- create the final archive
Use this archive as your (probably) one and only mod for Skyrim and you are ready to go!
This approach has several benefits:
- MO can still be used to add new mods between the ones suggested by STEP
- a new user doesn't have to get into the modding magic
- it keeps things pretty clean, simple and manageable (you will use one config file for AutomaticSTEPInstaller and the MO-Preparation tool)
While the general problem of maintenance still exists it might be possible to extract the config file from the wiki-data.
Posted 23 November 2013 - 04:19 PM
Posted 24 November 2013 - 07:35 AM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users