Roblox Debugging Playbook

Overview

Symptom-first triage for the recurring failure modes of the house stack (Luau strict + Rojo + Wally + ProfileDB/Replica + red networking + FeatureFlags): match your symptom in the table, run the discriminating experiment to confirm the cause, then apply the fix pattern. Most of these bug classes have burned a project before — check the table before inventing a new theory.

When to use / When NOT to use

Use when: a bug's symptom matches (or resembles) a row below; you are about to debug anything involving NPC locomotion, placement CFrames, player data, spawning, or client/server disagreement.

Do NOT use for:

• Full incident narratives and settled-battle history → roblox-failure-archaeology
• Driving the Studio runtime debugger (breakpoints, live inspection) → roblox-debugging skill
• General debugging process discipline (hypothesis → experiment loop) → superpowers:systematic-debugging
• Build/bootstrap failures (wally, rojo, npm scripts) → roblox-build-and-env
• Whether a fix is agent-safe to commit/push/sync → roblox-change-control (owns the four hard rules)
• Platform theory behind replication/streaming behavior → roblox-platform-reference

Jargon (defined once)