> 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/scope-and-non-goals.md).

# Scope and non-goals

The plugin detects redstone clocks, tells staff or the console about them, and can disable or destroy them, so the server spends its time on something else. Preventing players from doing harm with heavy redstone is a welcome side effect rather than the point.

It is a re-creation of [Trafalcraft's antiRedstoneClock](https://gitlab.com/Trafalcraft/antiRedstoneClock), rewritten from scratch with support for current PlotSquared and WorldGuard versions.

## This is not a performance tool

Removing a clock frees whatever that clock was costing, and nothing else. The plugin will not make a server run better on its own, and a server with performance problems that are not caused by redstone will have exactly the same problems afterwards. It also does its own work only while the server is keeping up — when TPS leaves the configured range, detection pauses rather than adding to the load.

## Paper, and Folia

The plugin is developed against Paper. Folia is supported explicitly: the plugin declares Folia support and ships region-aware schedulers for it, and the build has dedicated Folia run tasks.

Spigot, CraftBukkit, hybrid servers and Paper forks are not supported. They may well work — but if something breaks specifically because of a fork, that is not a case the project takes on. The same applies to Minecraft 1.13 and earlier: not supported, not planned.

The authoritative list of versions the project builds and tests against is in [Supported versions](/antiredstoneclock-remastered/reference/supported-versions.md). The plugin declares an API version of 1.19, so it may load on servers outside that list — untested and unsupported.

## One clock detector per server

Running a second anti-redstone-clock plugin alongside this one is not a supported setup. Two plugins counting the same events and both breaking blocks produce results neither of them intends, and neither can be diagnosed from the other's log.

Related: [How detection works](/antiredstoneclock-remastered/background/how-detection-works.md) · [Report an issue](https://github.com/OneLiteFeatherNET/AntiRedstoneClock-Remastered/issues)


---

# 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/scope-and-non-goals.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.