Instances, properties, methods, and events

A Coin Quest door has data you can read, actions you can request, and signals you can respond to. Confusing those categories leads to unclear code.

An Instance is the object. A property is data on it, such as Name. A method is behavior called with a colon, such as FindFirstChild. An event is a signal, such as Touched.

Read the punctuation: dot for a property, colon and parentheses for a method call, and later :Connect() on an event.

--!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 “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: FindFirstChild is a method called on workspace.

Line 5: IsA is another method and refines the object's class.

Line 6: Name and Anchored are properties; Touched is an event value. Printing the event does not connect to it.

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: You can classify each member by what it represents and how code uses 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.