Documentation

Quick Fixes & Common Issues

Fix the most common FiveM script problems: missing dependencies, framework settings, database tables, r_store credits and players stuck in r_ffa.

Common Installation Issues

Most problems come from a missing dependency or a wrong config value. Go through these steps first.

Check Dependencies

Make sure every dependency is installed and started before the R-Scripts resource.

Required by most scripts

  • ox_lib: UI and utilities
  • oxmysql: database

Frameworks

  • es_extended (ESX)
  • qb-core (QBCore)
  • qbx_core (QBX)

Configure Your Framework

Open config.lua in each script and set R.Framework. The accepted values differ per script:

ScriptValuesDefault
r_store, r_casino"ESX", "qbcore", "qbx""qbx"
r_tophud"ESX", "QBCore", "QBX""QBX"
r_billing, r_ffa, r_vehicleshop'auto', 'esx', 'qb', 'qbox''auto' (detects the framework)
r_loadingno framework needed

On ESX also check R.CoreName if you renamed es_extended, and set R.newESX = false in r_store, r_casino and r_tophud if you run ESX 1.1.

Database tables

The scripts that use a database create their tables on first start when the auto-insert option is on (it is on by default). The SQL files are included if you prefer to import them yourself:

ScriptTablesFileAuto-insert option
r_storer_store_players, r_store_purchasessql.sqlR.EnableAutoinsert
r_casinor_casino_players, r_casino_case_cooldownssql.sqlR.EnableAutoinsert
r_ffar_ffasql/r_ffa.sqlR.EnableAutoinsert
r_billingr_billing, r_billing_bills, r_billing_logsql.sqlR.AutoInsertSQL
r_vehicleshopowned_vehicles (ESX) or player_vehicles (QB)sql/esx.sql, sql/qb.sqlR.EnableAutoinsert
r_tophud, r_loadingno database

If you see "table doesn't exist" errors, import the file or start the resource once with the auto-insert option set to true.

Script-Specific Issues

Still stuck?

Ask on Discord

We usually reply within 2 hours.

Include these in your message:

  • Your framework (ESX/QBCore/QBX)
  • Your inventory system
  • Server console errors
  • What you have already tried