STG ScriptsDocumentation

Common Errors

Fixes for the most common problems when installing STG Scripts resources, from entitlement errors and corrupted downloads to 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.

"You lack the required entitlement"

Escrow protected scripts are tied to the Cfx.re account that bought them. The server license key in your server.cfg must be created on that same account.

  1. Sign in to the Cfx.re portal and check that the script is listed under Granted Assets.
  2. Check that your sv_licenseKey was generated on that same account.
  3. Restart the whole server, not only the resource, so the new entitlement is picked up.

If the script was bought on a different account, open a ticket on Discord.

"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 stuck?

Open a ticket on Discord and include:

  • the exact console error
  • your framework and inventory
  • your server artifact version
  • your Tebex transaction ID (tbx-...)

Still having trouble?

Open a ticket on our Discord. Our team answers around 15 hours a day.

Get help on Discord

On this page