Tags
Creators
Details
1.1.1
Compatibility
Changes
Changelog
Improved overall plugin stability and startup safety. Better reload handling. The plugin now recovers more cleanly after config reloads. Reduced false detections, so normal player builds are much less likely to be affected. Added a new smart chunk protection system. When one area starts acting suspicious, the plugin can slow down that area first before fully removing parts of the machine. Faster reaction to heavy lag machines. Dangerous machines are stopped earlier, before they can do serious damage. Improved protection against redstone clocks, hopper loops, dispenser spam, TNT/falling block abuse, and entity spam. Better handling for armor stand, item frame, villager, projectile, and vehicle spam. Added optional ProtocolLib support for earlier packet checks. If ProtocolLib is installed, some bad actions can be blocked sooner. Improved exploit protection for unsafe items, books, signs, payloads, chat, commands, and suspicious inventory contents. Better cleanup logic and safer machine removal. Added more smart limits based on player activity and server situation, so protection feels more fair. Improved performance of background scans. The plugin now uses a smarter scan system and avoids repeating expensive checks too often. Better behavior on low TPS. The plugin now adjusts itself more carefully when the server is already under load. Added more config options for tuning protection and performance. Added better update handling and admin notifications. Improved REST API safety and startup checks.
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:saSMcpEZ:GcknMFML"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:saSMcpEZ:GcknMFML"
}

