Configuration

Everything here lives in config.lua, read at resource start. Run restart tDetector after editing.

Speed unit, sensitivity, layout and HUD position are not here: players set those in /tdetector, and they persist in KVP.

Radar sources

Range

Raise detectionRange a long way and one officer with a radar on makes every detector on the map alert permanently.

Sensitivity and bands

bandRange composes with sensitivity rather than replacing it, so City reduces X and K on top of the band multiples.

False alerts

GPS lockouts

Lockouts are per client in KVP, so one player's MARK never quietens another's detector.

Alerting

The 3D detector prop

The box on the windshield, visible to everyone in and around the car.

A vehicle with no entry here and none saved in game gets no prop, and a car with no prop relays nothing to its passengers. /tdetectoredit is the easier route: in-game placements live in data.json and win over this table.

Access control

Two separate questions.

Who may use tDetector

Config.access = {
    mode = "everyone",   -- everyone | ace | job | item | custom

    ace  = "tdetector.use",              -- mode "ace"
    job  = { police = 0, mechanic = 2 }, -- mode "job": MINIMUM grade
    item = "radardetector",              -- mode "item"
    count = 1,                           -- how many of `item`; default 1

    custom = function(src) return false end,   -- mode "custom"
}

This is tLib's access module — frameworks, inventories and detection order are its documentation. A gate whose dependency is absent denies everyone and says so.

A player who does not pass cannot open /tdetector and is sent no radar data at all, both checked server-side on every request.

Who flips the switch

The toggle being greyed out is not the lock: the server also refuses to send radar data to a player not holding the item.

Wiring the QBCore item

Add the item to qb-core/shared/items.lua, drop radardetector.png into qb-inventory/html/images/, and restart tDetector. Using the item in a vehicle toggles the detector, identically to the /tdetector button.

['radardetector'] = {
  ['name']        = 'radardetector',
  ['label']       = 'Radar Detector',
  ['weight']      = 3000,
  ['type']        = 'item',
  ['image']       = 'radardetector.png',
  ['unique']      = true,
  ['useable']     = true,
  ['shouldClose'] = true,
  ['combinable']  = nil,
  ['description'] = 'We are not liable for your reckless driving.',
},

Without qb-core running, tDetector prints this and carries on:

[tDetector] Config.useAsItem is on, so the "radardetector" item is wired to the detector -- but qb-core is not running, so the item does nothing.

A missing or wrong setting

Nothing silently reverts. A scalar setting that is deleted, mistyped or unusable is replaced by its shipped default — all of them in TDET_DEFAULTS at the bottom of config.lua — and warned about once, naming the key, what was found and the line to paste back. Table-valued settings degrade per field, so deleting Config.bandRange.x leaves the other three bands untouched.

Next steps

• Integrating any radar — the per-entry shapes for Config.radarResources.
• Usage — what these values look like on the glass.