Difference between revisions of "Custom Blacklists"

Revision as of 19:11, 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.

Heres an example from the AS Alamo mission on the website to load and apply your own custom settings

init.sqf

if(isServer) then {
 
	// -------------------------------------------------------------------------------------------------------------
	// override default data 
	// see script/staticData.sqf
	["MISSION INIT - Waiting"] call ALIVE_fnc_dump;
 
	waitUntil {!isNil "ALIVE_profileSystemDataLoaded"};
 
	["MISSION INIT - Continue"] call ALIVE_fnc_dump;
 
	// override static data settings
	call compile (preprocessFileLineNumbers "script\staticData.sqf");
 
	["MISSION INIT - Static data override loaded"] call ALIVE_fnc_dump;
	["CUSTOM BLACKLIST LOADED: %1",ALIVE_unitBlackist] call ALIVE_fnc_dump;
 
	// -------------------------------------------------------------------------------------------------------------
};