1.0.1
Compatibility
Changes
📋 BanSentinel 1.0.1 - Compatibility & Visual Fixes
This update focuses on cleaning up the core punishment logic and fixing issues with how messages appear to players. I’ve refactored the internal handling to ensure it works smoothly on 1.21 without any version-specific errors.
✨ What’s New
Fixed Kick Screen Colors: Ban reasons and appeal links now properly display colors (like &c for red) instead of showing the raw codes.
Cross-Version Stability: Refactored core code to ensure full support and stability across the latest Spigot and Paper releases.
Code Optimization: Removed unnecessary overhead and cleaned up command execution logic to be more lightweight.
Config Cleanup: Simplified config.yml and plugin.yml for easier management.
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:Dts9Z66S:wUuys3gW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Dts9Z66S:wUuys3gW"
}

