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

# Troubleshooting

## The resource does not start

* `ox_lib` must be started before `daddy-combatlog`.
* Your server artifact must be 5104 or newer and OneSync must be enabled (`set onesync on` in `server.cfg`).

## `/testcombatlog` says I have no permission

Your account is not in the admin principal. Add it in `server.cfg` and restart the server:

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

If you changed `ServerConfig.AdminAce`, add your account to that group instead.

## No marker or panel appears

* Check `Config.DisplayMode` in `config.lua`. The panel only exists in `marker` mode.
* Walk to the spot. The marker is visible within `Config.RenderDistance` and the panel within `Config.NuiRenderDistance`.
* Set `Config.Debug = true` and read the F8 console for `Added combat log` lines.

## Logs show at the wrong place, or none are created

OneSync is required. Without it the server cannot read the player's position. A log is skipped when the server has no valid position for the player.

## The ghost ped wears default clothes

* `Config.DisplayMode` must be `'ped'` and `Config.AppearanceSync` `true`.
* The look is reported at most every `Config.SyncInterval` seconds, so a change made just before disconnecting may be missing. Lower the interval to reduce that.

## I do not see the identifier

By default only players with the admin permission see it (`ServerConfig.IdentifierAdminsOnly`).

## Nothing arrives on Discord

* Check `ServerConfig.DiscordWebhook` in `server/config.lua` (not in `config.lua`).
* Turn on `Config.Debug`. The server console prints the status code Discord answered with.

## The database table is not created

Set `ServerConfig.UseDatabase = true` and start `oxmysql` before `daddy-combatlog`.


---

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