> 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/background/what-happens-to-a-detected-clock.md). # What happens to a detected clock Detection and reaction are two separate things, and the reaction is where most surprises on a fresh installation come from. Out of the box the plugin does not only report a clock: it also places a warning sign, breaks the block and drops it. ## The order of events When a block reaches the trigger limit, the plugin first sends every enabled notification, and only then decides what to do with the block. Notifications go out in a fixed chain — Discord, sign, console, in-game admins — and every target that is switched on gets its message. The sign target is unlike the other three: it does not send a message anywhere, it **replaces the block of the clock** with a sign carrying the configured warning text. After the notifications, the block is dealt with according to two switches. With `clock.autoBreak` off, nothing happens to the world and the clock keeps running. With it on, the block is removed — and `clock.drop` decides whether its items drop on the floor first, as if it had been mined with a silk touch pickaxe. ## What this means in practice The default configuration has both the sign target and automatic breaking enabled, and the two work against each other: the sign is placed on the clock's block, and the removal step then takes that same block away again. On a default installation you therefore rarely see the sign survive — and what drops on the floor is the sign, not the redstone component that caused the detection. Whichever behaviour you want, pick one of the two: * Leave the world alone entirely — [Report clocks without breaking them](/antiredstoneclock-remastered/how-to-guides/report-clocks-without-breaking-them.md). * Keep automatic breaking, but stop the signs — [Stop warning signs from being placed](/antiredstoneclock-remastered/how-to-guides/stop-warning-signs-from-being-placed.md). A sign the plugin placed is marked, and breaking it never drops a sign item. That is deliberate: the sign is a marker the plugin put into the world, not loot. ## What this is not Nothing is undone. The plugin keeps no record of what a removed block was, and there is no command to restore it. On a survival server that is an argument for switching automatic breaking off and treating the notification as a report for a human to act on. Related: [How detection works](/antiredstoneclock-remastered/background/how-detection-works.md) · [Configuration reference](/antiredstoneclock-remastered/reference/configuration.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/background/what-happens-to-a-detected-clock.md?ask=&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.