Blueprints are serialized, i.e. they are single threaded, I was asking this question in reference to a blue print having a lock node, same thing.
I have not looked into the engine, but more than likely, or my guess if you will, is that each “blueprint” (and I use that term loosely), has a queue of “events” that needs to be processed, and that “Tick” can override any of that processing, when it’s ready to fire, because of “Tick” being so fundamental, I’m willing to bet that it has precedence. But as “events” come in, they get queued, then dispatched as the internal “scheduler” of the engine determines they should be. I say this, because I have never read any official doc, that mentions an order to “events”, yet there is specific verbage, about Tick events, that if they are not firing as fast as the engine determines they should, then they will get a higher “precedence” on the next tick cycle.
Just some thoughts.