Quasar Framework (qs-core) works with the tools a FiveM roleplay server already runs: txAdmin, oxmysql, ox_lib, pma-voice, Quasar Store's advanced inventory and the fuel, target, progress bar and vehicle key resources that ESX and QBCore scripts expect. This page lists every integration, how Quasar Framework detects it and the setting that controls it.
Most of it needs nothing from you. The txAdmin recipe installs the dependencies at tested versions, and the integrations switch on by themselves when the resource they talk to is started.
Overview#
Integration | Needed? | Installed by the txAdmin recipe |
|---|---|---|
txAdmin | Recommended — one-click install, admin rights, Heal revives | — |
oxmysql | Required by | Yes, |
ox_lib | Only for third-party scripts that use it | Yes, |
pma-voice | Recommended — proximity voice and the HUD voice indicator | Yes, |
Quasar Store advanced inventory ( | Optional, replaces | No (separate Quasar Store product) |
Fuel ( | Included | Yes, in |
Target, menu and input libraries | Only for third-party scripts that use them | No |
Progress bars ( | Included | Yes, in |
Vehicle keys ( | Included | Yes, in |
Society funds ( | Included | Yes, in |
Maps: |
| Yes, |
| Included | Yes, in |
Discord webhooks | Optional | Settings in the config files |
txAdmin#
Quasar Framework installs from txAdmin with a recipe and listens to txAdmin's Heal action. In txAdmin → Setup → Server Deployer, choose Remote URL Template and paste:
https://raw.githubusercontent.com/imnotquasar/qs-core/main/qs-recipes/recipe.yamlFeature | Detected from | What it changes | Setting |
|---|---|---|---|
One-click install | The recipe URL above | Imports the database ( | — |
Admin rights | txAdmin adds your identifier to |
|
|
Heal | txAdmin's | Heal on a player revives them from the downed state; Heal all revives every player with a loaded character. | — |
Spawn vehicle | Not hooked | The car has no keys, so |
|
Bans | Not hooked | Bans made in txAdmin are kept and enforced by txAdmin. Bans made with |
|
The full installation walkthrough is in Installation; admin rights, groups and bans are in Administration.
Quasar Store advanced inventory (qs-inventory)#
Quasar Framework ships its own inventory, qs-coreinventory. If you own Quasar Store's advanced inventory, qs-inventory, you can run it instead — every item operation of Quasar Framework, and of the ESX and QBCore bridges, then goes through it.
Part | Detected from | What it changes | Setting |
|---|---|---|---|
Quasar Framework core |
| Items given, removed and checked by Quasar Framework ( |
|
ESX bridge ( | The | Switches by itself: | Automatic |
QBCore bridge ( |
| Usable items registered by QBCore scripts are kept by the bridge for | Start order in |
Install qs-inventory
Install
qs-inventoryas its own documentation describes (items, images and its own settings).Replace the inventory in server.cfg
Replace the
ensure qs-coreinventoryline withensure qs-inventory, in the same place — afterqs-coreand beforeensure [bridge]:bash ensure qs-core ensure qs-inventory ensure qs-clothingLeave the core setting on auto
Keep
Config.Inventory = 'auto'in[core]/qs-core/shared/config.lua.Restart the server
Restart (not just the resource) so every resource picks the new inventory up.
ox_lib#
Detected from | What it changes | Setting |
|---|---|---|
Nothing — Quasar Framework does not use ox_lib. | The recipe installs ox_lib |
|
Keep it: a large share of ESX and QBCore scripts list ox_lib as a dependency. Remove it only if none of your scripts needs it.
oxmysql#
Detected from | What it changes | Setting |
|---|---|---|
| All database access. The recipe imports Quasar Framework's tables; the bridges create |
|
Third-party scripts that use oxmysql (MySQL.query, MySQL.insert, exports.oxmysql...) share the same connection. The tables are described in ESX & QBCore Compatibility.
pma-voice#
The recipe installs pma-voice 6.6.2 and starts it before qs-core.
Feature | Detected from | What it changes | Setting |
|---|---|---|---|
Voice settings | Convars in |
|
|
HUD talking indicator | GTA's talking state | The HUD voice icon lights up while you speak. |
|
HUD voice range | pma-voice's | When you cycle your voice range with pma-voice, the HUD shows the new mode. | — |
Fuel#
[bridge]/LegacyFuel is a LegacyFuel-compatible fuel resource. Scripts that call exports['LegacyFuel']:GetFuel(vehicle) or SetFuel(vehicle, fuel) work as they are.
Feature | Detected from | What it changes | Setting |
|---|---|---|---|
Fuel consumption | You drive a vehicle | Fuel drops once a second while the engine runs, faster at high RPM; at 0 the engine stops. A vehicle without a fuel value starts from its current GTA fuel level (or a random 45–85 if that is empty). | Tunables at the top of |
HUD fuel gauge | The resource named in the HUD config is started | The speedometer reads fuel from that resource's export; if it is not started, the HUD reads GTA's own fuel level. |
|
Garages | — |
| — |
To use a different fuel script, point Config.Vehicle.fuelResource and Config.Vehicle.fuelExport at its resource name and its getter export (one that takes the vehicle and returns a number). Stop the LegacyFuel bridge at the same time so fuel is not consumed twice — unless your scripts still call exports['LegacyFuel'], in which case pick a fuel script that answers under that name.
Target, menu and input libraries#
Quasar Framework's own resources do not need a target or menu library. Third-party scripts often do; install them as they are, the same way you would on ESX or QBCore, and ensure them after [bridge]:
Library | Typical users | Notes |
|---|---|---|
| ESX and QBCore scripts | Install as is. |
| QBCore scripts | Install both, as on QBCore. |
| QBCore scripts | Install as is. |
| ESX scripts that use | Registers the menu type that |
| Scripts built on ox_lib | Already installed (see ox_lib above). |
Progress bars#
Called through | Detected from | What it changes |
|---|---|---|
|
| Drawn with Quasar Framework's progress bar, with the animation, props and movement lock from |
|
| Same progress bar, with the animation and one prop. |
|
| Same progress bar. |
| Quasar Framework | The progress bar itself. |
A cancellable progress bar is cancelled with X. Scripts that use ox_lib's lib.progressBar show ox_lib's own bar.
Vehicle keys#
Called through | Detected from | What it changes | Setting |
|---|---|---|---|
|
| Forwarded to | — |
Built-in resources |
|
|
|
Keys, locks and hotwiring are explained in Vehicles.
Society and job funds#
Bridge | Used by | Stored in | Notes |
|---|---|---|---|
| ESX scripts that pay into or read society accounts |
| Exports |
| QBCore scripts that pay into or read job and gang funds |
| Exports |
The two are separate stores: money an ESX script puts in a society account is not visible in the qb-management fund of the same job. Quasar Framework's built-in resources do not use either, and paychecks are paid straight to each player's bank.
Maps#
Resource | Folder | Why it is there |
|---|---|---|
|
| Loads GTA Online interiors and map details (IPLs). |
|
| The Pillbox Hill hospital interior. |
Both are started by ensure [maps] in server.cfg, before [bridge]. Add your own maps to the same folder.
FiveM default resources#
Resource or setting | What it does with Quasar Framework | Setting |
|---|---|---|
| Installed from cfx-server-data into |
|
| Do not add it. Its automatic respawn fights Quasar Framework's downed state. | — |
FiveM's built-in | Replaced by |
|
Discord webhooks#
Logs are off until you paste a webhook URL. Each setting takes a Discord webhook URL; '' keeps it off.
Setting | File | What is posted |
|---|---|---|
|
| Cash handed over with |
|
|
|
|
| Present in the file; nothing is posted to it in this version. |
|
| Every action taken from the admin menu (F6) except Go to and Spectate, as one line: admin, action, target and detail. |
-- [core]/qs-core/shared/config.lua
Config.Webhooks = {
money = 'https://discord.com/api/webhooks/...',
admin = 'https://discord.com/api/webhooks/...',
connections = '',
}Building an integration of your own? Quasar Framework's exports and events — inventory, money, jobs, notifications, progress bar — are listed in Commands and Exports.
Frequently asked questions#
Do I need ox_lib for Quasar Framework?
No. Quasar Framework does not use it. The recipe installs it because many ESX and QBCore scripts list it as a dependency.
Can I use Quasar Store's qs-inventory with Quasar Framework?
Yes. Replace ensure qs-coreinventory with ensure qs-inventory in server.cfg; Quasar Framework and both bridges route items through it. Do not run both inventories at once.
Does Heal in the txAdmin menu revive downed players?
Yes. txAdmin's Heal revives the player from the downed state, and Heal all revives every player with a loaded character.
Which fuel script does the HUD read?
LegacyFuel by default — the compatible fuel resource in [bridge]. Change Config.Vehicle.fuelResource and Config.Vehicle.fuelExport in [core]/qs-corehud/config.lua to read another script's fuel export.
Do I need qb-target or ox_target?
Not for Quasar Framework itself. Install the target library a third-party script asks for, as it is, and start it after [bridge].
Why does the hospital look empty?
hospital_map is not running. Make sure it is in [maps] and that ensure [maps] is in server.cfg.



