> 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/about-daddy-studio.md).

# About Daddy Studio

Who we are and how we build our FiveM scripts, maps and clothing.

Daddy Studio makes FiveM resources for roleplay servers: **scripts**, **MLO maps** and **clothing packs**. Everything is sold on our [Tebex store](https://daddy-studio.tebex.io/) and delivered to your Cfx Keymaster account.

## What we make

|                     |                                                                        |
| ------------------- | ---------------------------------------------------------------------- |
| 💰 **Scripts**      | Admin panel, HUD, marketplace, GPS, loading screen, EMS tools and more |
| 🎁 **Free scripts** | Small tools we give away, fully open                                   |
| 🗺️ **Maps**        | MLO interiors with tuned occlusion and LODs                            |
| 👕 **Clothing**     | Uniform packs for police, sheriff and park ranger departments          |

## How we build scripts

* **Two editions:** every paid script comes as **Escrow** (config, languages and framework bridges open) or **Open Source** (full code, including the UI source).
* **Your framework:** most scripts work on **Qbox, QBCore and ESX** and detect them automatically.
* **Checked on the server:** actions that touch money, items or permissions are validated server side.
* **Readable config:** every setting has a short note next to it, languages live in their own files.
* **Try before you buy:** many scripts have a [live demo](https://lkrypton.github.io/daddy-demos/) and a video on our product pages.

## Support

Questions before or after a purchase? Open a ticket on our [Discord](https://discord.gg/NFKjbN9s2q). Each product also has its own installation and troubleshooting pages 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/about-daddy-studio.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.