A calm first hunt — read the red text, spot the typo, fix the line, and press Play again.
Every developer spends a chunk of their day fixing bugs. The good news: you already have the tool — the Output window names the script, the line, and the problem. This lesson is a gentle first hunt: a few broken scripts, a few red errors, and the small fixes that make them work. No prizes for being fast — the habit is the point.
You meant to print a message, but the Output shows an error on line 1. Read the message, then look at the line:
prnit("Hello")
Type the corrected line so the message prints.
This one is almost right. The Output points at line 1 again — Luau is saying it expected something and never got it:
print("Hello"
Close the call so the line runs without an error.
Here's the tricky one: no red error at all, but nothing appeared in Output. That's a different smell — the script ran and did what it said, which wasn't what you wanted.
print("Hello from the Workspace")
Output stayed empty after you pressed Play. The script is in the Workspace. What should you check first?
This last one is a broken line with a real typo. Type the corrected line in the box.
print "Hello"
Type the fixed line so it prints the message correctly.
Notice what you just did, four times: read the red line, open the script, spot the small thing, fix it, press Play again. That's the entire skill. Errors aren't failures — they're the game telling you exactly where to look.
What's the first thing you do when an error appears?