> 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/exclude-a-world-from-detection.md).

# Exclude a world from detection

Stop the plugin from touching redstone in a world — a creative world, a build server, a technical playground.

**Before you start:** none.

1. Run, with the name of the world:

   ```
   /arcm feature check ignored_worlds add creative
   ```

The command writes the world into `check.ignoredWorlds` and reloads the configuration itself.

To put a world back under observation, use `remove` instead of `add`:

```
/arcm feature check ignored_worlds remove creative
```

## Check it worked

Build a redstone clock in that world and let it run. Nothing is broken and no notification arrives.

## If it does not work

The world name must be the one the server uses, not the display name in a world-management plugin. `/arcm feature check ignored_worlds add <world>` only accepts worlds the server has loaded, so a typo is rejected instead of silently written to the file.

See also: [Configuration reference](/antiredstoneclock-remastered/reference/configuration.md) for `check.ignoredWorlds` · [How detection works](/antiredstoneclock-remastered/background/how-detection-works.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/exclude-a-world-from-detection.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.