Tracker Dart System

Installation uses third-eye / target on a vehicle, not the inventory item on its own. Typical flow:

1. Have the tracker item in inventory if your config requires it.
2. Target the vehicle and choose Install tracker system.
3. Press G (default) to open the overlay.
4. Press Space (default) to fire a dart at a vehicle ahead.

Set the inventory item to usable = false. Do not add an ox_inventory export on the item. That causes No such export trackersystem errors.

That is expected if you try to "use" the item from inventory. The item is a requirement check, not the install action. Install through target on the vehicle hood instead.

Both keys are configurable in config.

You need ox_lib and a target system (ox_target or qb-target). Helptext alone is not enough for install, remove, and refill interactions. Job and item checks still need a framework unless you customize the bridge.

Work through this checklist:

• Check allowedJobs. Default is often police/sheriff. Set to nil to disable.
• Check itemName matches your inventory item, or set to nil to skip the item.
• Set onlyAllowedVehicles = false if any vehicle should work.
• Confirm installWithTarget = true.
• Look for script errors on server start.
• Make sure the player has the correct job if jobs are restricted.

From v1.0.2 onward, use Config.installWithTarget = true. The old InstallwithItem setting was replaced. Re-read your config after updates instead of copying an old file.

This is a known qb-target integration issue. The fix is to use a global vehicle target in the client bridge instead of per-entity targeting. ox_target on the same server working for other scripts does not rule this out.

If options still fail, add debug prints in the bridge canInteract logic and check F8 while targeting a vehicle.

Confirm toggleOverlay = true and press G while in an allowed vehicle with the system installed. Also verify job restrictions and the vehicle allowlist.

Override the vehicle check in the client bridge with a custom CanVehicleHaveDartSystem function that returns true, or do a clean reinstall to make sure config is loading correctly.

Common causes:

• Blip limit reached because other scripts use too many blips. Test with other resources stopped.
• Job detection failing on ESX Legacy 1.9.3 or QB-Core. Update bridge files to the latest version.
• Transient issues that clear after a restart.

Enable debug = true and use the latest script version for more console output.

Yes, by default blips sync to players with the same job. You can configure it so only the officer who deployed the dart sees the blip.

Test on a vanilla GTA vehicle first. On addon models the dart can spawn inside body collision and look invisible. You may need per-model tuning or restrict allowed vehicles until offsets are right.

Target the vehicle near the dart prop, not just the hood. Remove works with ox_target and qb-target by default. Other target systems need bridge changes.

Refill through target on the vehicle when darts are depleted. It is not a simple inventory "use item" action. If refill is missing on qb-target, apply the same bridge fix as install.

Hit NPC vehicles are set as mission entities and should no longer despawn. This helps with ERS, FivePD-style traffic, and similar setups.

Generally yes through the QB bridge, but job and player resolution may need small bridge tweaks on some Qbox setups.

On standalone servers, keep Config.itemName and Config.installWithTarget = true, then adjust the bridge so target does not require the inventory item line and server-side item removal is bypassed. Revert to default bridges first; many issues are config-only.

Update to v1.0.7 or newer. Blip updates were optimized and police player lookup is cached. You can also raise Config.blipUpdateInterval (for example to 5 seconds).

Rare cross-script issues have been reported (for example jg-mechanic repair kits freezing while this resource is running). If another script breaks only when gs_trackerdart is started, test by stopping this resource temporarily to confirm the conflict.