Links
Tags
Creators
Details
1.4.0
Compatibility
Changes
๐ง Version update log
###V1.4.0 (latest version) Major new features:
- ๐ ** FakeBan: A brand new temporary ban feature that supports automatic expiration and secondary confirmation mechanisms
- ๐ ** Whitelist Protection System * *: protects designated players from bans, kicks, and temporary bans, preventing administrators from being maliciously banned
- ๐ ** Intelligent Tab Completion * *: Comprehensive command completion support to improve operational efficiency and accuracy
- ๐ ** Double confirmation mechanism * *: Fakeban operation requires executing the same command again within the specified time to take effect
- ๐ ** Automatic expiration cleaning * *: The temporary ban will be automatically lifted after it expires, without the need for manual intervention
User experience improvement:
- ๐ ** Intelligent Tab Completion System * *: Comprehensive command completion support, greatly improving operational efficiency
- ๐ ** Permission aware completion * *: intelligently display available commands based on user permissions
- ๐ ** Intelligent player filtering * *: automatically excludes players protected by whitelist to avoid misoperation
- ๐ ** Quick completion of common options * *: Quick selection of commonly used parameters such as ban reason and duration
- ๐ ** State awareness completion * *: unban displays banned players, unfakeban displays temporarily banned players
New command: -Bantools Fakeban<Player>[Reason] - Temporary ban on player (requires secondary confirmation) -/batools unfakeban<player>- Lift temporary ban
User experience improvement: -Intelligent Tab Completion: Display available commands based on permissions, automatically complete player names and common parameters -Player name filtering: Automatically exclude players from the whitelist protection during Tab completion -Common options: Provide quick selection of common reasons and duration of bans -State awareness: The unban and unfakeban commands only display players in their corresponding states
Configuration enhancement: -Unified configuration file: All configurations are centralized in the main configuration file, including whitelist settings -Added 'fakeban' configuration section, supporting custom temporary ban duration and confirmation message -Support customizing default reasons for temporary bans and confirming timeout periods
Technical improvements: -Optimized command processing architecture, supporting dynamic completion -Improved player list acquisition mechanism -Enhanced unified management of configuration files
Security improvement: -All operations (ban, kick, fakeban) support whitelist protection -Prevent administrators from being maliciously banned due to permission leakage -Temporary ban and regular ban are completely independent and do not affect each other
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:u9OtVM1S:udtKe918"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:u9OtVM1S:udtKe918"
}

