Common issues

Most common issues which can occur when using or installing FiveM Scripts

Error parsing script / Failed to load script Error parsing script @...lua in resource ...: @...lua:1: syntax error near '<\1>'

The script may be corrupt, try a clean reinstall. This may also be caused by your server artifacts being outdated. So make sure that you're using the latest recommended build or newer.

When installing a resource, make sure to not use FileZilla. As it has a high chance of corrupting an escrowed script. Instead we recommend using WinSCP

You lack the required entitlement to use

As a first step, make sure to restart your server after first installing your resource. If this error persists, it means that the script license is not on the same keymaster account as your FiveM server.

If the asset is on a different account, you may use the keymaster transfer feature to transfer the asset to the same keymaster account as your server license is using.

Failed to verify protected resource

Files were possibly corrupted during transfer. Ensure hidden files are copied; the .fxap file in a protected resource must be included. Some FTP programs may skip these files.

No such export * in resource *

This error mostly occurs when a resource is trying to call an export function of another resource. Please ensure that the script mentioned at the end of the error message is started before the script throwing the error

Attempt to index a nil value (global 'QBCore')

Make sure that qb-core is started before the script. Additionally verify that you have enabled the correct framework in the config.lua file

Attempt to call a nil value (field "AddPlayerItem")

Attempt to call a nil value (field "RemovePlayerItem")

Make sure that you've enabled the correct framework in the config.lua file

Resource * used the getSharedObject Event, this event no longer exists!

Open the config.lua file and toggle the UseNewExport option under the esx settings