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

# Installation

## Requirements

| Resource                  | Required | Notes                                                                                            |
| ------------------------- | -------- | ------------------------------------------------------------------------------------------------ |
| `ox_lib`                  | Yes      | Commands and notifications                                                                       |
| OneSync                   | Yes      | The server reads player positions with server-side natives                                       |
| Framework                 | No       | `qbx_core`, `qb-core` or `es_extended` are auto-detected. Without one the script runs standalone |
| `ox_target` / `qb-target` | No       | Ped mode interaction. Without one, **E** is used                                                 |
| `oxmysql`                 | No       | Only for the optional database log                                                               |

## Steps

### 1. Download and extract

Download the resource from your [Cfx Portal](https://portal.cfx.re/assets/granted-assets) (escrow edition) or from the store (open-source edition) and extract the archive.

### 2. Add the folder

Place the `daddy-combatlog` folder in your server's `resources` directory.

### 3. Start order

Start it after `ox_lib` and your framework:

```cfg
ensure ox_lib
ensure qbx_core        # or qb-core / es_extended
ensure daddy-combatlog
```

### 4. Give your admins access

The script grants the admin commands to the principal set in `server/config.lua` (`ServerConfig.AdminAce`, default `group.admin`). Add your admins to it in `server.cfg`:

```cfg
add_principal identifier.license:xxxxxxxxxxxxxxxxxxxxxxxx group.admin
```

### 5. Check it works

Join the server and type `/testcombatlog`. A combat log appears at your position. Use `/clearcombatlog <id>` to remove it.


---

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