Using elseif

Coin Quest can describe a score as expert, ready, or still learning, but the highest category must be checked before a lower threshold catches it.

Luau checks branches from top to bottom. It runs the first matching body and skips the rest of that chain.

When thresholds overlap, start with the highest or most specific requirement.

--!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.

elseif is read as “else if”: it checks another condition only after earlier branches did not run.

else is read as “else”: it provides the fallback branch.

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

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: score is the value being categorized.

Line 5: The highest threshold is checked first.

Line 7: elseif is reached only when the first check fails.

Line 9: else handles scores below both thresholds.

Line 11: One end closes the chain.

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: Boundary tests enter the intended category and reveal why order matters.

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