> For the complete documentation index, see [llms.txt](https://daddy-studios.gitbook.io/daddy-studios-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daddy-studios.gitbook.io/daddy-studios-docs/getting-started/faq-and-troubleshooting.md).

# FAQ & Troubleshooting

Answers to the most common questions about buying, installing and getting support.

## Buying

**Where do I buy?** Only on our [Tebex store](https://daddy-studio.tebex.io/).

**Escrow or Open Source, which one do I need?** Both have the same features. **Escrow** keeps the config, languages and framework bridges open and protects the rest. **Open Source** gives you the full code, including the UI source, if you want to change how the script works.

**Can I try a script first?** Many scripts have a [live demo](https://lkrypton.github.io/daddy-demos/) and a video on their product page.

**Do you give refunds?** Sales are final. If a product does not work and we cannot fix it, we may offer an exchange. See the [Terms of Service](/daddy-studios-docs/terms-of-service-tos.md).

## Delivery & Installation

**Where is my product?** In [Cfx Keymaster](https://keymaster.fivem.net/) under **Granted Assets**. See the [Keymaster Guide](/daddy-studios-docs/getting-started/cfx-keymaster-guide.md).

**How do I install it?** Follow the **Installation** page of the product in this documentation. Each product also has a `README` file inside its folder.

**The script does not start**

* Check the server console for the first red error, it usually names the missing piece.
* Make sure the requirements are started **before** the script (for example `ox_lib` and `oxmysql`).
* Escrow scripts need a server key from the account that bought them.
* Do not rename the resource folder unless the product page says you can.

**My framework is not detected** Start your framework before our script, and check the product's configuration page for a framework setting.

## Support

**How do I get help?** Open a ticket on our [Discord](https://discord.gg/NFKjbN9s2q). Link your Discord at checkout to get the **Customer** role, tickets need it.

**What should I send in a ticket?** The product name, your framework, the error from the server or F8 console and what you did before it happened.

**Do you take custom orders?** Yes, open a ticket on Discord and tell us what you need.

**Where do I see updates?** Product updates are announced on our Discord, and each product has a **Changelog** page here.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://daddy-studios.gitbook.io/daddy-studios-docs/getting-started/faq-and-troubleshooting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.