> 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/commands-and-permissions.md).

# Commands & Permissions

| Command                | Description                                                         |
| ---------------------- | ------------------------------------------------------------------- |
| `/combatlogs`          | List active combat logs with their ID, player, reason and time left |
| `/clearcombatlog <id>` | Remove one combat log                                               |
| `/testcombatlog`       | Create a test combat log at your position (in-game only)            |

All commands are restricted to the principal in `ServerConfig.AdminAce` (default `group.admin`). The script registers `command.combatlogs`, `command.clearcombatlog` and `command.testcombatlog` for it automatically.

## What admins get

Players who can use the commands also:

* receive an in-game notification when someone combat logs (`ServerConfig.AdminNotify`)
* see the player's identifier on the panel, the ped menu and the 3D text (`ServerConfig.IdentifierAdminsOnly`)

Everyone else sees the name, reason and time, but no identifier.

## Giving admin access

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

Use another group by changing `ServerConfig.AdminAce`, for example `group.moderator`, and add your moderators to that group instead.


---

# 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/commands-and-permissions.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.