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

# Installation

How to install a Daddy Studio clothing pack.

1. Download the pack from [Cfx Keymaster](/daddy-studios-docs/getting-started/cfx-keymaster-guide.md).
2. Put the folder into your server's `resources`, for example `resources/[clothing]/`. Some packs have more than one folder (the Sheriff pack has three): put all of them there. Some packs have more than one folder (the Sheriff pack has three): put all of them there.
3. Add it to `server.cfg` **before** your appearance script:

   ```
   ensure [clothing]
   ensure illenium-appearance
   ```
4. Restart the server. The new pieces show up in your clothing or appearance menu.

{% hint style="info" %}
Packs are large. Every player downloads the files once when they join, after that they load from the game cache.
{% endhint %}

## Notes

* Do not rename the folder or the files inside, the clothing collection names depend on them.
* The packs add a new collection, they do not replace base game clothing, so they work next to other clothing packs.
* Works with illenium-appearance, fivem-appearance and any menu that reads streamed collections.


---

# 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/clothing/installation.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.