Reports without the following information will not be investigated!
Your bug reports must have:
- A descriptive title - Engineers should know what the bug is before opening the thread.
- A detailed description of the bug - Information on what the bug is and what you expect to occur.
- Where the bug happens - Does the bug only happen with specific places / users / groups / etc?
- When the bug started happening - Dates help find the version causing it so it can be fixed faster.
- Screenshots and videos of the bug - Include screenshots / videos of the bug happening; they’re extremely helpful and more descriptive than words alone.
Provide step-by-step instructions engineers can take that cause the bug to happen.
These steps must be:
- Minimal - If you have a complicated repro, simplify as much as possible.
- Specific - The steps must be clear, detailed, and not open to misinterpretation. Don’t assume engineers know what you mean.
- Consistent - Ideally, your steps reproduce the issue 100% of the time. Please specifically mention how often your steps reproduce the bug (100% / 50% / Rarely?)
For bugs with complicated setups or conditions, attach a minimal place file to your thread that can be used to reproduce the bug. Provide repro files instead of screenshots for bugs that only happen for certain code / instances / etc!
- Crashes or Freezes - Include a repro. If you cannot provide a 100% repro, provide a dump.
- Performance Problems - Include a microprofiler dump, and your system information if the problem is specific to your computer.
- Problems running Roblox / Studio or error popups - Include relevant log files.
- Graphics Problems - Include your system information.
- Problems specific to a Place / User / Group / etc - First try to isolate the issue to a repro file. Otherwise, include direct links to the affected assets; engineers will not know what “my game” or “game-name” refer to.
- Backend Problems (e.g. Team Create connection failures) - Provide information to help find the problem on Roblox’s side.