Small details. Better patrols.
Good testing starts with a clear description of what happened—not just “it broke.” Check the same scenario again, keep it fictional, and make it easy for the developer to reproduce.
What to prepare.
- Your BeamNG version, BeamMDT edition and mod version.
- The vehicle, map and steps that produced the issue.
- What you expected, what actually happened, and whether it happens again.
- A screenshot or short clip without real personal information.
A useful report.
“After assigning a sample call, I changed maps. The call remained assigned when I expected a new shift. It happened twice on the same version.” Specific details make fixes possible.
Meet the testers