1.5.0
Compatibility
Changes
First of all, a huge thank you to the community for using and supporting this plugin! Your feedback is what keeps this project moving forward.
I’m always looking to improve, so please feel free to leave your suggestions or feedback in the discussion section. I’d love to hear how I can make this even better for your servers!
Version 1.5.0 is a major update that shifts the plugin's logic to be more user-friendly while giving Admins surgical control over redstone machines.
Major Logic Change: Placement vs. Usage In version 1.3.0, the plugin completely blocked the placement of redstone components. In v1.5.0, we’ve improved the player experience:
Allow Placement: Players can now place redstone blocks/items freely (no more glitchy "disappearing" blocks).
Smart Restriction: Even though they can place them, the redstone logic will not trigger or will be strictly limited based on your config/whitelist settings. This prevents server lag while keeping the building experience smooth. What’s New in 1.5.0?
- Advanced Whitelist System (Player-Specific Limits) You can now grant special privileges to VIPs, Builders, or trusted players without opening the floodgates for everyone.
Smart Radius Scan: When a redstone circuit triggers, the plugin scans a 15-block radius. If a whitelisted player is found, the system applies their specific limits instead of the global server restriction.
Limit Priority: If multiple whitelisted players are near a machine, the plugin automatically grants the highest limit available among them to ensure their machines run smoothly. 2. TPS & Performance Optimization
Deep code refactoring to ensure that the new scanning logic and event handling have zero impact on TPS.
Optimized data handling for whitelisted players to keep the plugin lightweight for large survival servers. New Whitelist Commands: Manage your trusted players with these new commands:
/antiredstone whitelist add <player>: Add a player to the whitelist.
/antiredstone whitelist remove <player>: Remove a player from the whitelist.
/antiredstone whitelist list: View all whitelisted players.
/antiredstone whitelist setlimit <player> <count> <time_ms>: Set a custom limit for a specific player. Example: /antiredstone whitelist setlimit Hieu 100 2000 (Allows Hieu's machines to trigger 100 times every 2 seconds). /antiredstone whitelist place <player> <true/false>: Toggle whether a specific player can bypass placement restrictions (if any are enabled in config). Note: Please update your config.yml or backup your old one before installing v1.5.0 to ensure all new features are initialized correctly.
Enjoy a lag-free server!
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:Fhl5i4IH:EVwbCCOO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Fhl5i4IH:EVwbCCOO"
}![AntiRedstone| Advanced Redstone Lag Prevention [1.18 - 1.21.4]](https://cdn.modrinth.com/data/Fhl5i4IH/77973c50780056f5d42a4fa12a8cc793b825c4b9_96.webp)

