> 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/stop-warning-signs-from-being-placed.md).

# Stop warning signs from being placed

Out of the box the plugin replaces the block of a detected clock with a sign carrying a warning text. Turn that off and leave the world untouched.

**Before you start:** none.

1. Open `plugins/AntiRedstoneClock-Remastered/config.yml`.
2. Remove the line `- sign` from the `notification.enabled` list.
3. Apply the change:

   ```
   /arcm reload
   ```

## Check it worked

Build a redstone clock in a watched world. The notification arrives and no sign is left behind.

## If it does not work

There is no command for this target — it is only configurable in the file. If signs still appear, the file was not saved before `/arcm reload` ran, or a second copy of the plugin is installed.

See also: [Configuration reference](/antiredstoneclock-remastered/reference/configuration.md) for `notification.sign.*` · [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/stop-warning-signs-from-being-placed.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.