Finding your way around Roblox Studio

Knowing where Studio shows objects, code, and messages lets you diagnose Coin Quest instead of guessing what happened.

Explorer answers what exists and where it lives. Properties answers what the selected object is like. Script Editor holds code, while Output reports messages and errors.

Play starts a temporary simulation. Stop returns you to edit mode; changes made only during Play normally do not become edits to the place.

--!strict asks Studio to check your code for type mistakes. It is an instruction for the editor and produces no Output message.

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.

. 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 1: Strict analysis is enabled for this complete script.

Line 3: workspace refers to the Workspace service; Name is a property read with a dot.

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 trace the selected object in Explorer to its property and its printed value in Output.

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