mirror of
https://github.com/ParadiseSS13/Paradise.git
synced 2026-08-20 10:37:17 +01:00
efc8adb6dd
* Basic mobs targeting, attacks, and pig migration. * run updatepaths * fix duplicate macro def * Update code/datums/ai/basic_mobs/basic_ai_behaviors/basic_attacking.dm Co-authored-by: Burzah <116982774+Burzah@users.noreply.github.com> Signed-off-by: warriorstar-orion <orion@snowfrost.garden> --------- Signed-off-by: warriorstar-orion <orion@snowfrost.garden> Co-authored-by: Burzah <116982774+Burzah@users.noreply.github.com>
21 lines
1.2 KiB
Plaintext
21 lines
1.2 KiB
Plaintext
/// A subtree is attached to a controller and is occasionally called by
|
|
/// /ai_controller/select_behaviors(). This mainly exists to act as a way to
|
|
/// subtype and modify select_behaviors() without needing to subtype the AI
|
|
/// controller itself.
|
|
/datum/ai_planning_subtree
|
|
/// A list of typepaths of "operational datums" (elements/components) we
|
|
/// absolutely NEED to run. Checked in unit tests, as well as be a nice
|
|
/// reminder to developers that such a thing might be needed. Note that in
|
|
/// the Attach/Inititalize/New (or any future equivalent for these procs),
|
|
/// you will need to add the trait TRAIT_SUBTREE_REQUIRED_OPERATIONAL_DATUM
|
|
/// to the mob in question in order for unit tests to succeed. This will
|
|
/// break obviously enough if you don't do this and declare the required
|
|
/// datum here however.
|
|
var/list/operational_datums = null
|
|
|
|
/// Determines what behaviors should the controller try processing; if this
|
|
/// returns SUBTREE_RETURN_FINISH_PLANNING then the controller won't go through
|
|
/// the other subtrees should multiple exist in the controller.
|
|
/datum/ai_planning_subtree/proc/select_behaviors(datum/ai_controller/controller, seconds_per_tick)
|
|
return
|