Overview
Cylex MDT is a premium police MDT built from the ground up for modern FiveM roleplay servers. Every page is reactive — changes made by one officer propagate to all others instantly via delta broadcasts, with no full-page reloads. The UI is built in Vue and ships with a fully configurable dark theme.
Framework, inventory, phone and housing integrations are all auto-detected — drop it in, configure your departments, and you’re done.
Pages & Features
Dashboard
The home screen. Shows announcements, on-duty officers and a live activity feed. Department supervisors and bosses can post pinned announcements directly from the dashboard.
Incidents
Create and manage police reports. Each report supports:
-
Multiple suspects (with warrant flags), victims, witnesses and attached officers
-
Incident type, narrative, and evidence attachments
-
Status tracking (open / pending / closed)
-
Department lock — optionally restrict edits to departments already attached to the report
BOLOs & Warrants
Issue and manage:
-
Arrest warrants, search warrants, vehicle search orders, eviction orders, detention orders
-
Warrant timers — configurable countdown that can run offline or only while the suspect is online
-
Expired warrants are automatically hidden from the active BOLO view
Units
Create and manage patrol units in real time. Officers can join/leave units, and all changes sync instantly to every open MDT.
Officers
Full officer directory with ranks, department affiliation, duty status (green dot = online, badge = on duty) and profile management. Changes like rank assignments sync live to every client without a full list reload.
Citizens
Server-wide citizen database. Search by name, identifier or license plate. View licenses, past incidents, notes and vehicle history.
Vehicles
Vehicle registration lookup. Attach strike points (configurable max), link to incidents, and flag as stolen or wanted.
Weapons
Weapon registration database with serial number tracking. Supports all standard GTA weapon hashes — easily extended.
Charges
Custom charge library. Each charge has:
-
Category (Violent Crimes, Drug Offenses, Traffic, etc.)
-
Felony class (Infraction → Class A Felony)
-
Fine amount and sentence length (used to auto-sum warrant timers)
Notes
Internal officer notes — private memos or shared department notes.
/kfb5odiFwFkWK2eUOVwJRtbE8vd.jpeg)
FTO Notes
A structured Field Training Officer evaluation system built into the MDT.
FTO officers create a report per trainee that covers the full training period. Each report includes:
-
Candidate & reporter — trainee name, reporting FTO, training start and end dates
-
Evaluation sections — separate fields for positive observations, areas needing improvement, general notes and private officer notes
-
Scores — per-category scoring stored on each report (e.g. driving, communication, use of force)
-
Status tracking —
Under Evaluation→Successful/Failed
Reports are department-scoped — each department only sees their own trainees. An officer’s FTO status is also visible on their profile page, so supervisors can see at a glance who is qualified to train.
Exams
A full written exam system for officer testing and certification — built entirely inside the MDT.
Supervisors or FTO officers create an exam with:
-
Title & description — context for what the exam covers
-
Questions — mix of multiple choice (auto-graded) and open-ended (manually reviewed) questions, each with a configurable point value
-
Participants — specific officers assigned to take the exam
-
Reviewers — officers who can read submissions and grade open-ended answers
Once published, assigned officers see the exam in their list and can submit their answers directly from the MDT. After submission:
-
Multiple choice answers are scored automatically
-
Open-ended answers are reviewed and graded by the assigned reviewer
-
The creator can mark the submission as Passed or Failed and leave a reviewer note
-
Submissions can be cleared and the exam re-used for a new round
Exams are department-scoped so each department manages their own pool independently.
Forensics
Manage evidence collected in the field. Link evidence bags to incidents directly from the MDT.
Live Map
Real-time map of on-duty officers.
Supports department-scoped view (each department only sees their own officers) or a shared cross-department view. The map snapshot loop only runs while at least one officer has the page open — zero performance cost when nobody is watching.
Analytics
Department statistics dashboard (boss / supervisor access only). Covers incident counts, warrant clearance rates, officer activity and more across 7d / 30d / 90d / 365d ranges.
Rank Permission Manager
Granular per-rank access control for every MDT page. Bosses can manage permissions in-game through a dedicated UI. All permission changes sync live to every connected officer.
Roster
Chain of command editor. Drag-and-drop rank ordering, boss-only access.
Logs
Activity log with configurable retention (default 30 days). Every MDT action (report created, BOLO issued, rank changed, etc.) is recorded with the officer’s name and timestamp.
Uniforms, Codes, Tags, Templates
Department-scoped management pages for uniform definitions, 10-codes / radio codes, custom record tags and report templates.
Automatic Duty Time Tracking
Script silently tracks how long each officer spends on duty — no extra commands, no manual logging.
How it works:
-
When an officer goes 10-41 (on duty), a server-side timer starts automatically
-
When they go 10-42 (off duty), change job, disconnect, or the resource restarts, the elapsed seconds are flushed to the database and accumulated into their lifetime duty total
-
The counter is tied to the framework’s own
/dutytoggle — it just works, with no extra setup
Where you see it:
-
Officers page — each officer’s profile shows their total accumulated duty time
-
Analytics dashboard — a Top Duty Hours leaderboard ranks officers by time served, giving supervisors a clear picture of who’s putting in the most hours
The timer survives crashes and resource restarts cleanly — partial sessions are saved the moment they end, so no time is ever lost.
Evidence System
A standalone physical evidence layer that ties into the MDT:
-
Blood Evidence — Drops at hit location with configurable spawn chance and per-player cooldown
-
Bullet Casings — Scatter around the shooter with a configurable spread range; optionally spawn a 3D prop
-
Flashlight Mode — Evidence is only visible while the officer holds
weapon_flashlight+ RMB — pure realism -
Evidence Bags — Requires
empty_evidence_bagitem to collect; yieldsblood_evidenceorcasing_evidence -
Processing Lab — Officers bring bagged evidence to a lab location; processing takes a configurable time and produces
processed_evidence -
Evidence Stashes — Drop-off points at configurable police station coords
-
Auto-Cleanup — Uncollected evidence disappears after a configurable number of minutes
| Exempt Jobs | Officers / EMS / Ambulance can be excluded from leaving blood & bullet |
Discord Webhook Logging
Every MDT action can be forwarded to a Discord channel via webhook:
-
Incidents, BOLOs, Citizens, Vehicles, Weapons, Charges, Notes, FTO, Exams, Units, Uniforms, Templates, Tags, Permissions, Announcements, Evidence
-
Each category gets its own webhook URL — or falls back to a single
systemchannel -
Embeds include officer name, action type and relevant record data
Theme & Customization
The entire color palette is defined in config.lua and injected at runtime — no need to rebuild the UI. Players can also personalize their own accent colors from an in-game settings panel (toggle-able by the server owner).
Compatibility
Frameworks
QBCore · ESX · QBox · Custom — auto-detected
Databases
oxmysql · ghmattimysql · mysql-async
Inventories
ox_inventory · qb-inventory · qs-inventory · esx_inventory · custom — auto-detected
Phones
cylex_phone · gksphone · high-phone · lb-phone · npwd · okokPhone · qs-smartphone · qs-smartphone-pro · roadphone · yseries — auto-detected
Housing
ps-housing · quasar-housing · loaf_housing · bcs_housing · nolag_properties · custom · none — auto-detected
Multi-Department
Ship with as many departments as you need — each with its own:
-
Short name, full name and job name mapping
-
Accent color
-
Logo image
Departments can be fully isolated (DepartmentScopedData = true) or share data across each other.
Default departments included (ready to use or rename):
MRPD · VPD · PBSO · Davis Sheriff · BCSO · SDSO · Park Rangers · State Police
Performance Notes
-
Delta broadcast system — server pushes only changed records to clients; no full-list refetch on every action
-
Chunked transfer — large data payloads are split server-side and reassembled client-side transparently
-
Live Map runs its snapshot loop only while at least one client has the page open
-
Analytics is built once on resource start; no periodic background queries
-
Log cleanup runs once on start then every 24 hours
Locales
English (en) and Turkish (tr) included out of the box.
All UI strings are in editable/locales/.
Open / Editable Files
Everything you need to configure lives in the editable/ folder and is not escrow-protected:
editable/
├── config.lua ← Main config (departments, pages, theme, keybind…)
├── evidence_config.lua ← Evidence system config
├── sv_config.lua ← Discord webhooks
├── client_open.lua ← MDT open/close logic (fully editable)
├── locales/ ← Translation files
└── framework/ ← Framework / phone / housing / inventory bridges
Dependencies
-
A supported database resource (
oxmysqlrecommended) -
A supported framework (QBCore, QBOX or ESX)
-
FiveM server build 5104 or newer
Youtube Preview
Purchase
%20 DISCOUNT FOR LIMITED TIME
Extra %20 discount with bundle!
| Code is accessible | Escrow |
| Subscription-based | No |
| Lines (approximately) | 5000 |
| Requirements | QBCORE / QBOX / ESX |
| Support | Yes |