Common troubleshooting

The most frequent installation errors, valid for every TC script.

#The script does not start

#“Could not find dependency …”

A resource listed as a dependency is not started. Check in server.cfg that oxmysql, ox_lib and tc-ui are ensured before the script (see the start-up order).

#The console mentions license, escrow or asset

FiveM escrow refuses to load the resource.

Check that your sv_licenseKey was created with the Cfx.re account that owns the script.
If you just added the script to your account, restart the whole server.
Make sure you did not edit an encrypted file (client/, server/, shared/). Only config.lua, bridge/, web/, sql/ and install/ are editable.

#Error mentioning `tc` (nil value)

The tc global comes from tc-ui. Usual cause: tc-ui is not started, starts after the script, or its folder was renamed. It must be named exactly tc-ui.

#The framework is not detected

The framework must start before the script (detection happens at load time).
Set Config.Bridge.Debug = true and read the console at start-up.
If detection is wrong, force it: Config.Bridge.Framework = 'esx' (or 'qbcore', 'qbox', 'vision').

#Staff commands answer “access denied”

Outside Vision: add add_ace group.admin command allow and put your identifier in a group (see General installation), or add your identifier to Config.Bridge.Admins.
Vision: you need one of the permissions listed on the script's Commands page.
After editing server.cfg or config.lua, restart the resource (restart tc-xxx).

#Database

Symptom	Likely cause	Fix
`oxmysql` error at start	Wrong connection string	Check `mysql_connection_string` in `server.cfg`
“Table … doesn't exist”	Automatic creation impossible (SQL rights)	Import the script's `install.sql` (Database page)
Broken accents	Wrong character set	Use `utf8mb4` for the database and the connection

The SQL account needs the CREATE right for tables to be created automatically.

#The interface (NUI) is blank or does not open

Check that tc-ui is started (ensure tc-ui) and error-free.
Open the in-game F8 console: a red error tells you which resource is at fault.
A script that holds mouse focus permanently can interfere: test by stopping it temporarily.

#After an update

Replace the script folder and the tc-ui folder.
Keep your config.lua (compare it with the new one to pick up added options).
Restart the resources, or the server if you also changed license.

#I cannot find my error

Go back to the Troubleshooting page of the script concerned, which lists cases specific to each feature. If the error persists, get in touch with: the script name and version, your framework and inventory, and the exact error text from the console.