Jump to content

BSL:AI activity: Difference between revisions

using template for table header
(use of tables looks better if each row of commands is its own table; added subheaders; moved ai2_idle to "AI tasks")
(using template for table header)
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
Commands for controlling the activity of AIs.
Commands for controlling the activity of AIs.
 
{{TOCfloat}}
{| class="wikitable"
{| {{BSL Group Table Header}}<onlyinclude>{{BSL Group Table|{{PAGENAME}}}}</onlyinclude>
!Group
!Kind
!Type
!Name
!Platform<onlyinclude>{{BSL Group Table|{{PAGENAME}}}}</onlyinclude>
|}
|}


Line 40: Line 35:
|}
|}


When these functions are passed "true" or a non-zero number for "passive", the specified AI (or all AIs, with '''ai2_allpassive''') will stop all "intelligent" activity (melee, gunfights, pursuit), but passive AIs will still patrol. Since the default value for "passive" is 0, you don't need to pass anything for that argument to make an AI active again; i.e., '''ai2_allpassive()''' makes all AIs active. '''chr_freeze''' and '''chr_neutral''' are simply aliases for '''ai2_passive'''.
Passive is not the opposite of active (see above). Even when passive, an AI can still be active. However, when these functions are passed "true" for "passive", the specified AI (or all AIs, with '''ai2_allpassive''') will stop all "intelligent" activity (melee, gunfights, pursuit), but passive AIs will still patrol. Since the default value for "passive" is 0, you don't need to pass anything for that argument to make an AI non-passive again; i.e., "ai2_allpassive();" turns off passiveness for all AIs. '''chr_freeze''' and '''chr_neutral''' are simply aliases for '''ai2_passive'''.


==Alert status==
==Alert status==