Tags
Creators
Details
1.2.2
Compatibility
Required content
Changes
THIS VERSION REQUIRE PACKETEVENTS TO WORK!
- Fixed a lot of errors, false flags and improved checks.
- Added new conditions for detection, like maxium ping and minium TPS. (Only apply in some checks with default configuration, but, you can apply it in any check adding manually)
- Added new placeholders ({ping} and {tps}) for verbose and logs.
Apparently, 1.7.x doesn't work with PacketEvents, I recommend use legacy versions for the moment. Probably some checks go to work with Bukkit Events if packetevents isn't in the server, like legacy versions (but with ProtocolLib).
Reset your checks.yml and language.yml if you want this changes, if you don't reset, this still go works correctly with your actual config (if is 1.2.1).
Report any error or give your suggestion in the discord server support.
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:q9Lcd0FU:VrGcEQw9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:q9Lcd0FU:VrGcEQw9"
}

