Scheduling with the task library

Coin Quest needs delays for temporary effects and independent work without using deprecated timing helpers.

task.wait yields the current thread. task.delay schedules a callback after time. task.spawn schedules a callback to run independently soon.

Choose the narrowest tool that matches intent, and keep ownership or cancellation needs visible.

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

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

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: The delayed callback is named.

Line 7: task.delay schedules it without yielding setup.

Line 8: task.spawn schedules separate immediate work.

Line 12: The current thread continues after scheduling.

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 scheduling choice has an explicit timing purpose and no legacy helper is used.

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