> For the complete documentation index, see [llms.txt](https://opuszek.gitbook.io/itemblocker/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://opuszek.gitbook.io/itemblocker/features/logs.md).

# Logs and Discord alerts

## Log files

Every blocked action is written to `plugins/ItemBlocker/logs/<date>.log`, one line each:

```
2026-11-02 17:40:01 | Steve | place | TNT | world | default
```

The columns are time, player, action, item, world and preset. Enchantments and effects are written with their level, such as `Sharpness 5`, and fixed enchantments as `enchantment-downgraded` and similar.

Holding a blocked item and clicking again within a second is only logged once. Files are written in the background, so a slow disk never holds up the server.

## /ib log

```
/ib log            # the last ten blocked actions
/ib log <player>   # the last ten of one player
```

It needs `itemblocker.log` and shows the most recent of the last 500 actions since the server started.

## Discord alerts

1. In Discord, open the channel settings, then **Integrations**, **Webhooks**, and create a webhook. Copy its URL.
2. Put it in `config.yml`:

```yaml
log:
  enabled: true
  discord:
    webhook: "https://discord.com/api/webhooks/..."
    cooldown-seconds: 60
```

3. Run `/ib reload`.

Each blocked action is posted to the channel, at most once per `cooldown-seconds` for the same player, action and item. Alerts never ping anyone, even if an item is named `@everyone`. If Discord cannot be reached, a warning is logged at most once a minute.

## Turning logging off

Set `log.enabled: false`. Discord alerts still work when a webhook is set.


---

# 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://opuszek.gitbook.io/itemblocker/features/logs.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.