> 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/scripts/daddy-combatlog/configuration/ped-appearance.md).

# Ghost Ped Appearance

Only used in ped mode (`Config.DisplayMode = 'ped'`).

## What is copied

* the ped model (read by the server, not sent by the player)
* clothing components, textures and palettes
* props (hats, glasses, watches, ...)
* for freemode peds: head blend (parents and mix), hair color, eye color, face features and face overlays (beard, eyebrows, makeup, ...)

Tattoos and other decals are not copied.

## How it works

The client reads its own ped with game natives, so it works with any clothing script (illenium-appearance, fivem-appearance, qb-clothing, and so on). The look is reported once after the player loads and then again whenever it changed, at most every `Config.SyncInterval` seconds. The server checks every value before it stores it and drops a report that is malformed, oversized or sent too often.

## Settings

| Setting                 | Default | Description                             |
| ----------------------- | ------- | --------------------------------------- |
| `Config.AppearanceSync` | `true`  | Turn the look copy on or off            |
| `Config.SyncInterval`   | `30`    | Seconds between look checks (minimum 5) |

{% hint style="info" %}
A change of clothes made in the last `SyncInterval` seconds before the player disconnects may not be on the ghost ped yet. Lower the interval if this matters to you; the cost is a few native calls per player at each check.
{% endhint %}


---

# 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/scripts/daddy-combatlog/configuration/ped-appearance.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.