Roblox Debugging Bugfix

Goal

Move from symptom to verified fix without guessing. For hard or intermittent bugs, follow the discipline below; skip phases only when you can justify it.

Phase 1 — Build a repro loop first (this is the skill)

Everything else is mechanical once you have a fast, repeatable pass/fail signal for the bug. Spend disproportionate effort here. Be aggressive and creative before you touch a fix.

Ways to construct one, roughly in order:

1. Studio playtest repro — the exact steps in Play mode that surface the bug; watch get_console_output.
2. execute_luau harness — call the suspect server/module function directly with a fixture input and assert the result, instead of clicking through the whole game.
3. Targeted scenario — spawn the minimal instances/state that trigger the code path (one part, one remote, one player state).
4. Replay a captured payload — save the real remote payload / data profile that misbehaves and push it back through the code path in isolation.

Make the loop fast, sharp, and deterministic: narrow to the specific symptom, pin any randomness/timing, and cut unrelated setup. A 2-second deterministic check beats a 30-second flaky one.