GPS Tracker

Overview

The GPS Tracker resource gives law enforcement, mechanics, and civilians the ability to attach temporary trackers to vehicles or players. When a tracker is active, the script broadcasts a blip on the map so authorized jobs can monitor the target in real time.

This page summarises the typical setup for the resource and highlights common integration points when running it alongside other QBCore systems.

Key Features

• Item-based deployment with configurable job or gang restrictions
• Real-time map blips that refresh on a configurable timer
• Support for multiple active trackers with automatic cleanup when a target disconnects or the timer expires
• Optional command support (e.g., /tracker or /gps) so staff can place or remove devices manually
• Client and server event hooks for integrating with dispatch, evidence, or notification systems

Requirements

• QBCore Framework (latest stable build)
• qb-core/shared/items.lua access so you can register the tracker item
• Inventory resource (qb-inventory, lj-inventory, etc.) for distributing the tracker item
• Dispatch/notification script (optional) if you want alerts when a tracker is planted or removed

Installation

1. Download the resource archive from the developer’s repository or release post.

2. Extract the folder (commonly named qb-gps or gps-tracker) into your server’s resources/[qb] directory.

3. Add the resource to server.cfg after the core QBCore resources:

   ensure qb-core
   ensure qb-target     # Optional, only if you use target interactions
   ensure gps-tracker

4. Register the tracker item in qb-core/shared/items.lua:

   ['gpstracker'] = {
     ['name'] = 'gpstracker',
     ['label'] = 'GPS Tracker',
     ['weight'] = 100,
     ['type'] = 'item',
     ['image'] = 'gpstracker.png',
     ['unique'] = true,
     ['useable'] = true,
     ['shouldClose'] = true,
     ['combinable'] = nil,
     ['description'] = 'Allows you to keep tabs on a vehicle or person.'
   },

5. Import any SQL that ships with the download (usually optional; the tracker often stores data in memory).

6. Restart the server and use the tracker item in-game to verify that blips appear for the correct jobs.

Configuration Highlights

Open config.lua (or shared/config.lua, depending on the release) to fine-tune behaviour:

• AllowedJobs: Restrict usage to police, mechanic, or custom job names.
• TrackerDuration: Set how long a device remains active before expiring.
• RefreshRate: Control how often blips update on the map.
• UseItem: Toggle whether a physical inventory item is required or if the tracker is command-based.
• NotificationEvents: Define which notification export is used (qb-core notify, okokNotify, ps-dispatch, etc.).

Remember to restart or ensure gps-tracker after configuration changes.

Usage Tips

• Give trackers to relevant jobs through shops, duty lockers, or crafting benches.
• Pair the script with dispatch systems so officers receive a call when a tracker is planted or destroyed.
• Consider logging tracker placements via server events for moderation or evidence review.
• Use the script’s remove command or export when a vehicle is impounded so blips do not linger.

Troubleshooting

Additional Resources

• Review the README packaged with the download for change logs and migration notes.
• Join the QBCore community Discord to receive release announcements and support from the original maintainer.
• Test the tracker on a staging server before deploying it to production to avoid conflicts with custom vehicle scripts.