1.1
Compatibility
Changes
Short Description: 20TPS 1.1 is a performance optimization and anti-exploit plugin for Minecraft servers. It helps maintain stable TPS, prevents common lag sources, and protects players from abuse such as redstone spam, TNT explosions, macro usage, login flooding, and combat exploits. Full Description: 20TPS 1.1 is a powerful performance and protection plugin designed for Paper and Spigot-based Minecraft servers. It combines server optimization with anti-exploit security to keep gameplay smooth and fair. Key features include: • TPS and server performance monitoring • Item despawn optimization • Void and Nether roof protection • Redstone, TNT, chunk, and entity limits • Wither, mob stacking, and mechanism control • Login throttling and anti-bot protection • Chest macro and fast-click detection • Combat reach and protection checks • /20tps status command • Crash detection and server safety reporting This version focuses on improving overall stability, reducing false positives, and making the protection systems more consistent under active server conditions. Release Notes: 20TPS 1.1 – Stabilization and protection update This release improves the plugin’s reliability and strengthens its anti-exploit and performance safeguards. Changes: • Improved login throttling and bypass handling • Refined chest macro and fast-click detection • Optimized combat protection and reach checks • Stabilized redstone, TNT, and chunk-limit behavior • Improved void and Nether roof protection • Updated status command output and in-game alerts • Enhanced crash reporting and server safety messaging Compatibility: Minecraft versions: 1.20.5 - 1.21.8+ Paper/Spigot-supported server builds using the 1.20 API
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:j4S3ujeA:z0gdLPGx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:j4S3ujeA:z0gdLPGx"
}

