UI name in toolbox: (score|odometer (m)) (≤|<|=|>|≥) [NUMBER]

Block type: Value block, output type Boolean

Definition: Becomes true (or remains true) based on a comparison between current score/odometer and a threshold value.

When it becomes true:

  • > (greater than): When score/odometer exceeds the threshold
  • < (smaller than): When score/odometer is below the threshold
  • = (equals): At the exact value (unreliable—see warning)
  • (greater or equal): When score/odometer meets or exceeds threshold
  • (less or equal): When score/odometer meets or is below threshold

How to build it:

  1. Drag (score|odometer (m)) (≤|<|=|>|≥) [NUMBER] from Logic category
  2. Select variable: score or odometer (m) from dropdown
  3. Select operator: , <, =, >, or from dropdown
  4. Enter numeric value in [NUMBER] field
  5. Connect to condition socket in WHEN block

Field specifications:

  • Variable dropdown: score or odometer (m)
  • Operator dropdown: , <, =, >,
  • [NUMBER]: numeric input

What it monitors:

  • Score: Points earned in the game
  • Odometer: Distance traveled (if location-based features are used)

Example (Simple):
Block: score > 500
Result: Whenever score exceeds 500, condition is true

Example (Range check):
Block 1: score ≥ 100 AND
Block 2: score ≤ 500
Result: Condition true only when score is between 100–500 (inclusive)

Example (Edge Case – Boundary condition):
Threshold: score = 100
Scenario:

  • Score at 99: Condition FALSE
  • Score reaches 100: Condition TRUE (very briefly)
  • Score reaches 101: Condition FALSE again
    Result: Triggers only at the exact moment

Warning – “Equal to” (=) is unreliable:

  • May never trigger (if scores jump past the value)
  • May be true only briefly (one evaluation cycle)
  • Avoid using = for critical game logic
  • Use (greater or equal) or (less or equal) instead for safer logic

Notes:

  • Continuously monitors the current score
  • Useful for unlocking content at score milestones
  • Useful for difficulty adjustments based on performance

Common mistakes:

  • Relying on = for important triggers
  • Forgetting that the condition remains true as long as the comparison is satisfied
Tagged: