ai_controller

Vars
ai_movement	Reference to the movement datum we use. Is a type on initialize but becomes a ref afterwards.
ai_status	Current status of AI (OFF/ON)
ai_traits	Bitfield of traits for this AI to handle extra behavior
behavior_args	Stored arguments for behaviors given during their initial creation
behavior_cooldowns	Current actions and their respective last time ran as an assoc list.
blackboard	This is a list of variables the AI uses and can be mutated by actions. When an action is performed you pass this list and any relevant keys for the variables it can mutate.
continue_processing_when_client	Can the AI remain in control if there is a client?
current_behaviors	Current actions being performed by the AI.
current_movement_target	Current movement target of the AI, generally set by decision making.
failed_planning_cooldown	Cooldown for new plans, to prevent AI from going nuts if it can't think of new plans and looping on end
idle_behavior	The idle behavior this AI performs when it has no actions.
max_target_distance	distance to give up on target
movement_cooldown	Cooldown until next movement
movement_delay	Delay between movements. This is on the controller so we can keep the movement datum singleton
pathing_attempts	Tracks recent pathing attempts, if we fail too many in a row we fail our current plans.
paused_until	AI paused time
pawn	The atom this controller is controlling
planning_subtrees	All subtrees this AI has available, will run them in order, so make sure they're in the order you want them to run. On initialization of this type, it will start as a typepath(s) and get converted to references of ai_subtrees found in SSai_controllers when init_subtrees() is called
Procs
PossessPawn	Proc to move from one pawn to another, this will destroy the target's existing controller.
SelectBehaviors	Are we close enough to engage? This is where you decide what actions are taken by the AI.
TryPossessPawn	Abstract proc for initializing the pawn to the new controller
UnpossessPawn	Proc for deinitializing the pawn to the old controller
able_to_run	Returns TRUE if the ai controller can actually run at the moment.
change_ai_movement_type	Overrides the current ai_movement of this controller with a new one
get_access	Use this proc to define how your controller defines what access the pawn has for the sake of pathfinding, likely pointing to whatever ID slot is relevant
get_minimum_distance	Returns the minimum required distance to preform one of our current behaviors. Honestly this should just be cached or something but fuck you
init_subtrees	Loops over the subtrees in planning_subtrees and looks at the ai_controllers to grab a reference, ENSURE planning_subtrees ARE TYPEPATHS AND NOT INSTANCES/REFERENCES BEFORE EXECUTING THIS
process	Runs any actions that are currently running
queue_behavior	Call this to add a behavior to the stack.
replace_planning_subtrees	Completely replaces the planning_subtrees with a new set based on argument provided, list provided must contain specifically typepaths
set_ai_status	This proc handles changing ai status, and starts/stops processing if required.

Var Details

var
ai_movement
– /datum/ai_movement

Reference to the movement datum we use. Is a type on initialize but becomes a ref afterwards.

var
ai_status
–

Current status of AI (OFF/ON)

var
ai_traits
–

Bitfield of traits for this AI to handle extra behavior

var
behavior_args
– /list

Stored arguments for behaviors given during their initial creation

var
behavior_cooldowns
– /list

Current actions and their respective last time ran as an assoc list.

var
blackboard
– /list

This is a list of variables the AI uses and can be mutated by actions. When an action is performed you pass this list and any relevant keys for the variables it can mutate.

var
continue_processing_when_client
–

Can the AI remain in control if there is a client?

var
current_behaviors
– /list

Current actions being performed by the AI.

var
current_movement_target
– /atom

Current movement target of the AI, generally set by decision making.

var
failed_planning_cooldown
–

Cooldown for new plans, to prevent AI from going nuts if it can't think of new plans and looping on end

var
idle_behavior
– /datum/idle_behavior

The idle behavior this AI performs when it has no actions.

var
max_target_distance
–

distance to give up on target

var
movement_cooldown
–

Cooldown until next movement

var
movement_delay
–

Delay between movements. This is on the controller so we can keep the movement datum singleton

var
pathing_attempts
–

Tracks recent pathing attempts, if we fail too many in a row we fail our current plans.

var
paused_until
–

AI paused time

var
pawn
– /atom

The atom this controller is controlling

var
planning_subtrees
– /list

All subtrees this AI has available, will run them in order, so make sure they're in the order you want them to run. On initialization of this type, it will start as a typepath(s) and get converted to references of ai_subtrees found in SSai_controllers when init_subtrees() is called

Proc Details

proc
PossessPawn
(/atom/new_pawn)

Proc to move from one pawn to another, this will destroy the target's existing controller.

proc
SelectBehaviors
(delta_time)

Are we close enough to engage? This is where you decide what actions are taken by the AI.

proc
TryPossessPawn
(/atom/new_pawn)

Abstract proc for initializing the pawn to the new controller

proc
UnpossessPawn
(destroy)

Proc for deinitializing the pawn to the old controller

proc
able_to_run
()

Returns TRUE if the ai controller can actually run at the moment.

proc
change_ai_movement_type
(/datum/ai_movement/new_movement)

Overrides the current ai_movement of this controller with a new one

proc
get_access
()

Use this proc to define how your controller defines what access the pawn has for the sake of pathfinding, likely pointing to whatever ID slot is relevant

proc
get_minimum_distance
()

Returns the minimum required distance to preform one of our current behaviors. Honestly this should just be cached or something but fuck you

proc
init_subtrees
()

Loops over the subtrees in planning_subtrees and looks at the ai_controllers to grab a reference, ENSURE planning_subtrees ARE TYPEPATHS AND NOT INSTANCES/REFERENCES BEFORE EXECUTING THIS

↑
process
(delta_time)

Runs any actions that are currently running

proc
queue_behavior
(behavior_type, ...)

Call this to add a behavior to the stack.

proc
replace_planning_subtrees
(/list/typepaths_of_new_subtrees)

Completely replaces the planning_subtrees with a new set based on argument provided, list provided must contain specifically typepaths

proc
set_ai_status
(new_ai_status)

This proc handles changing ai status, and starts/stops processing if required.

ai_controller /datum/ai_controller

Vars

Procs

Var Details

var ai_movement – /datum/ai_movement

var ai_status –

var ai_traits –

var behavior_args – /list

var behavior_cooldowns – /list

var blackboard – /list

var continue_processing_when_client –

var current_behaviors – /list

var current_movement_target – /atom

var failed_planning_cooldown –

var idle_behavior – /datum/idle_behavior

var max_target_distance –

var movement_cooldown –

var movement_delay –

var pathing_attempts –

var paused_until –

var pawn – /atom

var planning_subtrees – /list