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

# Changelog

## 1.0.0 — first public release

* Combat log detection for every disconnect, with readable reason labels
* Three display modes: marker with floating info panel, ghost ped, 3D text
* Ghost ped copies the player's clothing, props, hair and face (ped mode)
* Server-side positions and ped model: nothing about the log is taken from the client
* Discord webhook with the player, reason, identifier and coordinates
* Admin notifications, `/combatlogs`, `/clearcombatlog`, `/testcombatlog`
* Optional database log (oxmysql)
* Identifiers are sent only to players with the admin permission
* Logs are sent to players near the spot and to all admins (`ServerConfig.BroadcastRadius`)
* Server exports `getActiveLogs` and `getRecentLogs`
* Auto-detection of QBox, QBCore and ESX, standalone mode
* English and Turkish


---

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