Advanced Configuration

Creating a Custom Track

Follow these steps to set up timing for a new track:

1. Map the Track

   • Drive the racing line

   • Note key locations for checkpoints

   • Identify natural sector divisions

2. Place Start/Finish Line

   {
       pos = vector3(x, y, z),  -- Center of finish line
       width = 20.0,            -- Wide enough for all cars
       length = 3.0,            -- Short depth
       heading = 90.0,          -- Perpendicular to track
       type = "start"
   }

3. Add Validation Checkpoints

   • Place every 100-300 meters

   • Cover entire track

   • Ensure proper race line coverage

   {pos = vector3(x, y, z), radius = 15.0, type = "bet"}

4. Mark Sector Divisions

   • Typically divide track into thirds

   • First sector: Start to ~33%

   • Second sector: ~33% to ~66%

   • Third sector: ~66% to finish

   {pos = vector3(x, y, z), radius = 15.0, type = "sector"}

5. Test Thoroughly

   • Complete multiple laps

   • Verify all checkpoints trigger

   • Check sector timing accuracy

   • Adjust radii if needed

Optimizing Detection Zones

Start/Finish Line:

• Width should cover track width + runoff

• Length should be minimal (2-5 units)

• Heading must align with track direction

Checkpoints:

• Standard radius: 15.0 for most turns

• Increase for wide areas: 20.0-25.0

• Decrease for tight sections: 10.0-12.0

• Test at racing speeds

Multi-Track Support

To support multiple tracks, you can:

1. Create track-specific configs:

   local tracks = {
       ["track_name_1"] = {
           checkpoints = {...},
           minLapTime = 60000
       },
       ["track_name_2"] = {
           checkpoints = {...},
           minLapTime = 45000
       }
   }

2. Load based on player location or server event

3. Or create separate resources (simpler approach)