Runtime: Selector / Sequencer / Parallel nodes now actively tick all children rather than ticking from the previous child.

[AtmoMH]

Hi,

This seems odd as now the wait node doesn't work and a tree like

However, I may be very wrong and not understand what is going on!

The Sequencer ticks all it's child nodes at once; updating each update where they are meant to run in Sequence. Not sure I get this. I am a newbie however..! It seems like a parallel node now and doesn't do each child in turn.

[JuicyJugglesReturns]

I found here in the changelog that it states these changes are made so you are correct about the changes: b1b5296

What I don't understand is why these changes were made, it breaks all comparability to versions before this. Seems like it really should have been a new node vs changing current things.

[grzes]

I know this project isn't actively maintained, but I still like and use it and run into other people using it, so for reference:

I "fixed" the above issue in the Sequencer, making it tick from the last completed step. BUT, just today I've run into an opposing bug, where I now need a sequence to restart instead.

So it turns out these are actually different types of sequences, here's a cpp bt library which differentiates 3 types:
https://www.behaviortree.dev/docs/nodes-library/sequencenode/

So using the terms from the above link, the original code defined a ReactiveSequence, with my fix we get a "Sequence", and the cpp lib also defines a final type SequenceWithMemory, I think?

I've also found another paid asset on the asset store only provides a single Sequence type (behaving like a normal sequence, or sequence with memory) but provides "conditional aborts" that make the sequence behave like a reactive one.

I'm probably just going to implement "reactiveness" as an option on the Sequence node. Hope this helps someone!