F5 StudioF5 Studio
Skip to main content

Frequently Asked Questions

General​

What frameworks are supported?​

All F5 Studio scripts support ESX, QBCore, and QBox Core. Scripts with bridge support detect your framework automatically at startup — no manual configuration needed. The detection priority is: QBox → QBCore → ESX.

Where do I download my purchased scripts?​

After purchase, download your scripts from your Tebex account. You'll receive a keymaster asset grant — claim it at Cfx.re Keymaster.

How do I activate my license?​

  1. Go to Cfx.re Keymaster
  2. Log in with your Cfx.re account
  3. Go to Granted Assets and find the F5 script
  4. Generate a license key for your server's IP address
  5. The script will auto-validate on startup

Can I use F5 scripts on multiple servers?​

Each purchase grants a license for one server. If you need to run the script on multiple servers, you'll need additional licenses. Contact us on Discord for bulk pricing.

Do you offer refunds?​

Due to the digital nature of our products, we generally do not offer refunds. If you experience a technical issue we cannot resolve, please open a ticket on Discord.

Technical​

What database is required?​

Scripts that use a database require MySQL via oxmysql (recommended) or mysql-async. We recommend MariaDB 10.6+ or MySQL 8.0+. Some scripts (like F5 Safezones) store data in local files and don't need a database at all.

Which artifacts version do I need?​

We recommend using the latest recommended FiveM server artifacts. Minimum supported version is 6116+.

Do F5 scripts work with OneSync?​

Yes. All scripts are fully compatible with OneSync and OneSync Infinity.

Can I modify the scripts?​

Our scripts are escrow-protected via Cfx.re Tebex. You can modify any non-escrowed files (config files, shared files, etc.). Core logic files are encrypted and cannot be modified.

How do I update a script?​

  1. Download the latest version from Keymaster (paid) or GitHub (free)
  2. Back up your current config.lua
  3. Replace the resource folder with the new version
  4. Merge your config changes back in
  5. Restart the resource

Database migrations (if any) are applied automatically on startup — no manual SQL import needed.

tip

Always back up your config.lua before updating. New versions may add config options, but your existing values should carry over.

Compatibility​

Will F5 scripts conflict with each other?​

No. All F5 Studio scripts are designed to work together without conflicts. They share no overlapping events or database tables.

Do your scripts work with ox_lib?​

Yes. Our scripts are compatible with ox_lib and will use it automatically if detected. QBox Core servers typically already have ox_lib installed.

Are your scripts compatible with custom frameworks?​

Our scripts officially support ESX, QBCore, and QBox Core. Custom frameworks may work if they follow the same event and export structure, but we cannot guarantee compatibility or provide support for them.

What's the difference between QBCore and QBox Core support?​

QBox Core (qbx_core) is a maintained fork of QBCore with improved performance and ox_lib integration. The bridge detects QBox automatically — just ensure qbx_core instead of qb-core in your server.cfg. The API and events remain compatible.

Still have questions?​