Configuration
Debug Settings
Enable detailed logging for troubleshooting:
Config.debug = {
enabled = false, -- Master switch for all debug logs
categories = {
tablet = true, -- Tablet opening/closing
permissions = true, -- Permission checks
flags = true, -- Flag spawning/deletion
markers = true, -- Marker interactions
notifications = true, -- Notification sending
server = true, -- Server-side events
cleanup = true, -- Resource cleanup
lights = true -- Starting lights
}
}Set enabled = true during setup, then false in production.
Permission System
Configure who can access the race control tablet:
Config.permissions = {
requireAdmin = true, -- Enable permission checks
permissionType = 'esx_job', -- Options: 'esx_job', 'esx_group', 'ace'
allowedJob = 'circuit', -- ESX job name
allowedGrades = {0, 1, 2, 3, 4}, -- Job grades (empty {} = all grades)
adminGroups = { 'admin', 'moderator', 'steward' }, -- ESX groups
ace = 'formula1tablet.access' -- ACE permission name
}Permission Type Options:
1. ESX Job-Based (Default)
Only players with the specified job can use tablet
Can restrict by job grades
Example: Circuit marshals, race directors
2. ESX Group-Based
Based on ESX user groups
Useful for admin-only access
Multiple groups supported
3. ACE Permission
Uses FiveM ACE system
Add to server.cfg:
4. Disable Permissions
Anyone can access tablet (not recommended for public servers)
Notification Messages & Translation
Complete translation support - Customize all notification text:
Translation Example - French:
Notification Field Descriptions:
type- FormulaOneNotif style (drapeau_vert, drapeau_jaune, drapeau_rouge, sanction, info)title- Large heading in notificationmessage- Main body text (HTML supported:<br>for line breaks)penalty- Additional rule/penalty textduration- Display time in millisecondsesxNotif- Fallback ESX notification (if FormulaOneNotif unavailable)
Race Car Settings
Configure which vehicles receive race notifications:
Options:
checkVehicle = true- Only F1 drivers get flags (realistic)checkVehicle = false- Everyone gets notifications (spectators included)
Tablet Settings
Customize tablet prop and animation:
Customization:
Change
modelto use different propAdjust
attachposition/rotation for better hand placementSet
blockControls = falseto allow movement with tablet
Marker Positions
Configure interaction points for tablet and starting lights:
Adding More Markers:
Access Method
Choose how players interact with tablet:
'marker'- Use 3D markers (default)'ox_target'- Use ox_target (requires ox_target resource)'both'- Enable both methods
Flag Positions
IMPORTANT: Configure physical flag spawn locations around your track.
How to Set Flag Positions:
Get Coordinates: Use a coordinate script or in-game tool
Walk the Track: Place markers at strategic locations
Coverage: Ensure flags are visible from track
Heading: Set
hso flags face the correct directionHeight: Adjust
zcoordinate for proper elevation
Recommended Placement:
Every major turn
Start/finish straight
Dangerous zones
Every 100-200 meters for complete coverage
15-20 flags per sector is typical
Last updated
