Before you begin
Create a player Number property named Keys and an On/Off property named Powered.
Build it step by step
Create an Interact Pressed rule. Add TIMING → IF / ELSE inside its THEN action list.
Choose an Object property condition checking Keys at least 1. In the inner true branch, open a door; in the inner ELSE branch, add a helpful text message.
Use ALL or ANY conditions when appropriate: ALL requires every child condition; ANY needs only one. Keep the first example to two checks.
Add RANDOM: choose an action sequence for a decorative reward, or RANDOM: choose a property value for a number property. Keep randomness away from essential access until tested.
Test each branch deliberately by changing starting property values in the editor. Restart between cases so previous runtime changes do not affect the comparison.
Practical example
Interact → IF Keys ≥ 1 → open door; ELSE → show “Find a key first”. A later version can require both Keys ≥ 1 and Powered On.
Test your work
Each branch runs only in its intended case and the player receives a clear explanation when blocked.
If it does not work
A touch checklist nested inside a condition tests any contact; it does not create its own touched-object action context. Top-level contact rules provide that context.
Student challenge
Add a random celebration effect after the door opens, while keeping access deterministic.
Show the result to a partner. Explain what you changed and how you tested it.
