Jump to content

BSL:AI activity: Difference between revisions

m
groups of commands need to be put in an ad-hoc table if you want to place them side by side so that they don't take up a bunch of vertical space
m (link fix)
m (groups of commands need to be put in an ad-hoc table if you want to place them side by side so that they don't take up a bunch of vertical space)
Line 9: Line 9:
|}
|}


{{:ai2_active}} {{:ai2_inactive}}
{|
 
|-
{{:chr_all_active}} {{:chr_draw_all_characters}} {{:chr_disable_visactive}}
|{{:ai2_active}}
 
|{{:ai2_inactive}}
{{:chr_lock_active}} {{:chr_unlock_active}}
|-
 
|{{:chr_all_active}}
|{{:chr_draw_all_characters}}
|{{:chr_disable_visactive}}
|-
|{{:chr_lock_active}}
|{{:chr_unlock_active}}
|}
Active characters are ones that can be collided with, attacked, etc. An active character can be passive or not passive (see next commands). It is normal for characters to become inactive when they have not been drawn (i.e., have not been on-screen) for a while. Thus, using '''chr_all_active''' or '''chr_draw_all_characters''' to force all characters to be evaluated as active is an unusual measure that is not to be taken lightly. Those two variables might in fact only have been useful for Oni's developers. Set '''chr_disable_visactive''' to true to avoid making characters active simply because they are being drawn. '''chr_lock_active''' obviously prevents a character from automatically going inactive, and '''chr_unlock_active''' removes the lock.
Active characters are ones that can be collided with, attacked, etc. An active character can be passive or not passive (see next commands). It is normal for characters to become inactive when they have not been drawn (i.e., have not been on-screen) for a while. Thus, using '''chr_all_active''' or '''chr_draw_all_characters''' to force all characters to be evaluated as active is an unusual measure that is not to be taken lightly. Those two variables might in fact only have been useful for Oni's developers. Set '''chr_disable_visactive''' to true to avoid making characters active simply because they are being drawn. '''chr_lock_active''' obviously prevents a character from automatically going inactive, and '''chr_unlock_active''' removes the lock.


 
{|
{{:ai2_allpassive}}
|-
 
|{{:ai2_allpassive}}
{{:ai2_passive}} {{:chr_freeze}} {{:chr_neutral}}
|{{:ai2_passive}}
|-
|{{:chr_freeze}}
|{{:chr_neutral}}
|}


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'''.
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'''.