Franz-Inc
commented
10 months ago I think I solved my use case by adapting one of your _on_utility_ai_agent_behaviour_changed(behaviour_node): examples and using .get_parent(). Basically, I assess if a group has changed everytime the behaviour changes by comparing .get_parent() of old and new behaviour, and if its new, I run an end/start behaviour_group scripts that are loaded on each behaviour group.
func _on_utility_ai_agent_behaviour_changed(behaviour_node):
var new_group: bool = false
if current_behaviour != null && behaviour_node != null:
#current_behaviour.end_behaviour(self) -- not needed yet
if behaviour_node.get_parent() != current_behaviour.get_parent():
new_group = true
current_behaviour.get_parent().end_behaviour_group(self)
else:
new_group = true
current_behaviour = behaviour_node
if current_behaviour != null:
my_behaviour_label.text = current_behaviour.name
if new_group:
current_behaviour.get_parent().start_behaviour_group(self)
#current_behaviour.start_behaviour(self) -- not needed yet
else:
my_behaviour_label.text = "No behaviour!"
JarkkoPar
It might be useful to have signals for On_Behaviour_Group_Changed as well (or on action_group etc). I am using Behaviour Groups to organize my actions, and have been grouping them into States of Awareness of sorts. Similar to your vision and hearing Baddie example, my enemy will see the player and go into a Combat Behaviour Group. Once he looses sight of the player, he will revert to a Searching Group, triggering a Search Timer. However, I would like the flexibility for this timer to start once the Searching Group is entered, rather than when he looses sight (as there may be other reasons for the Behaviour groups to change). Also, if I start the timer when he 'looses sight', this doesn't take into account any delay due to the thinking_delay_in_seconds parameter (since the timer would start immediately, but the actual behavioural switch would occur after x seconds)