Support
Most trouble with an escrowed script comes down to something small in the install. Run the three checks below first. If the problem survives them, send the details in the list further down, so the first reply can be an answer rather than a question.
Before you open a ticket.
These three account for most reports that turn out not to be faults in the script. Each takes a minute to rule out, and ruling one out is useful information either way.
The script never started
Confirm server.cfg actually contains an ensure line for the resource, and that the folder name in /resources matches it exactly, case included. A folder sitting there without an ensure line loads nothing and reports nothing.
A dependency is missing
Check the fxmanifest and the included readme for resources this one depends on, then make sure every one of them starts before it. Missing dependencies usually surface as a nil value error rather than a message naming the thing that is absent.
The SQL was never imported
If the download ships a .sql file, import it into your database before the first start. Missing tables tend to show up on the first player interaction rather than at boot, which makes them look like a bug in the script.
What to put in the message.
A ticket carrying all of this can usually be handled in one pass. A ticket carrying none of it becomes a conversation about what your server is running.
- Tebex order reference
- The reference printed on your order confirmation email. It ties a payment to a grant on a specific Cfx.re account, so it is the fastest way to check whether delivery actually happened.
- Script name
- Which Redox script this is about, and the build you downloaded. If you have re-downloaded since the purchase, say so, because the current build may not be the one running on your server.
- Framework and version
- ESX Legacy, QBCore, Qbox or standalone, plus the release your server runs. Framework behaviour changes between releases, and a report without this usually ends in a guess.
- Server artifact version
- The FXServer artifact your server is built on. Plenty of reports trace back to an artifact that is far behind or far ahead of everything else in the stack.
- The exact console error
- Copy the block from the server console, or from the F8 client console for a client-side fault, as text rather than a screenshot. Include the few lines before the error as well; they often name the resource that really failed.
- What you already tried
- Anything you changed, restarted, reinstalled or ruled out, including edits to the open config and locale files. It keeps the reply from being a list of things you finished doing an hour ago.
Where to reach us.
The support channels are still being set up.
There is no Discord server or support inbox to publish yet, and a dead link here would only waste your time. Both get listed on this page the moment either one exists.
Until then, the working route is the Tebex order confirmation email that arrived with your purchase. Reply to it and keep the order reference in the message, because that reference is what lets a purchase, a grant and a Cfx.re account be matched up. If you have not bought anything yet, hold your question until you have that email in hand.
If the script simply has not appeared, check Granted Assets on the Cfx.re account you were logged into at checkout before writing in. Escrow grants land on that account and no other.