Mini-project: Build a score summary

A score summary turns raw Coin Quest state into feedback a player can understand and gives the Studio Companion a safe calculation to test with public values.

First calculate numeric state, then compare it with a goal, then format the result. Keeping those steps separate makes each one testable.

Public runtime cases disclose their inputs and purpose. They provide formative feedback without claiming that the code is certified.

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

= 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 name is display data.

Line 4: The collected coin input stays numeric.

Line 5: The multiplier is named.

Line 6: A separate bonus completes the rule.

Line 7: finalScore is a derived numeric value.

Line 8: The comparison records goal state.

Line 9: Interpolation produces the player-facing summary.

Line 11: The finished message is printed.

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: The formatted message matches each public numeric case and remains readable.

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