Could use some help making the new HSFX 4.1 into what I want
#2

There's a way to turn off the carrier mod on a mission-by-mission basis, by including a line in the [MODS] section of the .mis file.

Fireball Wrote:If you don't want the AI to use the catapult in a particular mission, you can add a [Mods] section to the end of the .mis file (if you don't already have a [Mods] section), and set the CatapultAllowAI parameter equal to 0. It would look like so:

[Mods]
CatapultAllowAI 0

If you don't want the AI to use the catapult in ANY missions, you can add the [Mods] section to the end of your conf.ini file (if you don't already have a [Mods] section), and set the CatapultAllowAI parameter equal to 0. That way you don't have to add it to each mission file. It would look like so:

[Mods]
CatapultAllowAI=0

Notice a slightly different format between the two. In the .mis file the parameter name and value are separated by one or more spaces. In the conf.ini file they're separated by an equal sign (=). Be sure to make a backup of your conf.ini before trying to make any changes.

The README file for the Carrier Takeoff mod explains all the different optional parameters that can go in the [Mods] sections.

Fireball

HSFX 4.1 includes the persistent .mis [MODS] section mod, so you only have to do this once for each .mis file.
Reply


Messages In This Thread

Forum Jump:


Users browsing this thread: 1 Guest(s)