Troubleshooting Guide

Find quick answers and solutions to common installation, permission, vehicle, and configuration issues below.

1. /oiltaskmanager or /oilbonusmanager Gives "No Permission" or Console Error

🔴 Symptom:

When running /oiltaskmanager or /oilbonusmanager, the chat reports "You do not have permission to do this", or the server console displays:

Execution of add_ace denied for resource bs-oilfieldjob

🟢 Cause:

1. FiveM's engine blocks resources from registering or modifying ACE permissions from script code unless granted permission in server.cfg.
2. The user executing the command is not part of the ACE group defined in config/sv_config.lua (adminPermission).

🔧 Solution:

1. Open your server.cfg and add the following lines above ensure bs-oilfieldjob:

   add_ace resource.bs-oilfieldjob command.add_ace allow
2. If you use a different group name (e.g., group.superadmin or group.god), update adminPermission in config/sv_config.lua:

   adminPermission = 'group.superadmin',

2. Vehicles Fail to Spawn at Base Headquarters

🔴 Symptom:

The crew leader starts the route, but no work truck appears, or the chat displays a vehicle spawn failure.

🟢 Cause:

The spawn coordinates defined in base.vehicle.spawnPoints are currently blocked by parked player cars, props, or nearby network entities. The script checks each coordinate against sharedConfig.job.spawnClearRadius (default: 3.5m) to prevent vehicle clipping.

🔧 Solution:

1. Ensure the parking bays in front of the base NPC at coordinates 1711.18, -1580.68, 111.29 are clear of obstructions.
2. In config/sh_config.lua, add more backup coordinates to base.vehicle.spawnPoints so the server has more alternative spawn points to choose from:

   spawnPoints = {
     vec4(1711.18, -1580.68, 111.29, 279.87),
     vec4(1710.41, -1576.29, 111.30, 279.87),
     vec4(1709.47, -1571.63, 111.33, 279.87),
     vec4(1711.00, -1566.21, 111.34, 279.87),
     -- Add additional bays here if running a high-population server
   },

3. Work Clothes Glitch or Show Invisible Body Parts

🔴 Symptom:

When clocking in, the character's torso, arms, or legs turn invisible or display distorted civilian clothing textures.

🟢 Cause:

Your server uses a custom clothing pack or add-on EUP that replaces or shifts vanilla GTA V drawable ID numbers. The default configuration in config/cl_config.lua targets standard base GTA DLC clothing components.

🔧 Solution:

1. Open your server's clothing store menu (illenium-appearance, rcore_clothing, fivem-appearance, or qb-clothing).
2. Dress your ped in the desired workwear outfit and record the exact drawable numbers:
   • torso2 (jacket/top)
   • pants (legs)
   • decals (badges or reflective strips)
   • hat (hard hat prop)
3. Open config/cl_config.lua and update outfits.male and outfits.female with the recorded numbers.

4. Target Interaction (ox_target / qb-target) Missing on Foreman NPC or Tasks

🔴 Symptom:

Approaching the base NPC or task props with your target key (Alt or Right Click) does not display any interaction eye or options.

🟢 Cause:

1. The interaction setting in config/sh_config.lua does not match the active target resource running on your server.
2. If jobName is set to a whitelisted string (e.g., 'oilworker'), your character does not have that specific job assigned.

🔧 Solution:

1. Open config/sh_config.lua and verify:

   interaction = 'ox_target', -- Or 'qb-target' / 'qbx-target'
2. If jobName is configured:

   jobName = false, -- Set to false to allow all players to interact without job restrictions
   Or grant your player the job via console command (e.g. /setjob [id] oilworker 0).

5. Database Errors: Table 'bs_oilfield_*' Doesn't Exist

🔴 Symptom:

Console prints SQL errors stating tables bs_oilfield_playerdata, bs_oilfield_playerquests, or bs_oilfield_bonuses are missing upon player connect.

🟢 Cause:

The install.sql file was not executed or failed to import into your MySQL database.

🔧 Solution:

1. Open your database manager (HeidiSQL, phpMyAdmin).
2. Connect to the database defined in your server's mysql_connection_string.
3. Open install.sql from the bs-oilfieldjob resource root and execute all queries.
4. Verify that the 3 tables are created:
   • bs_oilfield_bonuses
   • bs_oilfield_playerdata
   • bs_oilfield_playerquests