Well, that was almost month ago… so I expected any update at this point. I guess we must wait several years ![]()
On more serious note, what about performance? Is instantiation time ok? What about allocation and garbage collection?
Actually there is one important question.
The main problem I had with this asset 1-2 years ago was lack of abort system. I can see there is abort node that loops conditions and stops execution of branch, but this is far from enough. How would I abort lower priority nodes, is that possible?
Consider following example (BTW looks like UI is only usable in dark mode…):
There is enemy with some dodge logic that would run only if attack is approaching, but normally it walks somewhere. Now assume this enemy is on the way to waypoint, but suddenly there is attack and it must stop walking and dodge attack. How to “rewind” graph to AbortIf node/condition to make it react to the event?
// EDIT: I found this topic How to create a Low-Priority/Self Abort Workflow?
So it is possible for state machine branch, but in other cases it is complicated and not possible I guess.
