...if you wanted to write a behavior that runs events using conditions / actions / expressions, you're doing things wrong, you can do that in construct itself.
The reason I would do this is because a.) its still faster than the overhead of running c2 events, b.) I get sick of recreating events in project after project. I condense most of my events into behaviors and plugins because its easier to reuse them later than events are.
On the other hand I am curious, I must have missed this post last year, other wise I would have responded sooner lol, but how would one access the methods of a behavior on another object from within the object whose behavior is running, clearly that is probably better than accessing the aces, but idk... half the time the aces are already configured in such a way that a behavior script isn't very usable outside of those...
You would need the instance of the object being accessed, but im unclear as to how one actually calls the method on the behavior attached to that object?