> 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/report-clocks-without-breaking-them.md).

# Report clocks without breaking them

Let the plugin tell you about clocks and leave the blocks alone — the usual choice on a survival server where breaking player builds causes more trouble than the clock does.

**Before you start:** none.

1. Run:

   ```
   /arcm feature clock autoBreak
   ```

   The command toggles `clock.autoBreak`, saves the configuration and reloads it.
2. Read the reply: it confirms whether the feature is now enabled or disabled. You want **disabled**.

## Check it worked

Build a redstone clock in a watched world. The notification arrives, and the blocks keep running.

## If it does not work

If the clock is broken anyway, the toggle went the wrong way — the command flips the value rather than setting it. Run it once more and read the reply.

See also: [Configuration reference](/antiredstoneclock-remastered/reference/configuration.md) for `clock.autoBreak` and `clock.drop` · [What happens to a detected clock](/antiredstoneclock-remastered/background/what-happens-to-a-detected-clock.md)


---

# 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/report-clocks-without-breaking-them.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.