Links
Tags
Creators
Details
Licensed GPL-3.0-only
Published 2 years ago
Updated 9 months ago
All versions
1.2
Release
BanTools 1.22 years ago 256
Compatibility
Minecraft: Java Edition
1.21–1.21.5
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
Platform
Velocity
Changes
BanTools | v1.2 Features
- Ban Functionality:
- Supports banning by UUID, IP address, or player name.
- Default ban duration is permanent (if no duration is specified).
- Supports specifying ban duration (e.g.,
7dfor 7 days,2024/1/10-2025/01/10for a custom date range). - Automatically kicks banned online players.
- Unban Functionality:
- Supports unbanning a player using the
/bantools unbancommand. - Unbanning does not delete the ban record but marks the ban status as invalid.
- Supports unbanning a player using the
- Kick Functionality:
- Supports immediately kicking a player using the
/bantools kickcommand. - A custom kick reason can be specified (default uses the configured reason in the config file).
- Supports immediately kicking a player using the
- Automatic Unban Mechanism:
- If a ban duration is specified, the ban will automatically expire when the time ends.
- Multi-Condition Matching:
- On login, checks if UUID, IP address, or player name matches any ban records.
- If any condition matches, the player is considered banned.
- Configuration File Support:
- All ban records are stored in the
config.conffile, which supports manual editing. - The configuration file allows setting default ban and kick reasons.
- All ban records are stored in the
- Dynamic Configuration Reload:
- Supports dynamically reloading the configuration file via the
/bantools reloadcommand without restarting the server.
- Supports dynamically reloading the configuration file via the
- Real-Time Synchronization:
- All ban, unban, and kick operations are synchronized in real-time across all downstream servers.
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:ZLfM0fUb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:u9OtVM1S:ZLfM0fUb"
}

