Guides5 min read
5CODE Recognition requirements and supported frameworks
Will Recognition start on your server? This guide answers that before you buy. It covers the frameworks, the four requirements, what each optional resource unlocks, and the limits worth knowing first.
Patrick MiddlemanPublisher at 5CODE
- Published
- Last updated

On this page9
The short answer
Recognition supports QBCore, Qbox, ESX Legacy and Standalone, and the framework is auto-detected. A server needs four things to run it: FXServer build 7290 or newer, OneSync (legacy or infinity), oxmysql, and MySQL 8.0+ or MariaDB 10.4+.
Everything else is optional. An inventory, a voice system, an appearance script, an ambulance job, a police job and an MDT each unlock one part of Recognition, and the script runs without any of them. The rest of this guide goes through the requirements one by one, down to the limits worth knowing before you buy.
Which frameworks does Recognition work with?
Four are supported, and a fifth has an editable starting point.
| Framework | Resource | Support | Worth knowing |
|---|---|---|---|
| Qbox | qbx_core | Supported | Detected first, because it also provides the qb-core name |
| ESX Legacy | es_extended | Supported | ESX reuses character slots. A new character in a reused slot always starts clean |
| QBCore | qb-core | Supported | Nothing extra to install |
| ox_core | ox_core | Stub | An editable branch in the open bridge folder. Check it against your ox_core version |
| Standalone | none | Supported | No framework at all. One character per license, and items are kept by the script |
With Config.Framework = 'auto', the script picks the first of those that is running, in that order. You can also pin your framework. Qbox and ESX each have one extra install step.
The labels are the ones the docs use for every resource:
- Supported: ships with its own adapter and is selected automatically.
- Stub or snippet: an editable branch in the open
bridgefolder, or a one-line snippet you paste into your own file. - Detect only: the script notices that the resource is running and adjusts to it, nothing more.
What does a server need before installing it?
Four things, and none of them depends on your framework:
- FXServer build 7290 or newer. Older builds refuse to start the resource.
- OneSync, legacy or infinity. With OneSync off, FXServer never starts the resource.
set onesync oninserver.cfgfixes it. oxmysql. It must start before Recognition, and it is required even on a standalone server.- MySQL 8.0+ or MariaDB 10.4+. The tables install themselves on the first start.
Start Recognition after everything it works with, so that auto-detection can find them at boot:
set onesync on
ensure oxmysql
ensure ox_lib # optional
ensure qbx_core # or qb-core / es_extended / nothing (standalone)
ensure ox_inventory # your inventory
ensure pma-voice # your voice system
ensure illenium-appearance
ensure 5code-recognitionKeep the folder name 5code-recognition. Other scripts call its exports by that name, and renaming the folder breaks them.
What is optional, and what does each resource unlock?
Each row of this table unlocks one part of the script. None of them is required.
| Area | Supported | What it unlocks |
|---|---|---|
| Inventories | ox_inventory, qs-inventory, qb-inventory v2, jaksam_inventory, tgiann-inventory, ak47_inventory, origen_inventory, codem-inventory, core_inventory, ESX default | The five items. Without an inventory, the script keeps them itself |
| Voice | pma-voice, SaltyChat, YaCA, Native Mumble | The voice cue. Only pma-voice can also make the voice changer audible |
| Appearance | illenium-appearance, 17mov Character System, rcore_clothing, qs-appearance, tgiann-clothing, fivem-appearance, qb-clothing, esx_skin | The face editor used by the implant clinic, and "outfit changed" hints |
| Ambulance | qbx_medical, qb-ambulancejob, esx_ambulancejob, wasabi_ambulance_v2, randol_medical, ars_ambulancejob | Telling a revive from a respawn for the New Life Rule |
| Police and MDT | qbx_police, qb-policejob, esx_policejob, wasabi_police_v2, lb-tablet, tk_mdt, redutzu-mdt | Cuff, rob, search and escort proofs, and camera reports and witness statements sent to the MDT |
Every entry in this table is marked Supported in the docs. The compatibility matrix (opens in a new tab) lists more resources, some of them with the labels Stub, snippet or Detect only, so look up the exact resource you run.
Three things need no extra resource at all. Clothing is read from the game itself. Paper reports always work, with or without an MDT. And Recognition always uses its own HUD, which players can move and resize; it works alongside JG HUD.
ox_lib is not required either. It is only used if you pick it for notifications, the text UI or the progress bar.
The five items
Recognition adds five items: voice_changer, hidden_camera, magnetic_scanner, recognition_battery and recognition_report. Your inventory needs a definition for each, and the docs have paste-ready definitions per inventory. If one is missing, the rest of the script keeps working; only the missing items cannot be given out.
Do ESX and Qbox need an extra step?
Yes, one each, so that a deleted character's recognition identity goes with it:
- Qbox: add one entry to a list in the server config of
qbx_core. - ESX: import the script's SQL file once by hand before the next start. That is the way the docs recommend.
- QBCore: nothing to install.
Both steps are in the install guide (opens in a new tab). A server that runs 0R Multicharacter v3 has a step of its own in the same guide.
Who gets the admin panel?
Staff open the in-game admin panel through a permission, set in server.cfg:
add_ace group.admin recognition.admin allow
add_principal identifier.license:YOUR_LICENSE_HERE group.adminLighter staff roles do not need the whole permission. Each can get one of its child permissions instead: view, edit, export, classifier, identity or settings.
What are the limits?
Five things are better known before the purchase than after it:
- It records; it does not block. Recognition does not stop a player from shooting someone their character does not recognize. On aim, damage, kill, cuff, rob or search, the server logs what the attacker's character knew, and your staff get that record. The roleplay decision stays with you.
- The audible voice changer needs pma-voice. On every other voice system the device still feeds scans a fake voice. It just sounds like the wearer's normal voice to other players.
- English is the only language included. Every text is in an open locale file, so a translation is a translated copy of that file.
- Printing a camera recording needs the F3 menu. It is not available when scans start from a target option or a prompt instead.
- New clothing packs need an Auto-scan. After you install an EUP or addon clothing pack, run the admin panel's clothing Auto-scan. Until then, unknown items are treated on the safe side: an unknown mask covers the whole face.
What does it cost, and what happens on an update?
Recognition is €30, one-time. The current version is 1.0.1, released on 2 October 2026.
Four parts of the resource stay open and are yours to edit: config.lua, config_server.lua, the locale files and the bridge folder. Everything else is replaced on an update, so back those four up first. Every release that changes an open file says so in the changelog (opens in a new tab), so you can merge your edits.
The public docs have 81 pages for Recognition, among them the install guide, a 5-minute first test and the compatibility matrix.
Where to go next
To see what the script does once it runs, read how character recognition works: the scan, the four cues, disguises and what staff can see. The script's page shows the admin panel, with its pair view, lookup, timeline and live settings.
If your police department also needs an armory, how to set up police loadouts per unit goes through 5CODE Loadouts the same way.




