AntiRedstoneClock-Remastered

This plugin is inspired by https://gitlab.com/Trafalcraft/antiRedstoneClock

We re-created the whole code and improved everything. On top, we support Plotsquared v7 and Worldguard v7.

Goal

The goal of this plugin is to detect redstone clocks, inform staff or console about active ones and optionally destroy / disable the redstone clocks so your server can save performance for something else. Also it can prevent players doing harm with heavy clocks, but this is more of a side effect.

Not a goal

It's not planned to support Paper forks or spigot directly - this plugin is developed to work on Paper, if you are using a fork of paper or spigot and it doesn't work because of your fork, you are likely on your own then. Also this plugin is not a "performance tool", it won't make your server run better directly. Third, support from 1.13 backwards likely won't happen.

Minecraft Version Support

Only the last 2 versions of a major Minecraft are supported. For Minecraft version 1.19, it would be 1.19.4, For Minecraft version 1.20, it would be 1.20.6 and so on

Features

• 1.20+ Support
• Java 21 only support
• Plotsquared v6 and v7 support
• WorldGuard Support
• 1.20,1.21 ready
• Clock detection
• Sculk support
• Config Migration(Soon)
• Prevent duplicated loading of anti-redstoneclock plugins

[!CAUTION] The "world" world is ignored by default

Contribution

You want to help us? Sure go for it, we would love to see your contribution! You can look for open issues or if you have a nice idea, please open an issue or ask us on discord if you can add your feature with a PR. Communication is key.

Dependencies (soft-depend, can be used together)

• Plotsquared v7 https://github.com/IntellectualSites/PlotSquared
• Worldguard v7 https://github.com/EngineHub/WorldGuard

Permissions:

antiredstoneclockremastered.notify.admin

[!CAUTION] All others can be taken from the Plugin.yml or use LuckPerms, which are automatically suggested there

Commmands

• /arcm reload
• Reloads the config
• /arcm help
• Shows all commands and descriptions
• /arcm display
• Shows current cached redstone clocks

More information / external links / Download

Hangar: https://hangar.papermc.io/OneLiteFeather/AntiRedstoneClock-Remastered

Modrinth: https://modrinth.com/plugin/AntiRedstoneClock-Remastered

Discord: https://discord.onelitefeather.net

Release Cycle

Important Announcement: While we have already been using Semantic Versioning (SemVer) for our releases, starting from July 24, 2025, we will be implementing the "semantic-release" tool to automate this process.

What is Semantic Versioning?

Semantic Versioning follows the format of MAJOR.MINOR.PATCH (e.g., 2.4.1):

• MAJOR version increases when incompatible API changes are made
• MINOR version increases when functionality is added in a backward-compatible manner
• PATCH version increases when backward-compatible bug fixes are implemented

How Commits Affect Version Numbers

Different types of commits will automatically trigger different version increments:

1. MAJOR version bump (e.g., 1.2.3 → 2.0.0)
2. Breaking changes to the API
3. Commits with BREAKING CHANGE: in the commit message

4. Commits with ! after the type (e.g., feat!: remove deprecated methods)

5. MINOR version bump (e.g., 1.2.3 → 1.3.0)

6. Commits with type feat (new features)

7. Example: feat: add new command for clock statistics

8. PATCH version bump (e.g., 1.2.3 → 1.2.4)

9. Commits with type fix (bug fixes)

10. Example: fix: resolve issue with clock detection in nether worlds

11. No version bump

12. Commits with types like docs, style, refactor, test, chore
13. Example: docs: update README with new information

Example Release Flow

1. Current version: 1.2.3
2. Developer adds a new feature: feat: add support for custom clock detection rules
3. Version becomes 1.3.0
4. Developer fixes a bug: fix: prevent false positives in clock detection
5. Version becomes 1.3.1
6. Developer makes a breaking change: feat!: redesign configuration format
7. Version becomes 2.0.0

Update Triggers

Please note that version updates can be triggered by: - Pull Requests (PRs): Any merged PR can trigger a version update based on its commit messages - Renovate Bot: Dependency updates through Renovate will also trigger appropriate version updates

References

• Official Semantic Versioning specification: https://semver.org/
• Conventional Commits standard: https://www.conventionalcommits.org/
• Semantic Release tool: https://github.com/semantic-release/semantic-release