Connections and cleanup

Reinitializing a Coin Quest controller without cleanup can make one touch run the same behavior several times.

The connection is a resource owned by the controller that created it. Disconnecting stops future callbacks but does not undo work already completed.

Make teardown idempotent: calling it again should not create an error or a new listener.

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

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

: is read as “colon”: it calls a method with the object supplied as the first receiver value.

? is read as “optional”: it marks a type that may also be nil.

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 6: The optional typed local owns the returned connection.

Line 10: cleanup names the teardown behavior.

Line 11: The guard permits repeated cleanup calls.

Line 12: Disconnect stops future callback delivery.

Line 13: Clearing the reference records that cleanup happened.

Line 17: task.delay schedules teardown without blocking setup.

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 listener stops once and repeated teardown remains harmless.

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