19,580
edits
BSL:AI activity: Difference between revisions
centering and titling command table; forcing TOC on to try to fill more of that upper space; fixing phrasing of "Passive" section
(we can do away with the Group column on grouped pages and still have it on BSL:List) |
(centering and titling command table; forcing TOC on to try to fill more of that upper space; fixing phrasing of "Passive" section) |
||
| Line 1: | Line 1: | ||
Commands for controlling the activity of AIs. | Commands for controlling the activity of AIs. | ||
{{TOCfloat}} | |||
{| class="wikitable" | {| class="wikitable" style="margin-left:auto; margin-right:auto;" | ||
|+Contents | |||
!Kind | !Kind | ||
!Type | !Type | ||
| Line 39: | Line 40: | ||
|} | |} | ||
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== | ||