Find and fix a bug
Use reproduction steps, project search and snapshots to make debugging reproducible.
Capture the failure#
Record what you did, what you expected and what actually happened. Copy the exact Output message, file path and line number. Mention if this was a server problem, a problem for one client or all clients.
- Repeat the steps in a new play session.
- See if the failure depends on the number of players or their spawn time.
- Reduce the case to the smallest system that has the failure.
Gather relevant code#
Search for the function or remote event name in the Explorer search bar. The Context tab has a list of detected functions and require expressions. Send the relevant bundle with your bug report; it is a text index, not a Luau parser or a guarantee of full dependency awareness.
Prove the fix#
Make a checkpoint before implementing a fix. Repeat the reproduction and test related cases like respawning or reconnection. If you find a regression, restore the checkpoint and retain the failed patch in an export for comparison.