Combining conditions safely

A locked door may require a key, a level, and an active round. Naming each rule makes failures easier to explain.

Break a decision into facts with game-language names. Combine those facts only after each one is understandable.

Parentheses show intentional groups and reduce the chance that and/or precedence communicates a different rule.

--!strict asks Studio to check your code for type mistakes. It is an instruction for the editor and produces no Output message.

Matching quotes such as "hello" surround a string: a piece of text. The quotation marks tell Luau where the text starts and ends.

print(...) calls the built-in print function. Put the values to show inside its parentheses; separate multiple values with commas. Read the result in Studio's Output panel.

local is read as “local”: it creates a name that is available only in the current code scope.

if is read as “if”: it starts a decision by evaluating a condition.

then is read as “then”: it marks the body that can run when the condition is truthy.

end is read as “end”: it closes a block such as a decision, loop, or function.

= is read as “is assigned”: it evaluates the right side and stores that value in the name on the left.

Read one statement at a time: name the value being read, what the operation does, and where its result goes. Keep identifiers exactly as written so you can find them again in the code.

Pause at calls, conditions, and loops. Explain when the body runs before moving to the next statement; use the line notes above when a symbol is unfamiliar.

Begin at the first executable statement. Comments and blank lines do not run; a branch chooses which block runs, and a loop may revisit its body.

Line 3: The inventory fact is named.

Line 4: The numeric state remains separate.

Line 5: Round state is another fact.

Line 6: The comparison receives a game-language name.

Line 7: The final rule combines three booleans.

Line 9: The branch reads like a plain question.

Before running, identify the starting values and any existing Studio objects this example needs. List what you expect to change.

After your practice change, check this result: You can identify which named fact prevents the branch from running.

Reading or printing a value leaves it unchanged. Look for assignments, calls that change state, and property updates to explain each change you observe.