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

# Display Modes

Set `Config.DisplayMode` in `config.lua`.

## marker

A world marker. When you stand next to it (`Config.NuiRenderDistance`) a floating panel shows the name, reason, time and identifier. Press **E** to copy the info to your clipboard.

The marker color follows the disconnect reason (`Config.ReasonColors`).

## ped

A ghost ped lies where the player disconnected, semi-transparent and without collision. Interact with it through `ox_target` or `qb-target` (**View Information**). If neither is running, or `Config.UseTarget = false`, stand next to it and press **E**.

With `Config.AppearanceSync` the ghost ped copies the player's look, see [Ghost Ped Appearance](/daddy-studios-docs/scripts/daddy-combatlog/configuration/ped-appearance.md).

## drawtext

The same marker, with a line of native 3D text instead of the panel when you are close: name, reason, time and identifier separated by `|`. Press **E** to copy the info. No UI is used, which makes this the lightest mode.

## Which one to pick

|                       | marker | ped      | drawtext |
| --------------------- | ------ | -------- | -------- |
| Looks like the player | no     | yes      | no       |
| Needs the UI          | yes    | no       | no       |
| Target resource       | no     | optional | no       |


---

# 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/display-modes.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.