[2.0.69] Everything signal fails to evaluate when Each signal is also used with no inputs
Posted: Wed Oct 15, 2025 7:43 pm
If you use the Everything 'signal' with no inputs, it should evaluate that condition to True.
But if you also use the Each 'signal' in a separate OR clause, then it it evaluates to True...but no output occurs.
In part this makes sense - since the Each signal implies iterating over each signal, and there are non to iterate over
but in part it's a bug, since it looks like it would work from the UI, and this is a fairly logical way to e.g. add a default output if there are no inputs.
Not bothering with saves since it can be trivially blueprinted:
But if you also use the Each 'signal' in a separate OR clause, then it it evaluates to True...but no output occurs.
In part this makes sense - since the Each signal implies iterating over each signal, and there are non to iterate over
but in part it's a bug, since it looks like it would work from the UI, and this is a fairly logical way to e.g. add a default output if there are no inputs.
Not bothering with saves since it can be trivially blueprinted: