> 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/readme.md).

# Welcome to Daddy Studio

Documentation for every Daddy Studio script, map and clothing pack.

Setup guides, configuration and help for everything we sell. Pick a product on the left, or start below.

## Start here

| 📥 Just bought something?                                                                                                                  | 🛠️ Something not working?                                                                                                         |
| ------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------- |
| [Download it from Keymaster](/daddy-studios-docs/getting-started/cfx-keymaster-guide.md), then follow the product's **Installation** page. | Read the [FAQ & Troubleshooting](/daddy-studios-docs/getting-started/faq-and-troubleshooting.md) page or open a ticket on Discord. |

## Catalog

|                                                                                       |                                                                  |
| ------------------------------------------------------------------------------------- | ---------------------------------------------------------------- |
| 💰 [**Scripts**](/daddy-studios-docs/scripts/introduction-to-daddy-studio-scripts.md) | Admin, HUD, marketplace, GPS, loading screen and more            |
| 🎁 [**Free Scripts**](/daddy-studios-docs/free-scripts/free-scripts.md)               | Chance, Voice Volume, Intoxication, illenium-appearance redesign |
| 🗺️ [**Maps**](/daddy-studios-docs/maps/introduction-to-daddy-studio-maps.md)         | MLO interiors                                                    |
| 👕 [**Clothing**](/daddy-studios-docs/clothing/clothing.md)                           | Department uniform packs                                         |

## Latest releases

|                                                                               |                                                                  |
| ----------------------------------------------------------------------------- | ---------------------------------------------------------------- |
| ⏸️ [**Daddy Pause Menu**](/daddy-studios-docs/scripts/daddy-pausemenu.md)     | GTA's pause menu replaced, in five styles (beta)                 |
| 🎓 [**Daddy College**](/daddy-studios-docs/scripts/daddy-college.md)          | School system with lessons, exams, detention and campus security |
| 🎲 [**Daddy LS Tour**](/daddy-studios-docs/scripts/daddy-lstour.md)           | 3D multiplayer board game with AI players                        |
| 🖥️ [**Daddy Admin**](/daddy-studios-docs/scripts/daddy-admin.md)             | Tablet admin panel with a live map, tickets and an F9 quick menu |
| 🩸 [**Daddy HUD**](/daddy-studios-docs/scripts/daddy-hud.md)                  | Survival HUD with a body map, injuries and a noise indicator     |
| 🔧 [**Daddy Car Crafting**](/daddy-studios-docs/scripts/daddy-carcrafting.md) | Build vehicles part by part at a workshop bench                  |

## Links

[🛒 **Tebex Store**](https://daddy-studio.tebex.io/) | [💬 **Discord**](https://discord.gg/NFKjbN9s2q) | [📺 **YouTube**](https://www.youtube.com/@daddy.studios) | [🖥️ **Live demos**](https://lkrypton.github.io/daddy-demos/)


---

# 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/readme.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.