Support
Talk to the people who wrote the code
No ticket bots, no outsourced first line. The developer who wrote the script reads your message, and can point you at the exact config line or, on an open-source edition, the exact line of code.
- Reply timeUsually within a few hours on weekdays, a day at most
Pick a lane
Three ways in, one team behind all of them
Fastest
Discord ticket
Open a ticket in the support channel or just ask in public. Paste the report below and the answer usually comes back in one round.
Private
For invoices, privacy requests, security reports and anything you would rather not post in a public channel.
Self-serve
Docs and changelog
2 scripts are documented section by section, and every release is listed. Half of all tickets are answered there already.
Before you write
Send this, not "it does not work"
- Script and version - the version is on the product page and in the changelog.
- Framework and its version - QBCore, QBox, ESX legacy or standalone.
- The exact console error - server and client, the first red line matters most.
- What changed - an update, a new resource, a config edit right before it broke.
- Resources touching the same thing - target, inventory, notification, dispatch.
Script + version: <name> v<version> (see the changelog) Framework: QBCore / QBox / ESX legacy / standalone + version Server artifact: What I did: What I expected: What happened instead: Console error (exact lines, server and client): Other resources touching the same thing (target, inventory, notify): Changed recently (update, new resource, config edit):
We point you at the config, locale or bridge line, and if the fix is in the escrowed core we ship it in the next release.
Common fixes
Check these first
The resource starts but nothing happens in game
Nine times out of ten a dependency is missing or starts after the script. Check the Requires line under "At a glance" on the product page, make sure every required resource is in your server.cfg above ours, and look at the first red line in the server console - it names the missing piece.
It worked, I updated, now it does not
Read the changelog entry for the version you installed: breaking changes are listed first. Compare your edited config with the new default one - a renamed key is the usual culprit. If you edited the open files - or the code of an open-source edition - diff your copy against the fresh download before asking.
Where do I enter the licence key?
Nowhere - we issue no keys and nothing calls home to us. Escrowed scripts use your normal sv_licenseKey, which must belong to the Cfx account that bought them, or the console says "You lack the required entitlement". Open-source editions need nothing at all.
My membership ended. Does the script stop?
Yes, once the paid period is over: Cfx removes the grant and the escrowed membership scripts stop starting. Resubscribe, or buy a script outright to keep it for good.
Payment, invoice or refund questions
Tebex is the merchant of record, so invoices and refunds go through them: the link is in your receipt email. Our refund terms are on the Refunds page, and we can nudge Tebex on your behalf if a case is stuck.
It conflicts with another resource
Tell us which one and what you see. Conflicts with the common targeting, inventory and notification resources are usually a config switch on our side; conflicts with a heavily customised framework may need you to send a snippet.
What support covers
Honest scope, so nobody waits for an answer that is not coming
Covered, as long as the script is ours
- Installation and configuration on the frameworks listed on the product page
- Bugs you can reproduce on a fresh copy of the current version
- Migration notes when an update changes a config key or an export
- Questions about exports, events and how to hook your own code in
- A pointer to the exact config line - or code line on an open-source edition
Best effort only
- Copies you have modified heavily - send a diff and we will look, but not debug your fork line by line
- Bugs inside third-party resources, even when ours triggers them
- Custom features - ask, it may land in a release, but it is not a support ticket
- Frameworks marked planned or not supported in the compatibility matrix
- Payment disputes - those go through Tebex, we can only nudge
Want to see how we answer before you buy? Grab a free script, break it, and open a ticket. Same queue, same people.
The paperwork
What the licence lets you do with the code, what we hold about you, and when a purchase can be refunded - on this site, in plain words.
Still stuck?
Bring the console, we bring the fix
Open a ticket with the template above and the first reply will be a real answer, not a form.
