# FAQ and troubleshooting

## FAQ and troubleshooting

### Common questions

#### Which frameworks are supported?

Scripts support **QBCore** and **QBX**.

#### Which inventory systems are supported?

Most scripts support **qb-inventory**, **ox\_inventory**, and **qs-inventory**.

Check the script config for exact support.

#### Can scripts be customised?

Yes.

Most scripts include a `config.lua` file for item names, cooldowns, rewards, locations, and more.

#### Can one purchase be used on multiple servers?

No.

Each purchase is for one server unless stated otherwise.

### Startup issues

#### The script does not start

Check these first:

* The `ensure` line exists in `server.cfg`
* Dependencies start before the script
* Config values use valid item and job names
* The correct inventory type is selected

#### The script starts but features do not work

This usually points to config mismatch.

Check:

* Item names
* Target resource setup
* Inventory selection
* Required jobs or permissions

#### A required item does not work

Confirm:

* The item exists in your inventory resource
* The item name matches `config.lua`
* The item is useable if the script expects that behavior

### Purchase issues

#### My Tebex purchase is missing

Wait a few minutes first.

If it still does not appear, open a Discord ticket with proof of payment.

#### I want a refund

All payments are final.

Refunds are not available.

### Before opening a ticket

Include these details:

* Script name
* Framework version
* Inventory resource
* Console errors
* Screenshots or short clips of the issue

{% hint style="success" %}
A complete ticket usually gets a faster answer.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://shocks-development.gitbook.io/shocks-development-docs/shocks-scripts-doc/faq-and-troubleshooting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.