If I’m creating a blueprint and want maximum flexibility für conditions I can do something like:
...
input:
...
flex_condition:
name: "Flexible conditions"
default: []
selector:
condition: {}
...
conditions:
- conditions:
- condition: !input flex_condition
...
Is it possible to something similar with triggers?
The reason is that I want to have a flexible possibility to add - let’s say - custom triggers for special cases.
I know that I could e.g. use an input boolean as a trigger and to a kind of outsourcing to the logic behind that input boolean. Yes, that’s an option but something like the condition above is much more nicer.
Is it possible?