Frequently asked questions

Each purchase is tied to the FiveM server key you check out with, the same way Tebex handles any other store purchase. Running the script on a different server means re-linking it there — see the Entitlement Error guide in the docs if a transfer doesn't go smoothly.

QBCore, ESX, Qbox, ND_Core, ox_core, and standalone are supported where it makes sense for the script — check each resource's own configuration docs for the exact framework bridge options.

Digital goods delivered through Tebex are generally final once the escrowed files are issued — reach out on Discord before purchasing if you're not sure a script fits your server, and we'll help you check compatibility first.

It depends on the script — check the individual product's docs for specifics. Tommy's Radio, for example, natively supports running across multiple servers in a network.

Join the Discord with the script name, your server's artifacts version, and the full error text from the txAdmin console. The docs FAQ also covers the escrow errors that show up most often (syntax errors, entitlement errors, ACE permission issues).

Scripts ship escrow-protected (standard for the FiveM marketplace) — config files and most client-facing settings are open, but core logic is protected the same way Cfx.re requires for any escrowed resource.

Tommy's Radio has a public demo server — see the docs for connection details. Other scripts are covered by their own docs pages with screenshots and short overview videos where available.

Updates ship as needed for FiveM/framework compatibility and new features. Release notes call out any config changes you need to make — check them before updating a live server.