All versions
1.0.0
Release
ClientPolicy 1.0.02 months ago 82
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Changes
Initial release.
- Channel, brand and mod loader handshake fingerprinting, buffered from login
- Wildcard signature database in signatures.yml with per-mod categories
- ALLOWLIST and BLOCKLIST profiles bound via clientpolicy.profile.<name>
- Tiered LOG -> WARN -> KICK ladder with escalation threshold and counter reset
- Delayed first scan plus a rescan window so late channel registration cannot dodge enforcement
- /clientpolicy rules and /clientpolicy check for player-facing transparency
- /clientpolicy inspect for writing your own signatures
- SQLite audit log with /clientpolicy history and configurable retention
- Separate action for channels matching no signature
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:tmlnLXud:bkJV5DaN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:tmlnLXud:bkJV5DaN"
}

