Common Errors
Fixes for the most common problems when installing STG Scripts resources, from entitlement and syntax errors to corrupted downloads, start order and duplicate installs.
Most install problems come down to one of the issues below. Work through the one that matches your console error before opening a ticket.
- Lacking entitlement: the console says you lack the required entitlement
- Syntax error near
<\1>: the console showsError loading bufferwhen the resource starts - Found a different bug?: what to send us in a ticket
"Download corrupted" or the resource will not start after an update
FiveM can keep a stale copy of an escrowed resource in its cache. Clear it and start the resource again:
Stop the resource with stop <resource>.
Delete the server cache folder.
Run refresh so the server reads the resource again.
Start it with ensure <resource>.
If the error stays, download the latest version again from the Cfx.re portal and replace the whole folder.
Config changes do not apply
This almost always means the resource is installed twice, for example an old copy left in another folder or renamed with a suffix. The server loads one copy while you edit the other.
Search your resources folder for the resource name and keep a single copy.
Framework or player data not detected
STG scripts read your framework through stg_lib, so it has to start after your framework and dependencies. Use this order in server.cfg:
ensure oxmysql
ensure ox_lib
# your framework: es_extended, qb-core or qbx_core
# your inventory
ensure stg_lib
ensure [STG]Item images are missing
Each script ships its item images in the [SETUP] folder. Copy them into your inventory's image folder, for example ox_inventory/web/images or qb-inventory/html/images.
Database errors on start
Import the .sql file from the script's [SETUP] folder into your database before the first start, and make sure oxmysql is running.
Still having trouble?
Open a ticket on our Discord. Our team answers around 15 hours a day.