Support

Licensing

Every NX Creative script is sold through Tebex and bound to your FiveM server key through Tebex Keymaster. There is no separate activation step, the binding happens as soon as the resource starts.

If a script fails to validate at boot, the common causes are:

1. Buyer mismatch. The Tebex account running the server does not own this license. Use the account that purchased the script.
2. Key mismatch. The license is bound to a different server key. Rebind through your Keymaster dashboard.
3. Refund or chargeback. Refunded purchases have their licenses revoked. Repurchase, or open a ticket if you believe the revocation is a mistake.

Where to ask for help

Before you open a ticket

Include these six details and you will roughly halve the turnaround:

1. Script name and version.
2. Framework (ESX, QBCore, or QBox) and version.
3. ox_lib, ox_target, and ox_inventory versions.
4. Full client and server console output around the error.
5. Your FiveM artifact number.
6. Exact reproduction steps.

What we support

• Install and configuration issues.
• Bugs in the script itself.
• Compatibility with the supported frameworks and the ox resources listed under Dependencies.

What we do not support

• Modifications to the script source.
• Compatibility with unsupported frameworks or forks of dependencies.
• General server-building help, such as server.cfg debugging, artifact selection, or hosting. The wider FiveM community has better resources for that.