1. Explain what drivers should submit
Publish your car requirements and submission deadline before entries become busy. Tell drivers where to send their car and how they will hear about any problems.
Leave time for corrections. A submission deadline right before the first run gives both the driver and inspector very little room to resolve an issue.
2. Make feedback easy to act on
A driver needs to know what needs attention and what to do next. Clear feedback is more useful than a message that only says the car failed.
For staff, checking the same kinds of file problems across many cars can become repetitive. Separate those checks from the decisions that depend on your rules and an inspector’s judgment.
3. Scan common issues and review the result
Car Quick Scan & Auto-Fix checks textures, physics, model and car information. It produces HTML and PDF reports, with skin previews and wheel-clearance images to support the review.
Fix It For Me repairs supported problems on a copy of the car, including common texture, file-layout and naming issues. Drivers and staff can review the result before using it.
The module runs with the core bot. It reduces repeated checking and repair work, while your inspector decides whether the car meets your competition’s requirements.
Before your next event
Readiness checklist
Tick these as you prepare, or print a copy for your team. This site does not save your ticks.
Keep the checklist
A simple copy for your team, ready to open in Google Sheets or Excel.
Common questions
Does a scan mean a car is approved for competition?
No. The report helps identify issues and supports the review. Your inspector still checks the car against your event’s requirements and gives final approval.
Does Auto-Fix repair every problem?
No. It repairs supported problems on a copy of the car. Other issues may need manual work, and the repaired copy should be reviewed before use.
