Supported frameworks: ESX, QBCore, Qbox
Automatic or fixed framework, what Agora reads in each framework, how a player is recognised, and the start order to follow in server.cfg.
Updated on Sep 27, 2026, 12:03 p.m.
On this page
In short. Agora works with ESX, QBCore and Qbox. The framework is set in Server → Database: Automatic by default, or fixed by hand. The agora resource must start after the framework, and OneSync must be on.
Automatic or fixed #
Automatic is the default on a new installation. Agora then finds the framework by cross-checking two sources:
- what the in-game resource reports when it starts (it checks whether
qbx_core,qb-coreores_extendedis running); - the tables in your database:
users.identifierfor ESX,players.citizenidfor QBCore and Qbox. Qbox is recognised byplayer_groups, or by theplayers.userId→users.userIdjoin.
Under the Framework dropdown, the screen says what is detected right now and where it comes from: "Detected: QBox (reported by the in-game resource)" or "… (from the database tables)". The Test button says it too. Detection runs again when you save or test the connection, when the resource reports a different framework, and otherwise at most every 10 minutes: Agora never polls your database.
When detection cannot decide, Agora does not guess. The screen shows "Not detected: …" with the reason, the MDT, the live map and the portal read no characters (the forum is not affected), and the failure reaches Administration → Errors.
| Reason shown | What is going on | What to do |
|---|---|---|
| "…neither the ESX tables nor the QBCore/QBox ones…" | Wrong database, or the framework tables are not imported yet | Check the database name, import the framework SQL |
| "…both the ESX tables and the QBCore ones…" | The database keeps two frameworks' tables and the resource has not reported yet | Start the game server with the resource (its report decides), or fix the framework |
| "…the in-game resource reports QBox, but the database only holds the tables of the ESX framework…" | The connection points at another server's database | Fix the database, or fix the framework |
| "…the game server database is not responding…" | Database unreachable, and the resource has not reported yet | See Game database unreachable |
Fixing the framework (ESX, QBCore or Qbox) turns detection off: Agora reads that framework, full stop. An installation that had already saved a framework keeps it after the update; nothing changes until an administrator sets the dropdown back to Automatic and saves. The in-game resource follows the same setting.
What Agora reads #
| Framework | Characters | Jobs and ranks | Vehicles | Licenses |
|---|---|---|---|---|
| ESX | users | jobs and job_grades tables | owned_vehicles | user_licenses table |
| QBCore | players | deduced from characters, jobs table if present, or jobs.lua | player_vehicles | character metadata |
| Qbox | players and users | players, player_groups, or jobs.lua | player_vehicles | character metadata |
Multi-jobs (player_groups) are supported. Agora adapts to databases that lack some columns.
In QBCore and Qbox, jobs are declared in Lua: without a panel or SFTP, only jobs already held by a character show up. Connect the panel or SFTP to read jobs.lua and get the full list.
How a player is recognised #
By their FiveM license (license: or license2:), which Cfx guarantees, once they have linked their game with a code. The discord: identifier the FiveM client announces is not enough: nobody checks it.
- ESX:
identifier(with or withoutchar1:, with or withoutlicense:). - QBCore and Qbox:
players.license.
The player still needs Discord linked to FiveM: without a Discord identifier, the tablet does not open.
Order in server.cfg #
ensure qbx_core # or qb-core, or es_extended
ensure agoraOn Automatic, the resource detects the framework when it starts: it must already be running when ensure agora runs. If none is running, the console shows "framework: no framework detected".
If the fixed framework is not running, the console says so at startup: "framework: qbox configured but qbx_core missing — the live map and the MDT will have no characters". Start the framework before ensure agora, or set the dropdown back to Automatic (or pick the right one) in Server → Database.
OneSync #
ESX Legacy, recent QBCore and Qbox already require OneSync. With it, the server reads positions for the live map. Without it, the console says so in yellow and clients send their own position, only while a map is open. Turn it on (onesync on) so that clients send nothing.
A server without a framework #
The resource still works: the live map shows players by their FiveM name, in grey. The MDT has no characters to read. Leave the framework on Automatic: the "… configured but … missing" warning no longer comes back at every start, the console only notes "no framework detected".
Was this article helpful?
Related articles
- Connect the game server databaseThe MDT reads your FiveM server's real database: create a dedicated MySQL user, reachable from Agora, then fill in Server → Database.
- Install the agora FiveM resourceThree ways to drop the resource in: one click through the panel, over SFTP, or the zip placed by hand; always named agora, after the framework.
- The live map: permissions, on duty, multi-job, OneSyncLive player positions for staff, and for on-duty colleagues of the same job if you open it; almost no cost for the game server.
- Troubleshoot the FiveM resourceNo signal, secret refused, OneSync missing, blank tablet, framework not found: the console messages and their fix.