That could be it, but based on the context my guess is that this task returns a status of running so it doesn't need a repeater to have it call OnUpdate again.Don't you need a repeater task if you use the OnUpdate method? You have a repeater on your right side but not on your left side.
But I haven't used BD in a long time and maybe he changed the way that works, so I could be wrong.
[TaskDescription("Changes the movement goal/strategy set of the agent")]
[TaskCategory("Resonance/Test")]
public class TestAction : Action
{
public override TaskStatus OnUpdate()
{
Debug.Log("Running");
return TaskStatus.Running;
}
}
[edit]No I see OnReset isn't used like that. I overrode OnBehaviorRestart and reset variables which might be of concern but it didn't help anything.Wait.. could it be that I don't set finished to false in OnReset? Does state persist between playthroughs in the tasks?
So what is the difference between the stripped down existing task and the new task that you tried which just returned the status of running? If you enable logging on the behavior tree you'll be able to see a text representation of what the behavior is trying to do.I stripped my task down to nothing but the update method returning "running" and it still hangs in the same fashion
OnReset is only called by the editor so I don't think so.Wait.. could it be that I don't set finished to false in OnReset? Does state persist between playthroughs in the tasks?