Function parameters

One Coin Quest message function can describe different coin amounts when the changing value arrives as input.

A parameter is the function's input name. An argument is the actual value a caller supplies.

Parameters exist only inside that function call, so name them for the role they play.

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

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

A colon in a declaration, such as coins: number, introduces a type annotation: the kind of value that name is allowed to hold.

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.

Start with the statements outside function bodies. A function definition creates a callable value; its body runs when a call, event, or scheduled task reaches it.

Trace the arguments at each call and the branch or loop inside that call. Return to the caller when the function returns. For an event, use the action named in Try it to trigger the callback.

Line 3: coinCount is a numeric parameter.

Line 4: The body formats the current call's input.

Line 7: The first call supplies 3 as an argument.

Line 8: The second call supplies a different argument.

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: Each call maps its argument values to meaningful parameter names.

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