> For the complete documentation index, see [llms.txt](https://docs.onelitefeather.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onelitefeather.net/antiredstoneclock-remastered/how-to-guides/produce-a-debug-log-for-a-bug-report.md).

# Produce a debug log for a bug report

Collect the detailed log a maintainer needs when the plugin does not behave as expected.

**Before you start:** none.

1. Switch debug logging on:

   ```
   /arcm feature debug
   ```

   It takes effect immediately, no restart needed.
2. Reproduce the problem.
3. Switch debug logging off again with the same command, so the file stops growing.
4. Attach `plugins/AntiRedstoneClock-Remastered/debug-logs/latest.log` to your report at <https://github.com/OneLiteFeatherNET/AntiRedstoneClock-Remastered/issues>.

## Check it worked

`latest.log` exists and contains lines mentioning the block type you were testing with. Debug messages never appear in the server log, so an empty server log means nothing here.

## If it does not work

If the server log says `This server does not run on Log4j2, debug logging is not available`, the debug file cannot be written on that server software. Attach the server log instead and say which server software you run.

See also: [Debug log files](/antiredstoneclock-remastered/reference/debug-log-files.md) for the path, rotation and retention.


---

# 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://docs.onelitefeather.net/antiredstoneclock-remastered/how-to-guides/produce-a-debug-log-for-a-bug-report.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.