The DataModel, services, and workspace

Coin Quest code must find world objects, players, shared assets, and server systems through stable locations.

game refers to the DataModel root. Services are organized below it. game:GetService() asks for a service by its official name.

workspace is the familiar reference to Workspace, the service holding active 3D world objects.

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

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

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

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: GetService returns the Players service and the local uses its conventional capitalized name.

Line 4: Workspace is requested in the same explicit way.

Line 6: The comparison shows that the service local and workspace reference identify the same object.

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 service local, printed name, and Explorer object all refer to the same hierarchy node.

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