> 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/allow-redstone-clocks-in-a-region.md).

# Allow redstone clocks in a region

Carve out a single area — a farm, a shop district, one plot — where clocks are permitted while the rest of the world stays protected.

**Before you start:** WorldGuard or PlotSquared has to be installed. The plugin picks up either one automatically when it is present.

## With WorldGuard

1. Set the region flag:

   ```
   /rg flag <region> redstone-clock allow
   ```

The flag is registered by the plugin at startup and defaults to *deny*.

## With PlotSquared

1. On the plot, set the flag:

   ```
   /plot flag set redstone-clock true
   ```

## Without either plugin

1. Add the region name to `check.ignoredRegions` in `config.yml`, or run:

   ```
   /arcm feature check ignored_regions add <region>
   ```

   This list is only evaluated when WorldGuard is installed — it matches region names, and without WorldGuard there are no regions to match.

## Check it worked

Build a clock inside the region and let it run. Nothing is broken and no notification arrives. Build the same clock just outside the region: it is detected.

## If it does not work

Region membership is checked at the exact block of the triggering component. A clock that straddles the region border is detected as soon as the triggering block sits outside it.

See also: [How detection works](/antiredstoneclock-remastered/background/how-detection-works.md) for the order in which worlds, regions and plots are consulted.


---

# 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/allow-redstone-clocks-in-a-region.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.