Comments and readable names

Coin Quest will grow across twelve modules. Clear names help you return to a script later and understand which value or behavior it represents.

A name should answer what a value means in the game. A comment should answer why a less-visible decision exists.

Single-line comments begin with two hyphens. Avoid narrating a clear line such as assigning 5 to coinCount.

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

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 comment records the design intent behind the value.

Line 4: firstRoundSeconds is a camelCase local name that includes meaning and unit.

Line 6: The value is printed so you can verify it during a test.

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: A reader can infer both what the value measures and why you chose it.

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