QBCore Police Resource

SpectiveMDT

Website-backed MDT bridge for QBCore with personal and cruiser MDT interfaces, dispatch tooling, radar, lidar, spikes, station utilities, and API-linked officer records.

Version 1.0.0
Author Spective Scripts

Dependencies

qb-corescreenshot-basic (optional)qb-target (recommended)matching inventory item definitions

Commands / Entry Points

/smdt/smcar/smpanic

Install

Installation Flow

  1. Place the resource in your server resources folder.
  2. Ensure qb-core before the script.
  3. Add ensure spective_mdt to server.cfg.
  4. Set spective_mdt_api_base_url to your live website or API path.
  5. Set spective_mdt_api_key to the plaintext workspace API key from the website.
  6. Optionally install screenshot-basic and set spective_mdt_public_url if player uploads need a public endpoint.
  7. Verify allowed jobs, dispatch jobs, stations, armory items, and photo booth settings in config.lua.

Database

SQL Requirements

This resource does not ship local SQL in this repository because it expects a separate website/API stack. You still need the correct API base URL and workspace key in server.cfg so the in-game resource can talk to the website side.

The bundled install.sql in this site includes the SQL required for both the docs CMS and the pet tables used by this project.

Features

Feature Overview

  • Personal MDT and cruiser MDT workflows backed by a website API.
  • Records for citizens, vehicles, dispatches, warrants, incidents, and BOLOs.
  • Radar, lidar, spike strips, evidence lockers, armory interactions, and duty points.
  • Manual website presence sync and QBCore-backed officer profile data.

Configuration

API and Website Requirements

This resource is only one half of the system. It expects a live website/API where workspaces and records are stored.

  • Set spective_mdt_api_base_url to your public website or API path.
  • Set spective_mdt_api_key to the plaintext workspace key for the correct workspace.
  • If screenshot uploads come from player clients, use a publicly reachable URL with spective_mdt_public_url when the API host is not directly reachable by players.

The in-game script will still function against the wrong key, but it will read and write records to the wrong workspace, so key management matters.

Troubleshooting

Operational Notes

  • If the resource cannot connect, recheck the API base URL and workspace API key in server.cfg.
  • If officers do not appear on the website, make sure they clicked Go online from inside the MDT.
  • If the armory workflow breaks, verify the item names match your live inventory system.