ESX Scripts

Your download link arrives by email as soon as checkout finishes. You can also log in to My Account with the email you ordered with and open Downloads. That is also where you find anything you bought before.

Sales are final once a product has been downloaded. If you picked the wrong item and haven't downloaded it yet, contact support and we will swap it for the right one at no charge.

No. Your license covers personal use with the account that made the purchase. Reselling, sharing or uploading the files to public sites ends every license on that account.

Yes. Every product comes with ongoing support and updates. Support for very old versions, or setups running outdated dependencies, can end over time.

Current ESX scripts target ESX Legacy, which loads the framework with exports['es_extended']:getSharedObject() instead of the old esx:getSharedObject event. A script written for Legacy will usually throw errors on ESX 1.1 or 1.2 servers, so update your es_extended before buying scripts built for the current release.

Most ESX scripts assume es_extended and oxmysql, and many also want ox_lib, an inventory such as ox_inventory, and a target resource such as ox_target or qtarget. Each product page lists the specific dependencies for that script.

Drop the resource folder into your resources directory, import any SQL file that came with it, and add an ensure line to server.cfg below es_extended and the script's other dependencies. Set your options in the config, restart, and check the server console for errors before opening to players.

An escrow ESX script is encrypted through FiveM Asset Escrow and tied to your Keymaster license, so you can adjust the config but not the code. Open source scripts give you every file, which matters if you plan to change framework calls or add your own features. Product pages on store-tebex.io say when a script is open source or fully unlocked.

A standalone script runs without any framework, so it works on ESX, QBCore or a vanilla server. The trade-off is that a standalone script usually has no built-in hooks for ESX jobs, money or items unless the developer added an optional bridge.