Usage

Usage Guide

Core Navigation

• Opening the MDT: Use the configured command (default /mdt) or hotkey (default F6).

• Dashboard: View active dispatches, recent warrants, bolos, and your department's status at a glance.

• Search: Use the sidebar to search for Citizens (by name/ID) or Vehicles (by plate).

Records & Law Enforcement

• Citizen Profiles: View a citizen's licenses, owned vehicles, properties, and prior criminal record. You can also add notes or change their profile image.

• Incidents & Reports: Create detailed incident reports, link involved citizens, add evidence, and specify charges. Reports can be saved as drafts or submitted.

• Warrants & Bolos: Issue arrest warrants for citizens or BOLOs for vehicles. These will appear on the dashboard for all officers.

• Charges: Manage the penal code directly within the MDT (if permitted by rank).

Evidence System

• Collection: Pick up shell casings at crime scenes (requires an evidence bag). Casings store the weapon type and a unique identifier.

• DNA Lab: Process collected evidence in the DNA lab to link weapon shells to specific suspects.

• Evidence Locker: Store and manage all collected evidence items with detailed logs.

Medical & EMS Features

• Treatments: EMS can record patient treatments, including descriptions and vitals.

• Medications: Prescribe and track medications given to citizens.

• Blood Tests: Request and process blood samples to determine a citizen's blood type.

• Death Records: Document deceased individuals and the circumstances surrounding their death.

Department Tools

• GPS Codes: Set up common GPS coordinates for your department for quick dispatching and navigation.

• Outfit Codes: Save rank-specific uniform configurations to ensure all members are correctly dressed.

• Staff List: High-ranking members can view all department staff, their ranks, and manage employment (firing staff).

• Cameras: Access live CCTV feeds, vehicle dashcams, and officer bodycams (if the officer has the bodycam item active).

Configuration Usage (shared/config.lua)

The system is designed to be highly customizable. Here is how to configure key features:

• Command & Hotkey:

  Config.Command = "mdt" -- Command to open MDT
  Config.Key = "F6"      -- Hotkey to open MDT

• Phone Integration: Use Config.Phone = "lb" to integrate with lb-phone, or "none" for standalone usage.

• Department Setup: Provide unique themes and logos for each department under Config.TabletTypes.

  ["police"] = {
      title = "Police Department",
      primaryColor = "#69ffec",
      backgroundColor = "#0e1117",
      -- ...
  }

• Permissions: Define the minimum job grades required to perform specific actions in Config.Permissions. Setting a permission to true allows all ranks within that job to perform the action.

  ["police"] = {
      ["create_warrant"] = true,     -- All police ranks can create warrants
      ["delete_warrant"] = {3, 4}    -- Only ranks 3 and 4 can delete them
  }

• Auto Weapon Registration: Set Config.AutoRegisterWeapons = true to automatically fetch weapons and their serial numbers from players' inventories (supports ESX, QBCore, ox_inventory) and display them in the MDT along with database records.

• Items: If you utilize bodycams or vehcams as inventory items, define their item names here:

  Config.BodycamItem = "bodycam"
  Config.VehcamItem = "vehcam"

• Billing Integration: Configure your preferred billing script in shared/config.lua.

  Config.BillingScript = "auto" -- options: "auto", "esx_billing", "okokBilling", "tgg-billing", "codem-billing", "RxBilling", "none"
  Config.BillingAccount = "society_police" -- The account where the money goes

  The "auto" setting will attempt to detect established billing resources on your server.

Events & API

Unlike some other resources, aty_mdt manages most data operations internally without exposing public server/client exports. However, it listens to specific client events that you can trigger from other scripts (e.g., for usable items).

Usable Item Events (Client-Side)

If you have an inventory system that supports UseableItems (like QBCore or ESX), you can trigger the following events to open the bodycam or vehcam overlays when an item is used:

Toggle Bodycam UI:

TriggerEvent("aty_mdt:toggleBodycamItem")

Toggle Dashcam/Vehcam UI:

TriggerEvent("aty_mdt:toggleVehcamItem")

(Note: Ensure players have the corresponding job that allows usage of these cameras as defined in Config.CCTVJobs and Config.Permissions)

Developer & Customization Notes

The user interface is built using Vue.js (source code available in the web folder) and communicates with the game client via NUI Events.

• UI Source Code: Find the frontend source inside the web/ directory. (Use npm run build after making modifications)

• Escrow / Open Source: Core configuration (shared/*.lua), server getters (server/getters.lua), and open files (server/open.lua) are completely unescrowed for easy modification, allowing you to easily adapt database queries and framework checks to your server's specific needs.