Insurgency
| Part of: | |||
|---|---|---|---|
| |||
| Requirements: | Synced | ||
|
| ||
-
Note: module is work in progress...
How It Works
Work in progres...
Usage: place the Military Insurgency module in the editor, select the desired Size, Weighting and Faction from the drop down.
- Force Faction BIS standard or custom factions can be entered in the text box. Custom units need to have groups properly configured for them to work with ALiVE. See here for a list of factions that are known to work with ALiVE. You can also manually map the faction groups if the configs are incorrectly defined. See Declaring Faction Mappings for further info.
- Objective Filters provide options to restrict objective clusters by size or relative importance, so for example it is possible to identify only large military bases and airfields as objectives, excluding smaller bunkers and watchtowers.
- Place Units defines whether the module will spawn units or only create empty objectives.
TAOR & Objective Blacklists
Tactical Areas Of Responsibility are a fundamental feature. They represent a zone or boundary area for which the military commander is responsible. This does not mean the commander will never leave that zone to attack nearby opposition but his primary objectives will be inside the defined TAOR.
To restrict objectives to a user-defined TAOR, place a named area marker covering the chosen area and add it to the appropriate TAOR box in the module params. A good convention is to use the format TAOR_Faction_xx (e.g. TAOR_BLUE_1). Multiple areas can be listed separated by commas e.g. TAOR1, TAOR 2, TAORxx.
Blacklisted areas will be ignored and can be defined using area markers with the name specified in the module params, for example BL_Faction_xx (e.g. BL_R_1). If TAOR and BL area markers overlap, Blacklist always takes precedence.
