AND/OR Block

AND

What it does: Becomes true only when ALL connected conditions are simultaneously true.

How it works:

  • Evaluates all connected conditions
  • Returns TRUE only if every single condition is TRUE
  • Returns FALSE if any condition is FALSE

When to use:

  • Requiring multiple game states simultaneously (e.g., “Task 1 finished AND Score > 100”)
  • Creating multi-step triggers
  • Ensuring all prerequisites are met

Example (Simple):
Connect: [task 1] finished AND score ≥ 100
Result: Both must be true to activate actions

Example (Chaining for 3+ conditions):
Block 1: [task 1] finished and [task 2] finished (output = AND1)
Block 2: AND1 and score > 500 (output = both previous tasks done AND high score)

Common mistakes:

  • Using AND when you mean OR (and vice versa)
  • The more conditions in an AND, the less likely it will trigger

OR

What it does: Becomes true when ANY connected condition is true.

How it works:

  • Evaluates all connected conditions
  • Returns TRUE if even one condition is TRUE
  • Returns FALSE only if all conditions are FALSE

When to use:

  • Multiple ways to trigger the same action (e.g., “Task 1 answered OR Task 2 answered”)
  • Creating fallback conditions
  • Flexible game branching

Example (Simple):
Connect:[task 1] answer is correctOR[task 2] answer is correct
Result: Triggers if either task is answered correctly

Example (Combining AND and OR):
Block 1:score > 100ORscore < 50(output = OR1)
Block 2:[task finished]ANDOR1(triggers if task done AND score is either high or low)

Notes:

  • Can be nested inside other logic operations
  • The more conditions in an OR, the more likely it will trigger

Common mistakes:

  • Misunderstanding OR (triggers if ANY condition is true, not just one specific one)
Tagged: