"Else" is pretty tricky indeed when you consider it in the field of C2.
Programaticly it's strictly logic : did the code block before executed or not ?
I'm wondering about a case of use:
if, elseif, else
So so far, else as been evoked in "simple case tests" if I may say so, where you have actualy "workarounds" in C2 by inverting conditions or "duplicating" with different comparison operators, and where it's a simple matter of if, else.
How would the C2 "else" handle a "more complex" structure:
Var1 = 0
-> do this
Else
Var1 = 1
-> do that
Else
-> do whatever
I'm aware this can be achieved already and doesn't require an "else" to do.
The interest here, though, is to make sur that if the code in the last event "else" is executed, it implicetely means that all events "linked" above did not execute/their conditions were false.
This is something else that can be worked around but what I expect from an else is to handle such a structure for me now.
So my question 
Ashley here is is the "else" currently planned to take several top levels into account, and if so how would that impact on the "picking" side ? (also are you planning the little visual links like in CC between top and "else" events, it wasn't on your screenshots and I really liked those ^^)
I might come later with more feedback on the subject it is just indeed really tricky once you start to think about it.
Also, since I've used C2 from the start without else, and tools have been given to workaround, it's actualy pretty hard to think about how I would use it and expect from it on usage.