Mini-project: A round countdown

A visible round countdown gives Coin Quest structure, but its timing must let the rest of the simulation keep running.

Use a bounded numeric loop for known seconds. Each iteration reports the state, then task.wait yields before the next one.

The wait duration is approximate scheduling, not precision physics timing. The important beginner rule is that the loop is finite and yields.

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

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

for is read as “for”: it starts a controlled repetition with a changing loop value.

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

. is read as “dot”: it accesses a named property or table field.

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 duration has a descriptive name and unit.

Line 4: A start status appears once.

Line 6: The loop counts from five through one with a negative step.

Line 7: Interpolation formats the current state.

Line 8: task.wait yields between updates.

Line 11: The completion status runs after the finite loop.

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 finite countdown yields between updates and ends with one completion message.

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