Difference between revisions of "Custom Blacklists"

From ALiVE Wiki
Jump to: navigation, search
(Created page with "The ALiVE modules have blacklists of units, groups and buildings stored in sys_profile. The mission editor and script is able to define which units get blacklisted or blacklis...")
 
Line 8: Line 8:
  
 
The arrays are the following, the functions speak for themselves.
 
The arrays are the following, the functions speak for themselves.
*ALIVE_CQBunitBlackist
+
*'''ALIVE_CQBunitBlackist'''
*ALIVE_unitBlackist
+
*'''ALIVE_unitBlackist'''
*ALIVE_vehicleBlacklist
+
*'''ALIVE_vehicleBlacklist'''
*ALIVE_groupBlacklist
+
*'''ALIVE_groupBlacklist'''
  
 
The elements that have to be used are the classes as defined in the configFile.
 
The elements that have to be used are the classes as defined in the configFile.
 +
 +
To add buildings for the CQB manager to consider, add elements to '''ALIVE_CQBStrategicTypes'''.

Revision as of 19:04, 24 February 2014

The ALiVE modules have blacklists of units, groups and buildings stored in sys_profile. The mission editor and script is able to define which units get blacklisted or blacklisted on top of the current blacklists.

To add elements to an array use the method described in the biki.

_array1 = [player, 7, "String"]
_array2 = [player, 2]
_array3 = _array1 + _array2


The arrays are the following, the functions speak for themselves.

  • ALIVE_CQBunitBlackist
  • ALIVE_unitBlackist
  • ALIVE_vehicleBlacklist
  • ALIVE_groupBlacklist

The elements that have to be used are the classes as defined in the configFile.

To add buildings for the CQB manager to consider, add elements to ALIVE_CQBStrategicTypes.