roblox-debug
/roblox-debug
Debug Roblox errors - Output messages, stack traces, "attempt to index nil", "Infinite yield possible", require errors, scripts that don't run, replication issues. Use when the user pastes an error, says something "doesn't work", or a play test shows errors.
- Author
- gustavopiumbini ↗
- Repository
- robloxcodingtoolkit ↗
- Licence
- MIT
- Last repository change
- 29.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 29.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Debug Roblox errors - Output messages, stack traces, "attempt to index nil", "Infinite yield possible", require errors, scripts that don't run, replication issues. Use when the user pastes an error, says something "doesn't work", or a play test shows errors.
Triggers from the description
Original author description
Debug Roblox errors - Output messages, stack traces, "attempt to index nil", "Infinite yield possible", require errors, scripts that don't run, replication issues. Use when the user pastes an error, says something "doesn't work", or a play test shows errors.
How it works
- First: where does the script run?
- Common errors
- Method
SKILL.md preview
---
name: roblox-debug
description: Debug Roblox errors - Output messages, stack traces, "attempt to index nil", "Infinite yield possible", require errors, scripts that don't run, replication issues. Use when the user pastes an error, says something "doesn't work", or a play test shows errors.
---
# Debugging
## First: where does the script run?
- `Script` runs in `Workspace`/`ServerScriptService` (server containers), not in `ReplicatedStorage`/`StarterPlayerScripts`.
- `LocalScript` runs in `StarterPlayerScripts`, `StarterCharacterScripts`, `StarterGui`, `StarterPack`/Backpack, or the character — not in Workspace or ServerScriptService.
- `RunContext = Client` scripts run on the client anywhere.
- ModuleScripts only run when required.
- Check `Disabled`/`Enabled` and that the script is a Script vs LocalScript as intended (`inspect_instance`).
## Common errors
| Message | Usual cause | Fix |
|---|---|---|
| `attempt to index nil with 'X'` | Object not there yet (replication/streaming), nil `FindFirstChild`, nil character | `WaitForChild(name, timeout)`, nil checks, `CharacterAdded` |
| `Infinite yield possible on ...WaitForChild("Y")` | Wrong name, created on the other side only, streaming | Check hierarchy (`search_game_tree`), timeout |
| `X is not a valid member of Y` | Typo/case, accessed too early | `FindFirstChild`, exact case |
| `Requested module experienced an error while loading` | Error at the top of the required module | Read the previous error |
| `Module code did not return exactly one value` | Missing `return Module` | Add it |
| Cyclic require (hang/nil) | A requires B requires A | Extract shared dependency |
| `DataStore request was added to queue` | Too many requests | Lower frequency, check budget |
| HTTP 403 on DataStore in Studio | API access off | Game Settings → Security → Enable Studio Access to API Services |
| `Script timeout: exhausted allowed execution time` | Loop without yield | `task.wait()` |
| Remote "doesn't fire" | Created on different sides, wrong name, handler connected late | Create on server, `Net.Names`, connect in `Init` |
| Client change "disappears" | Client changes don't replicate | Do it on the server via a remote |
## Method
1. Get the exact message and line (`ServerScriptService.Server.Services.ShopService:42`) from `get_console_output`; read that script around the line with `script_read`.
2. Read the code and full stack trace.
3. Form a hypothesis and confirm with evidence: temporary `warn` with context, or `execute_luau` to inspect live state.
4. Fix the cause, not the symptom (don't wrap everything in `pcall`).
5. Remove temporary logs; run the Studio lint: `return require(game.ServerStorage.DevTools.Lint).summary(require(game.ServerStorage.DevTools.Lint).run())` (via `execute_luau`).
Versions
The database has no other skills named roblox-debug.
Database snapshot: 13.11.2026 · package version ee5f3a6eaf76 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90roblox-studio-mcp
Use the Roblox Studio MCP server (Roblox_Studio) to inspect the open place, read scripts, run Luau, play test, read Output, simulate input and take screenshots. Use whenever Studio MCP tools are available, to verify changes in Studio, or when asked to test or debug in the game. - 100glua-error-debugger
Reads and fixes Garry's Mod Lua errors. Explains the error line and stack trace format, how to tell client errors from server errors, and the usual cause and fix for the common messages - attempt to index a nil value, attempt to call a nil value, attempt to perform arithmetic or… - 91roblox-game-development
Use this skill for any Roblox related tasks - 90roblox-networking
Design or review Roblox client-server communication. Use for remotes, bindables, replication, network ownership, input validation, rate limiting, and exploit defenses. - 90roblox-debugging-bugfix
Debug and fix Roblox bugs through Studio MCP. Use for repro steps, console errors, script search/read/edit flow, broken UI, failed gameplay systems, data issues, remotes, regressions, root-cause reports, and post-fix verification. - 100roblox-studio-mcp
Use when working in Roblox Studio through MCP: editing scripts or scenes, generating assets, playtesting, screenshots, or input.