Find and fix a bug
Use reproduction steps, project search and snapshots to make debugging repeatable.
Capture the failure#
Record what you did, what you expected and what actually happened. Copy the exact Output message, file path and line number. Say whether it occurred on the server, one client or all clients.
- Try the same steps in a fresh play session.
- Check whether the failure depends on player count or spawn timing.
- Reduce the case to the smallest affected system.
Gather relevant code#
Search for the error’s function or remote name in the Explorer search field. The Context tab lists detected functions and require expressions. Copy the relevant bundle with your bug report; it is a text index, not a full Luau parser or a guarantee of complete dependency understanding.
Prove the fix#
Save a checkpoint before applying a fix. Repeat the original reproduction and test nearby behaviour, such as respawning or reconnecting. If the change causes a regression, restore a checkpoint and keep the failed attempt in an exported backup for comparison.