Parents, children, and safe lookup

Coin Quest code should handle a missing optional object without crashing and wait only when replication timing gives a required object reason to arrive later.

Parent points upward one hierarchy level. FindFirstChild checks now and may return nil. WaitForChild yields for a required child, commonly where client replication timing matters.

Do not use WaitForChild to hide a misspelled server object that should already exist.

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

== is read as “equals equals”: it compares two values and produces a boolean.

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.

return is read as “return”: it ends the current function call and sends a value to its caller.

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 immediate lookup may return an Instance or nil.

Line 4: The guard handles the absent folder explicitly.

Line 5: warn reports actionable setup feedback.

Line 6: return prevents later indexing of nil.

Line 9: The child lookup happens only after the parent is known.

Line 10: Parent travels upward while door may still be nil.

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: Both missing hierarchy levels produce clear feedback rather than a nil indexing error.

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