Conditional touch events from another blueprint

Yup, you’re absolutely correct.

A function must return and always will. Even if it executes nothing. Even if you do this:

344181-screenshot-3.png

It seems disconnected but it will return, the execution chain will continue. This becomes critical when you deal with Interface functions as they will always return default values even if they’re not implemented… A nasty thing to track down.

The below macro would terminate the execution chain:

344182-screenshot-4.png

Whatever follows this macro, will not trigger.