We removed the ‘OR’ in rules from the UNSW version intentionally to simplify the thinking process and eanble teachers to think one rule at a time which are created without any other dependency, but can be nested in the editor (this functionality has not been pushed in the main repo yet).
This means something like the following in which only one statement per 'block' will show to students:
If <attended=yes> then [statement1]
else If <attended=no> then [statement2]
If <completedX between value1 and value2 > then [statement3]
else If <completedX between value2 and value3 > then [statement4]
by treating the variables separately, you don’t need to worry about filling all the conditions as each statement is only affecting the cases in which the conditions are true or matching values.
As the conditions you are showing below are separate it is easier to think about it as a matrix in which the different options are treated separately. I'll make a post with a longer explanation to illustrate the approach and logic.