7 replies to this topic

[Turambar]

As I'm re-writing the biffing at the end of SoS, I'm trying to prevent some resources such as ITM, SPL, STOs from being biffed if the installation is a BWP installation.
I need to use an ACTION_IF for that; could you tell me a good condition to identify the fact that the mod is being installed by BWP, or a file that is only related to BWP, whose existance I can use for that purpose?

[dabus]

BiG World Install.bat?

[Turambar]

BiG World Install.bat?

ok, I could use that... But still, it could also exist if, for some reason, you are installing by hand a mod, having downloaded (but not using) BWP. Otherwise, are there any temporary files which are created by the .bat when the installation starts and removed after the last mod is installed?
I think a file such as running.bwp would be a good way to see if a BWP installation is currently running, and not just if its files exist. For example, you could add a command "copy [any file] running.bwp" at the very beginning of the .bat, and "del running.bwp" as last command

edit: moreover, BIG world install.bat has spaces in its name; I'm not sure it doesn't create problems when I'm checking for its existance

Edited by Turambar, 23 January 2011 - 06:00 AM.

[the bigg]

The only time where biffing ITM and the like is NOT a bad idea is when the only mod you're installing is SoS (and, even then, the benefits are dubious at best). As such, you might as well never biff ITM files.

[Turambar]

The only time where biffing ITM and the like is NOT a bad idea is when the only mod you're installing is SoS (and, even then, the benefits are dubious at best). As such, you might as well never biff ITM files.

On linux, from what I know and have seen, having files in the override folder causes much worse lags than in windows, and if someone only installs SoS, biffing is important.
Anyway, I could ask the user if he wants to biff everything (not recommended unless it's the last mod) or to wait for general biffing. So, my idea was to only prompt the user if they are installing manually from setup-sos, or if they are re-installing previous mods, but I'd need to know a way to do it.
A thing I could use is, is the BW installation %interactive%?

[Jarno Mikkola]

On linux, from what I know and have seen, having files in the override folder causes much worse lags than in windows, and if someone only installs SoS, biffing is important.
Anyway, I could ask the user if he wants to biff everything (not recommended unless it's the last mod) or to wait for general biffing. So, my idea was to only prompt the user if they are installing manually from setup-sos, or if they are re-installing previous mods, but I'd need to know a way to do it.
A thing I could use is, is the BW installation %interactive%?

Or you could just add a component that does the biffing, in which case the BWS wouldn't ever run the thing, but the manual installer(the player) might.

[Turambar]

Or you could just add a component that does the biffing, in which case the BWS wouldn't ever run the thing, but the manual installer(the player) might.

Good idea, thanks! FORCED_SUBCOMPONENT could work, so you can chose between moving to override and biffing (and BWP can just install the former).
Would AT_EXIT instructions from the main component be performed after the installation of the FORCED_SUBCOMPONENTs?
For example:

BEGIN main
//install mod
AT_EXIT ~instructions~
//install mod
BEGIN ~biff~
FORCED_SUBCOMPONENT ~chose~
//biff
BEGIN ~nobiff~
F_S ~chose~
//move to override

Are the ~instructions~ performed after either ~biff~ or ~nobiff~ have been installed?

Edited by Turambar, 23 January 2011 - 07:09 AM.

[Jarno Mikkola]

Would AT_EXIT instructions from the main component be performed after the installation of the FORCED_SUBCOMPONENTs?
For example:

BEGIN main
//install mod
AT_EXIT ~instructions~
//install mod
BEGIN ~biff~
FORCED_SUBCOMPONENT ~chose~
//biff
BEGIN ~nobiff~
F_S ~chose~
//move to override

Are the ~instructions~ performed after either ~biff~ or ~nobiff~ have been installed?

Erhm, I was thinking more along the lines of:

BEGIN main
//Where all the things have this:
COPY ~x~ ~override~
//And then:
BEGIN ~Biffing~
...

And that's it. See the BWS would only install the first component where the manual installers can either go and choose to install all, or just one of the components, as then there is no subcomponents needed... just like the kits in this mod.