A short refresher over Studio, parts, playtesting, and reading errors before the real coding begins.
You made it through the whole warm-up: Studio installed, your first parts placed, your first script run, and your first error read like a sentence. Before we start writing real code, a two-minute lap of everything you just learned — so it's warm when we use it.
The Explorer is the tree of everything in your game. The Properties panel is the settings of whatever you select. The Output window is where scripts print — and where errors appear in red. When something's wrong, Output names the script and the line first.
You want to know which objects are inside the Workspace. Where do you look?
Play starts a test of your game; Stop ends it. Anything you change while playing — colors, sizes, positions — is thrown away on Stop. That's on purpose: it lets you experiment without wrecking your real work.
You test your game and press Stop. What happens to changes you made during the test?
An error like Workspace.Script:3 tells you exactly where to look: the script named Script, around line 3. The words after it say what went wrong. When something doesn't work, check Output before anything else.
When your script breaks, the first place you look is the window.
That warm-up is everything you need for the next section: how to make things (parts), how to make things run (scripts), and how to find your own mistakes (Output). From here, the lessons assume you're comfortable with all three — and if you ever forget, the previous section is one click back.
Next up: scripts, variables, and the language every Roblox game is written in.
