1.3.5
Compatibility
Changes
It is recommended to delete the config.yml to set up the new configuration.
-
Changes and Improvements ā We have improved the optimization of using op2. Now, after applying a ban, there will be a pause during which mass banning will stop for a period of time while the IPs being blacklisted are processed. This can be customized in the config.yml; I recommend setting it to 5 minutes or more for better performance.
-
If the bans exceed 7000 IPs per second, there will be a random interruption in the banning process to stabilize and process the sanctions.
-
Now, op1 can ban a dynamic IP from 0 to 255 in 2-3 seconds without crashing the server.
-
Additionally, both systems operate on separate threads to prevent saturation of the main thread when applying mass bans, especially when using op2.
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:fRqinjfY:f8Iy45kk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fRqinjfY:f8Iy45kk"
}

