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

# Daddy Combat Log

Combat log detection for FiveM with a marker, a ghost ped or 3D text at the spot where the player left.

![Daddy Combat Log](https://2487709298-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqcEXX242M9YYHjASblGi%2Fuploads%2Fgit-blob-82fa3f390fd822c04dfbbfb86a8bbb75ca3b91cd%2Fdaddy-combatlog-thumbnail.jpg?alt=media)

When a player disconnects, Daddy Combat Log leaves a marker, a ghost ped or a 3D text at the exact spot, so staff can see who left, why and when.

## Features

* **3 display modes**: `marker` (world marker + floating info panel), `ped` (a ghost ped lying where the player disconnected) and `drawtext` (marker + native 3D text)
* **Ghost ped that looks like the player**: clothing, props, hair and face are copied (ped mode). It reads the ped itself, so it works with any clothing script
* **Disconnect reason detection** with readable labels (crash, timeout, F8 exit, AFK kick, quit, kick, ban) and reason-based marker colors
* **Discord webhook** with the player, reason, identifier and coordinates
* **Admin notifications** in game, plus `/combatlogs`, `/clearcombatlog` and `/testcombatlog`
* **Optional database log** through oxmysql
* **Staff-only identifiers**: the license / Discord ID is only sent to players who can use the admin commands
* Auto-detects **QBox, QBCore and ESX**, or runs standalone
* **English and Turkish** included

## Requirements

* FiveM server artifact 5104 or newer with **OneSync enabled**
* `ox_lib`
* Optional: `ox_target` or `qb-target` (ped mode), `oxmysql` (database log)

Continue with [Installation](/daddy-studios-docs/scripts/daddy-combatlog/installation.md).

***

[🛒 Escrow on Tebex](https://daddy-studio.tebex.io/package/7688381) | [🔓 Open Source on Tebex](https://daddy-studio.tebex.io/package/7688373) | [💬 Get Support](https://discord.gg/NFKjbN9s2q)


---

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