> 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/notify-staff-in-game.md).

# Notify staff in game

Send a clickable chat message to your staff whenever a clock is detected.

**Before you start:** none.

1. Grant your staff group the permission `antiredstoneclockremastered.notify.admin`.
2. Give the same people operator rights on the server.
3. Make sure `admins` is listed under `notification.enabled` in `config.yml`.
4. Apply the change:

   ```
   /arcm reload
   ```

## Check it worked

Build a redstone clock in a watched world. Staff members who are online receive a message from `[AntiRedstoneClock]` naming the coordinates. Clicking the message teleports them there.

## If it does not work

The in-game notification requires **both** the permission and operator status. A staff member who holds `antiredstoneclockremastered.notify.admin` but is not an operator receives nothing.

See also: [Permissions reference](/antiredstoneclock-remastered/reference/permissions.md) · [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/notify-staff-in-game.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.