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

# Sheriff Uniforms

Three sheriff departments in one pack for FiveM, LSCSO, LSSD and PBSD uniforms.

![Sheriff Uniforms](https://2487709298-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqcEXX242M9YYHjASblGi%2Fuploads%2Fgit-blob-7ec175024d0589198998e64b78c5bab135bc53f8%2Fdaddy-clothing-sheriff-thumbnail.jpg?alt=media)

Three sheriff departments in one pack: Los Santos County Sheriff (LSCSO), Los Santos Sheriff (LSSD) and Paleto Bay Sheriff (PBSD). Streamed clothing for the freemode peds, works with any appearance menu.

[🛒 **Buy on Tebex**](https://daddy-studio.tebex.io/package/7706319) | [👀 **Browse every piece in 360°**](https://lkrypton.github.io/daddy-demos/clothing/?pack=sheriff)

## What's inside

251 items with 723 texture variations.

| Ped        | Items | Pieces                                                                                                                                                       |
| ---------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Male**   | 204   | 75 tops, 15 trousers, 11 undershirts, 22 armor / vests, 14 gear pieces, 13 patches and badges, 8 bags and belts, 2 shoes, 10 extras, 10 hair pieces, 24 hats |
| **Female** | 47    | 3 tops, 2 trousers, 2 gear pieces, 3 shoes, 10 hair pieces, 22 hats, 5 arms                                                                                  |

## Departments

| Department                                                                                               | Male | Female |
| -------------------------------------------------------------------------------------------------------- | ---- | ------ |
| [**LSCSO**](/daddy-studios-docs/clothing/sheriff-uniforms/lscso-uniforms.md) · Los Santos County Sheriff | 127  | 44     |
| [**LSSD**](/daddy-studios-docs/clothing/sheriff-uniforms/lssd-uniforms.md) · Los Santos Sheriff          | 43   | -      |
| [**PBSD**](/daddy-studios-docs/clothing/sheriff-uniforms/pbsd-uniforms.md) · Paleto Bay Sheriff          | 34   | 3      |

The pack comes as three clothing resources, one per department: `DaddyXLarestia_Lscso`, `DaddyXLarestia_Lssd` and `DaddyXLarestia_Pbsd`. Start all three.

{% hint style="info" %}
LSSD and PBSD were sold as separate packs before 11 October 2026. They are now part of this pack.
{% endhint %}

## Requirements

* Nothing, no framework or Lua
* An appearance or clothing menu, for example illenium-appearance

Setup: [Installation](/daddy-studios-docs/clothing/installation.md).


---

# 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/sheriff-uniforms.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.
