Unattended installation of specific components from a mod

[forbjok]

Is it somehow possible to make WeiDU perform an unattended installation of a pre-configured set of components from a mod?
For instance, install only some components of BG2 tweak pack, ignoring the rest, based on a premade configuration of some sort, without having to manually specify what to do with each component.

[Mike1072]

From the command-line or .bat:

Code: [Select]

setup-modname.exe --language 0 --skip-at-view --force-install-list 0 1 5 8 9
This installs components 0, 1, 5, 8, and 9 in the first language translation (usually English) and doesn't display the readme.

You can use --force-uninstall-list 1 5 9 to uninstall some selection of components, or --uninstall to remove all components of a mod.

[forbjok]

Are those component numbers unique IDs that will remain the same within the same mod (assuming the author doesn't change it, of couse) across versions, or are they simply an incremental ID based on the component's position in the install script?

[the bigg]

They're generally incremental, but the author can optionally manually specify an identifier.

[forbjok]

Nice
They are the "#component_number" from WeiDU.log then?

Another thing though... in the BGT installer, it asks for the path to BG1.
Is it possible to specify that through the commandline as well?

[the bigg]

You can also get the component numbers via weidu --list-components mymod.tp2 0 (where 0 is the language #, obteinable via weidu --list-languages mymod.tp2).

You can specify the BG1 directory (and Widescreen resolution, etc.) via pipes: echo "C:\path\to\bg1" | setup-bgt.exe ... if it's a single line, or write the contents to a input.txt and then use type input.txt | setup-widescreen.exe ... . See also the install.bat from the Big World Setup for examples.

[Miloch]

If you don't want to spend your life hacking batch files (or reinventing the wheel), try the Big World Setup which will do that for you.

[the bigg]

Wait, BWS has been able to do components for the last six months and has never been integrated in the BWP proper?

[Miloch]

I don't know when exactly dabus added component-picking, but it worked just fine on my last install a month or so ago. Didn't have to touch a single batch file.

[anon]

Sorry for the thread necromancy, but this is so relevant to my question it makes more sense to continue the discussion than start a new one.

How exactly do I

...write the contents to a input.txt and then use type input.txt | setup-widescreen.exe ...

I've looked at the bigworld install batch file and i follow most of it, but I don't see a clear use of this syntax. From the quote above, I don't see how to write multiple input options to a single file (assuming each row is a unique set of inputs for a given mod?) and then call the correct row via pipes to provide the input to weidu.

For example; say I've got input.txt with 3 rows, covering the romance cheat options for bg2 tweak pack, [a b a a], some entries for lvl 1 npcs, and my widescreen resolution.

a b a a
0 12 2 2 2
1400 900

and my corresponding .bat for installing said mods is

SETUP-BG2_TWEAKS.exe --language 0 --force-install-list 3183 [romance cheat]  --skip-at-view
setup-level1npcs.exe --language 0 --force-install-list 0 1207 [jaheria] --skip-at-view
SETUP-WIDESCREEN.exe --language 0 --force-install-list 0 --skip-at-view

Do I edit my batch file and use some sort of array index notation to specify the row from input.txt?

Code: [Select]

input.txt(1) | SETUP-BG2_TWEAKS.exe --language 0 --force-install-list 3183 [romance cheat]  --skip-at-view
input.txt(2) | setup-level1npcs.exe --language 0  --force-install-list 0 1207 --skip-at-view
input.txt(3) | SETUP-WIDESCREEN.exe --language 0 --force-install-list 0 --skip-at-view

I have my own custom .bat that is _almost_ unattended, but there are about 5 mods that make me monitor it to give input and I know I can get around it, since BWP handles it somehow. Not to mention, automating lvl1npc would be _really_ nice.

[Jarno Mikkola]

You put the inputs for each setup....exe's to different files, and different inputs to different lines, so the above would be:

a
b
a
a

0
12
2
2
2

1400
900

Code: [Select]

input1.txt | SETUP-BG2_TWEAKS.exe --language 0 --force-install-list 3183 --skip-at-view
input2.txt | setup-level1npcs.exe --language 0 --force-install-list 0 1207 --skip-at-view
input3.txt | SETUP-WIDESCREEN.exe --language 0 --force-install-list 0 --skip-at-view