Supported Frameworks

MonoAdmin works with ESX, QBCore, Qbox and servers with no framework at all (standalone). The framework decides how much of your players’ data MonoAdmin can read and change: moderation, the map, reports and logs work everywhere, while jobs, money, items and characters need a framework. This page explains how MonoAdmin detects your framework, which versions it supports and what each framework gets.

How Detection Works

A framework is the roleplay base your server runs on. The MonoAdmin resource looks at which resources are started on your server and picks the first match in this order:

Order	Resource started	Framework
1	qbx_core	Qbox
2	qb-core	QBCore
3	es_extended	ESX
4	none of these	Standalone

Qbox is checked first because qbx_core also provides qb-core. Without that rule, every Qbox server would be mistaken for QBCore. If more than one of these is started, the first in the list wins.

The framework’s version is read from the resource’s own manifest. Along with the framework, the resource also looks for:

• an inventory resource: the first started of ox_inventory, qb-inventory, ps-inventory and qs-inventory,
• a database resource: the first started of oxmysql, mysql-async and ghmattimysql,
• the ambulance script that Auto-detect would use for Revive,
• the garage script (jg-advancedgarages) and the phone script (lb-phone), each with its version,
• whether voice and text mutes are possible.

Detection runs when the resource starts, and again about a second after your framework, oxmysql, an inventory, chat, pma-voice, an ambulance script, jg-advancedgarages or lb-phone starts or stops. So the start order in server.cfg does not matter much, and restarting a framework resource is picked up without restarting MonoAdmin. You can see the result in four places:

• the framework detected line in the server console, and monoadmin status,
• Settings > Server Link, under Detected framework,
• the guided setup’s What We Found on Your Server screen,
• the dashboard, if it differs from your project.

Your Choice and What Is Detected

You pick a framework when you create the project. MonoAdmin compares it with what the server reports. A feature is offered only when both agree it exists. The project’s choice sets the upper limit, and the server’s detection says what is actually there.

If they differ, you see:

• on the dashboard, The server runs a different framework, with an Open Settings button,
• in Settings > Server Link, “This project is set to {expected}, but the server reported {detected}.”,
• in the server console, the warning The panel is set to esx but this server runs qbcore. Change the framework in the panel's settings. on every connect, and in monoadmin status.

To fix it, correct the project’s framework under Settings > Overview, or use Switch to {framework} on the guided setup’s detection screen. Changing the framework hides pages and actions the new framework does not support. Nothing is deleted.

Supported Versions

Framework	Supported	Tested on a real server
ESX	1.13.5 to 1.16.0	1.13.5, 1.15.2 and 1.16.0
QBCore	No minimum is checked	1.3.0
Qbox	1.22.5 and later	1.22.5 and 1.24.0
Standalone	No framework needed	Yes

ESX and Qbox have a minimum; QBCore has none. If the server reports an older ESX or Qbox, the console warns with one of these lines:

• es_extended reports version {version}; MonoAdmin supports ESX 1.13.5 and later. Money, items and character edits may fail until ESX is updated.
• qbx_core reports version {version}; MonoAdmin supports Qbox 1.22.5 and later. Money, items and character edits may fail until Qbox is updated.

The dashboard and Settings > Server Link show the same notice. Nothing is switched off by the warning: those features are still offered, and they may fail on the older version.

ESX’s manifest reports a version one patch lower than the release on some tags (release 1.13.5 reports 1.13.4). MonoAdmin takes this into account, so a correctly installed 1.13.5 does not trigger the warning. Qbox’s manifest version is its release, so there is no such offset: a Qbox that reports 1.22.4 is older than 1.22.5.

For QBCore, MonoAdmin does not check a minimum version. The version in the table is the one it has been run against. Other versions are not blocked, but they have not been tested. A fork that keeps the resource names (qb-core, qbx_core, es_extended) is detected as that framework. How well it works depends on whether the fork keeps the original’s functions.

MonoAdmin as a whole is tested on server build 35245.

What Every Framework Gets

These work on all four setups, standalone included:

• Bans (including sticky bans), kicks, warnings, community service and mutes (see Voice and Text Mutes for what they need), with the local ban copy on your server
• Reports, the report command (/report unless you renamed it), and Discord tickets
• The live server map with player tracking, the Player Monitor, screenshots and profile pictures
• Server Logs for connections, kicks, staff actions, chat and commands
• Analytics for players, activity, entities, disconnects and crashes
• The in-game menu and the Game World Editor
• Player actions that need no framework: heal, freeze, teleport, shout, routing buckets, fun effects, and spawning, repairing, boosting and deleting a vehicle
• Announcements, server-wide cleanups, the entity list and entity map, and heal everyone

What Differs by Framework

Feature	ESX	QBCore	Qbox	Standalone
Set Job, Give Money, Take Money (online players)	Yes	Yes	Yes	No
Give Item (online players)	Yes	Yes, with ox_inventory or qb-inventory	Yes, needs ox_inventory	No
Revive	Through your ambulance script, or MonoAdmin’s own if none runs, or your own code with Custom	The same	The same	MonoAdmin’s own revive, or your own code with Custom
Character tab and Vehicles page (needs oxmysql)	Yes	Yes	Yes	No
Gang editing	No gangs on ESX	Yes	Yes	No
List of every job and gang a character belongs to	No	No	Yes	No
Inventory editing	Any inventory	ox_inventory or qb-inventory	ox_inventory	No
Economy and Jobs in Analytics	Yes	Yes	Yes	No
Item lines in Server Logs	With ox_inventory	With ox_inventory	With ox_inventory	No
Vehicles page that follows the garages and impounds of jg-advancedgarages	With jg v3	With jg v3	With jg v3	No
lb-phone’s number and Reset Lock on the Character tab	With lb-phone 2	With lb-phone 2	With lb-phone 2	No
Phone lines in Server Logs	With lb-phone 2	With lb-phone 2	With lb-phone 2	With lb-phone 2

On a standalone server, Settings > Features shows Not available on Standalone instead of a switch for Money, Items, Jobs and Character Editing.

The details of these rows are on Inventory Resources, Revive and Ambulance Scripts, Garage Scripts and Phone Scripts.

Standalone Notes

• The in-game menu’s own Revive row, under Self, is hidden on a standalone server, because there is no framework to revive through, unless Revive is set to Custom under Settings > Advanced. Then your own code does the reviving and the row appears. Reviving a player from the panel or from the players sheet works either way: with the default, None, it uses MonoAdmin’s own revive, which brings the player back in the game only, and with Custom it runs your code. See Revive and Ambulance Scripts.
• There are no jobs, money, items or characters to show, so the Character tab, the Vehicles page and the economy and job charts do not appear.

ESX Notes

• On ESX 1.16 and later, character edits are made inside ESX’s own persistence lock, which stops ESX’s save from undoing an edit. Older ESX versions do not have the lock, and edits go ahead without it.
• ESX has no gangs, so the gang editor does not appear.

QBCore and Qbox Notes

• Characters on both have a gang you can change.
• On Qbox, the Character tab also lists every job and gang the character belongs to.
• Qbox gives items through ox_inventory only.

Checking What You Have

To see exactly what your server can do, open Settings > Server Link for the detected framework, and the guided setup’s What We Found on Your Server screen for the inventory, database, ambulance, garage and phone scripts. If a page or button is missing, Troubleshooting lists the usual reasons.