How to Read Roblox Studio Script Errors: The Output Window Explained
Every red line in Roblox Studio's Output window tells you the script, the line and what went wrong — most beginners just never learned to read it. Here is how, plus fixes for the six errors everyone meets first.
In this guide
Opening the Output Window (And Leaving It Open) The Three Kinds of Messages How to Read an Error Line The 6 Most Common Beginner Errors 1. "attempt to index nil with ..." 2. "expected 'end' (to close ...)" or the error points at the very end of the script 3. "attempt to call a nil value" / calling a function that does not exist 4. "Infinite yield possible on 'WaitForChild(...)'" 5. "... cannot be set" / trying to change a read-only property 6. Plain syntax errors from typos A Calm Debugging Workflow That Always Works Frequently Asked Questions My script has no errors but still does nothing. Why? Do warnings matter if my game still works? How do I find which line an error is on if the script is long?New scripters treat the Output window like a fire alarm: something red appeared, the game is broken, panic. Experienced developers treat it like a message from a colleague. An error in Roblox Studio is not a punishment — it is the engine telling you the exact script, the exact line and the exact problem, in that order. Once you can read that message properly, you can fix most beginner errors in under a minute, including the six that account for nearly every "my script doesn't work" question ever asked.
Opening the Output Window (And Leaving It Open)
In Roblox Studio, go to the View tab at the top and click Output. A panel appears, usually docked at the bottom of the screen. Leave it open permanently. Every test run, press Play and glance at Output first, before you judge whether your code "worked". Many scripts fail silently from the player's point of view — nothing visibly happens — while Output contains a precise explanation.
The Three Kinds of Messages
| Message type | Colour | Meaning |
|---|---|---|
| Print / output | White or blue | Messages your scripts deliberately printed with print(), plus general information from the engine. |
| Warning | Yellow / orange | Something is wrong or risky, but the script keeps running. Warnings often predict a future error — do not ignore them. |
| Error | Red | The script hit a problem it could not continue past. That script stops at that line. Other scripts keep running, which is why your game may half-work. |
That last detail matters: an error stops one script at one line. Everything after the error line in that script never runs. When a system "half works" — the shop opens but the buy button does nothing — you are usually looking at a script that died partway through.
How to Read an Error Line
A typical error looks like this:
ServerScriptService.RoundManager:42: attempt to index nil with 'Value'
Read it in three parts. ServerScriptService.RoundManager is where the script lives and its name — click the error in Output and Studio jumps straight to the script. 42 is the line number. attempt to index nil with 'Value' is what actually went wrong. Ninety percent of debugging is taking that final sentence seriously instead of staring at your whole script hoping to spot the problem.
The 6 Most Common Beginner Errors
1. "attempt to index nil with ..."
What it means: your code tried to use something that does not exist. The script asked for an object — a part, a player, a value — got nil (nothing), and then tried to read a property or child of that nothing.
Usually caused by: a typo in an object's name, looking for an object before it has loaded, or searching in the wrong place, such as looking in Workspace for something that lives in ServerStorage.
Fix: print the object before the failing line to confirm it exists, check the spelling against the Explorer exactly (capital letters count), and if the object loads later, use WaitForChild() instead of a direct reference.
2. "expected 'end' (to close ...)" or the error points at the very end of the script
What it means: you opened a block — an if, a function, a for or while loop — and never closed it with end. Studio keeps reading, reaches the bottom of the file, and complains there.
Fix: count the openers. Every function, if ... then and loop needs its own end. Click just after a keyword and watch the matching highlight. Indentation is your friend: code inside a block should sit one tab further in, so a missing end visibly breaks the pattern.
3. "attempt to call a nil value" / calling a function that does not exist
What it means: you called something as a function, but that thing does not exist — often a misspelled method name, a function you renamed in one place but not another, or a function defined after the line that calls it in the same script (for local functions).
Fix: compare the call, character by character, with the definition. Check capitalisation. If it is a built-in method, check you are using the right object — for example, :Clone() exists on instances, but a variable holding a number has no methods at all.
4. "Infinite yield possible on 'WaitForChild(...)'"
What it means: this one is a warning, in yellow. Your script waited for a child that has not appeared after several seconds — and may never appear. The script is stuck on that line forever, which looks exactly like "nothing happens".
Usually caused by: a spelling mismatch, or waiting in the wrong parent, or the object genuinely never being created because another script errored earlier.
Fix: verify the name and parent in the Explorer while the game is running. Then scroll up in Output — an earlier red error in the script that was supposed to create the object is the real culprit.
5. "... cannot be set" / trying to change a read-only property
What it means: some properties can be read but not written by scripts. Classic beginner cases include trying to set properties the engine controls, or changing things from the wrong type of script — for example, a server script cannot reach into a player's screen GUI in the way many beginners expect, because GUIs live on the client.
Fix: read the exact property named in the error and ask two questions: is this property script-writable at all, and am I in the right place (Server Script vs LocalScript) to touch it?
6. Plain syntax errors from typos
What they look like: messages like "Expected identifier when parsing ..." or "Expected ')' (to close ...)" near a specific line.
What it means: the line itself is malformed — a missing bracket, a stray comma, a keyword typed wrongly. Lua cannot even start running the script, so nothing in it works.
Fix: look at the line named, then the line above it. A missing closing bracket is usually on the previous line, and the error address points where the parser gave up, not where the typo lives.
A Calm Debugging Workflow That Always Works
- Read the first error only. Later errors are often consequences. Fix the top red line first, then test again.
- Add print checkpoints. Put
print("checkpoint 1"),print("checkpoint 2")between steps of your script before testing. The last checkpoint that appears tells you exactly where execution stopped. - Print the values, not guesses. Before a line that fails, print the variables it uses. Half of all "impossible" errors turn out to be a variable holding nil, zero, or the wrong object.
- Change one thing at a time. If you edit five lines and the error vanishes, you learned nothing and probably created the next bug.
- Comment out to isolate. Temporarily select a block of code and comment it with
--. If the error disappears, the problem is inside that block; narrow it down by halves. - Test in a live-style run. Some errors only appear with real players or in a server test (Studio's Test tab can start local servers with multiple test players). If it works in Play Solo but fails in the real game, suspect client/server differences first.
Frequently Asked Questions
My script has no errors but still does nothing. Why?
Check Output for a yellow "Infinite yield possible" warning — a script stuck on WaitForChild looks silent but is actually frozen mid-line. Also check that the script is in the right place and is not Disabled, and that a LocalScript is not sitting somewhere LocalScripts never run, such as ServerScriptService.
Do warnings matter if my game still works?
Yes, eventually. A warning means the engine noticed something unsafe — a yield that may never finish, a deprecated function, a risky operation. Games accumulate warnings until one becomes a real failure. Fix warnings while your codebase is small and they are still easy to find.
How do I find which line an error is on if the script is long?
Click the error message directly in the Output window — Studio opens the script at the exact line. If clicking is not an option, the number after the script name in the error (the :42: part) is the line number, and you can jump to it in the script editor.
