FiveM Common Errors & Fixes — Quasar Framework (qs-core) | Quasar Store

FiveM Common Errors & Fixes — Quasar Framework (qs-core) | Quasar Store | Quasar Store

The database does not connect, or a table does not exist

If [qs-core] Database connection established. never appears, oxmysql could not reach your database. Check the line written by txAdmin (or by you on a manual install):

bash

set mysql_connection_string "mysql://user:password@localhost/database?charset=utf8mb4"

The user, password, host and database name must be correct and MySQL 8.0+ or MariaDB 10.4+ must be running. An error such as Table 'database.players' doesn't exist means the schema was never imported: the recipe does it for you, but on a manual install you import [core]/qs-core/sql/qscore.sql yourself. It creates players, bans, player_colors, player_groups, vehicles, the inventory tables and the banking tables; the ESX bridge creates users and owned_vehicles on its own.

The interface stays in English

Set the language with setr, not set:

bash

setr qs:locale "es"

setr replicates the value to every player. With a plain set, server messages change language but the client side — HUD, inventory, menus, notifications — keeps English. Valid codes are en, es, fr, de, it, pt, pl, ru, tr and ar; anything else falls back to English. Restart the server after changing it. Third-party ESX and QBCore scripts keep their own language settings.

Admin commands say "No permission."

qs-core admin commands check the ACE command.qs of the player who types them. Two things must be true:

server.cfg grants it to the admin group: add_ace group.admin command allow (the recipe writes this line).
The player is in group.admin. txAdmin adds its master account automatically; add other admins with add_principal identifier.fivem:<id> group.admin in server.cfg, or type setgroup <id> admin in the server console.

The player can check it right away — /setgroup applies the group at once and the player gets . uses the ACE , which the same line covers.

The F6 admin menu says "You are not allowed to use this"

The menu uses the same permission as the admin commands (Config.Permission = 'command.qs' in qs-admin/config.lua). Fix it exactly as for No permission. above.

/setgroup does nothing, or the console shows "Access denied for command add_principal"

setgroup and removegroup answer in the server console, not in chat: use them from the console or check its output ([qs-core] Usage: setgroup <serverId> <group> means an argument is missing). A player without command.qs gets no reply at all. qs-core applies groups by running add_principal / remove_principal, so server.cfg must allow the resource to do that:

bash

add_ace resource.qs-core command.add_ace allow
add_ace resource.qs-core command.remove_ace allow
add_ace resource.qs-core command.add_principal allow
add_ace resource.qs-core command.remove_principal allow

A removed admin still has admin rights

/setgroup <id> user or /removegroup <id> removes the group saved by qs-core immediately. A principal written in server.cfg (add_principal identifier.… group.admin) cannot be removed by a command — delete that line and restart. txAdmin's own admin accounts are managed in txAdmin.

A moderator or superadmin cannot use the admin commands

/setgroup <id> mod puts the player in group.mod, which only has the permissions server.cfg gives it. Grant it the admin commands with add_ace group.mod command.qs allow, or use admin as the group.

"You have reached the character limit."

The limit is enforced by Config.MaxCharacters in qs-core/shared/config.lua (default 5). qs-coremulticharacter/config.lua has its own Config.MaxCharacters, which only sets how many slots the selection screen shows. Change both to the same number and restart.

The loading screen never closes, or the screen stays black

The loading screen is closed by the character selection (or by the intro when it plays), with an automatic fallback 12 seconds after the player spawns. If it stays up or the screen stays black, check in order: qs-coremulticharacter is started; the server console shows Database connection established. (without the database the character list never arrives); F8 shows no script errors; and the ensure order is the one from the recipe.

Closing the character creator still created the character

Leaving the creator confirms the character with the appearance it had at that moment. Nothing is lost: change the look later at any clothing store or barber, or delete the character from the selection screen and create it again.

A player reconnects and is still downed

The downed state is saved with the character, so logging out does not escape it. After 20 seconds the player can press E to respawn at the nearest hospital, or press G to call EMS. Admins can use /revive <id> or the Heal button in the txAdmin menu, which also revives.

A character has no clothes or the default look

Appearance is applied by qs-clothing when the character loads, so it must be started (it is in [core]). In the editor, Cancel or Esc discards the changes; only Save keeps them. A character created while qs-clothing was not running has no saved appearance — open a clothing store, or let an admin use /clothing.

Money, items or positions went back after a crash

Characters are saved every 5 minutes (Config.SaveInterval), when a player disconnects or logs out, and when qs-core stops. If the server process crashes, changes since the last autosave are lost. Lower Config.SaveInterval in qs-core/shared/config.lua if you want more frequent saves.

Changes made in the database are undone

Online characters live in memory and are written back on every save, so an SQL edit to players while the player is online is overwritten. Edit characters while they are offline, or use the commands (/addmoney, /setjob, /giveitem) and exports for online players.

The inventory does not open

The inventory and the item wheel do not open while you are downed — that is intended, and dying closes them. Otherwise check the key: F1 by default, but every player can rebind it in Settings → Key Bindings → FiveM, and a player who bound inventory to another key keeps that key.

An item shows "Not usable", or nothing happens when it is used

For an item to do something it needs two things:

Its definition has useable = true (exports['qs-core']:RegisterItem('pizza', { label = 'Pizza', weight = 500, useable = true })). Without it the inventory shows Not usable.
Something handles it: exports['qs-core']:RegisterUsableItem(item, handler), an ESX ESX.RegisterUsableItem / QBCore QBCore.Functions.CreateUseableItem, or a listener on qs:server:usedItem. Food and drinks are handled by qs-needs once they are listed in NeedsConfig.Consumables.

The inventory never removes a used item by itself: a consumable handler must remove it. Items are also briefly blocked while a progress bar runs or after many uses in a row.

An item does not appear in a shop

Shops hide products whose item is not in the catalogue. Register the item first (with RegisterItem, or through the resource that adds it) — icepack and burn_cream, for example, only exist while qs-ambulance is running.

"Too heavy to carry" or "Inventory full"

Players carry up to 50 kg (Config.MaxWeight = 50000 grams) in 30 slots (Config.Slots), set in qs-coreinventory/shared/config.lua. Weapons and unique items take a whole slot each; other items stack to 64 unless their definition sets stack.

The weapon disappears when the item is dropped, given or stored

That is intended: weapons are items, and when the last item of a weapon leaves your inventory — dropped, given, moved to a trunk or stash, sold — the weapon is taken from your hands too. Note that dropping an item destroys it; give it to a player or put it in a stash to keep it.

Grenades and other throwables disappear one by one

Intended: each throwable you throw uses one item, and the number you can throw always matches the number of items you carry. Throwables stack to 10.

"You have no weapon that takes this ammo"

Ammo items load the weapon in your hands if it matches, otherwise the first weapon of that category you carry: ammo_pistol for pistols, ammo_smg for SMGs, ammo_rifle, ammo_shotgun, ammo_sniper, ammo_mg and so on. Equip a weapon of the right category first. Melee weapons and throwables use no ammo.

A weapon given from the admin menu or by a script is gone after reconnecting

The admin menu's Give Weapon and ESX xPlayer.addWeapon give the ped a game weapon, not an item, so it is not saved. Give the weapon item instead: /giveitem <id> weapon_pistol 1, or AddItem / xPlayer.addInventoryItem from a script.

The trunk or glovebox does not open

The vehicle is locked or you have no keys means exactly that: the trunk needs the vehicle unlocked and its keys, and the glovebox needs the keys. Open the inventory on foot right behind the vehicle for the trunk, or from a seat for the glovebox.

I installed Quasar Store's qs-inventory but the basic inventory still opens

qs-core always uses qs-coreinventory while it is started. Run qs-inventory instead of it: remove ensure qs-coreinventory from server.cfg and ensure qs-inventory before [bridge]. The console line [qs-core:warn] Inventory backend not available means neither inventory is running.

"You need keys to drive this" and the engine turns off

A driver without the vehicle's keys cannot start it (Config.RequireKeysToDrive). Owned vehicles give you their keys automatically the first time you sit in the driver seat, and so do cars from the dealership, a garage, /car and the admin menu. For any other vehicle: share keys with /givekeys, let an admin use /adminkeys, or hotwire it. Keys are kept for the session, so after reconnecting owned cars hand them out again when you get in.

Hotwiring does nothing

Hotwiring (G) only works in the driver seat of a vehicle you have no keys for, and needs a lockpick in your inventory (sold at the Hardware Store). A failed attempt breaks the lockpick and sets off the alarm, and the police may be alerted.

A vehicle spawned by another script cannot be driven

The script spawned the vehicle without giving keys. Give them after spawning, on the client with exports['qs-corevehiclekeys']:GiveKeys(plate) or from the server with TriggerClientEvent('vehiclekeys:client:SetOwner', source, plate) — QBCore scripts that already use that event or qb-vehiclekeys work as they are. As a stopgap set Config.RequireKeysToDrive = false in qs-corevehiclekeys/config.lua.

My car is not in the garage

A vehicle belongs to the garage where it was last stored and is listed only there. A vehicle whose garage is not one of the configured garages — every car bought at the dealership, or one stored in a garage you later removed from the config — appears in every garage and can be taken out from any of them; storing it assigns that garage.

"That vehicle is already out"

A vehicle with that plate exists in the world, so it cannot be taken out twice. Find it, or delete it with /dv and try again. If the car was destroyed, lost or deleted, there is nothing in the world with its plate and it can be taken out again — no impound needed.

"This is not your vehicle" when storing

Only vehicles owned by your character (in the vehicles table) can be stored. Cars from /car, the admin menu or job garages are not owned by anyone.

A car removed with /impound is gone

/impound removes the vehicle from the world. The owner takes it out again from the garage where it was last stored — or from any garage if it was never stored.

My car ran out of fuel and there are no gas stations

The bundled LegacyFuel bridge only consumes fuel; it has no pumps or jerry cans. Replace it with a fuel script that has gas stations. If that script's resource or export is not LegacyFuel / GetFuel, point the HUD at it with Config.Vehicle.fuelResource and Config.Vehicle.fuelExport in qs-corehud/config.lua.

An ESX or QBCore script errors on an item or a job ("attempt to index a nil value")

The script uses an item or job Quasar Framework does not know: xPlayer.getInventoryItem() returns nil for unknown items, and unknown jobs get generic grades. Define everything the script ships with — items in the qs-core catalogue, in es_extended/config/items.lua (BridgeItems) or qb-core/shared/items.lua; jobs in qs-core/shared/jobs.lua or qb-core/shared/jobs.lua; gangs in qb-core/shared/gangs.lua. Then restart the server.

"No such export getSharedObject in resource es_extended" (or GetCoreObject in qb-core)

The script started before the bridges. server.cfg starts [bridge] last on purpose: put every third-party script after the ensure [bridge] line, never before it.

"No such export … in resource ox_inventory" or "qb-inventory"

The script calls an inventory resource directly instead of going through the framework. Quasar Framework does not provide ox_inventory or qb-inventory exports, so those calls are not covered. Use a version of the script that uses the framework's item functions (xPlayer.addInventoryItem, Player.Functions.AddItem, QBCore.Functions.HasItem), or adapt those calls to exports['qs-core']:AddItem / RemoveItem / HasItem.

A Qbox script does not work

Scripts written only for Qbox (qbx_core, exports.qbx_core) are not supported. Scripts that support QBCore work through the QBCore bridge — pick the QBCore version of the script when there is one.

ESX menus do not open

ESX.UI.Menu needs a menu resource, exactly as on ESX. The console line [es_extended bridge] no menu resource registered for type "default" — install esx_menu_default tells you which one. Install it after [bridge].

A garage or vehicle shop script shows no vehicles

Owned vehicles live in qs-core's vehicles table. The ESX owned_vehicles table exists but stays empty and QBCore's player_vehicles does not exist, so scripts that read those tables with SQL see nothing. Use qs-garage and qs-vehicleshop, or adapt the script to exports['qs-core']:GetCitizenVehicles(citizenid) (or GetPlayerVehiclesQBShape for QBCore-shaped rows).

Money or jobs written with SQL to users are undone

The users table is a copy that qs-core keeps up to date, in one direction only. A script that edits money or jobs there with raw SQL changes nothing in game. Use the framework functions (xPlayer.addAccountMoney, xPlayer.setJob) instead.

Item labels are missing in a QBCore script's client UI

On the client, QBCore.Shared.Items contains the items listed in qb-core/shared/items.lua. If a script reads labels from it on the client, add its items to that file.

A script sees no weapons in xPlayer.getLoadout()

Weapons are inventory items in Quasar Framework, so xPlayer.getLoadout() is always empty. Check for the weapon item with xPlayer.hasItem('weapon_pistol') or xPlayer.getInventoryItem('weapon_pistol').

Common Errors

Common Errors

Installation & txAdmin#

Language & permissions#

Characters & players#

Inventory & weapons#

Vehicles#

Economy & jobs#

ESX & QBCore scripts#

Performance#