Tags
Creators
Details
1.3.0+26.1.bukkit
Compatibility
Changes
BanHammer 1.3 โ staff tools and optional visuals
The ordinary survival Ban/Pardon hammers remain the default. Enable the separate staff mode with /bh staff while holding a Ban Hammer: right-click bans, left-click kicks/jails, sneak-click cycles configurable presets. Adds moderation commands, mutes, warning policies, jail, history, statistics, appeals, SQLite/MySQL storage and cancellable API events.
The ban screen shows reason, remaining duration and staff attribution. /bh pack offers an optional visual pack; declining does not kick. Older versions use a netherite axe fallback. The separate original 3D pack is an alpha whose graphical rendering remains unverified. Custom model values are 710001/710002.
Fixes preset cycling when Bukkit predicts a cancelled air click and accepts permanent before ISO-8601 duration parsing. Database changes commit before enforcement; temporary expiry and persistence are covered by automated tests. Staff sanctions cannot be reversed by ordinary survival pardon gameplay by default.
Install the exact Minecraft JAR, back up the BanHammer folder and server ban files, replace the old JAR, then restart. /bh craft goes straight to crafting. Configure new options in moderation.yml; keep your existing gameplay configuration. Use /bh mute, etc. if another plugin owns a bare alias. No client mod is required.
Exact-file validation โ Minecraft 26.1, spigot: Startup, console commands and clean shutdown only; no client gameplay certification on this version. The new moderation scenario has not been repeated on this exact Minecraft version; this compatibility build is beta. The same source passed the full scenario on Paper 1.19 and 1.21.1. Survival ban/pardon and death-item anti-duplication were separately tested on the 1.21.11 Bukkit build. MySQL-compatible persistence was tested with MariaDB 11.4.13 on Paper 1.21.1. This is not a player-capacity/TPS guarantee. Discord delivery, Essentials jail integration, other forks/modpacks and graphical client rendering are not independently certified. Use one database per server; complete proxy/network unban reconciliation is not supported. Existing native/Folia/Sponge alphas do not acquire the Bukkit 1.3 features.
SHA-256: 2ece89e8f5ac8a46423b49057e745adf61372079b7562e1b33d6a4a29ff61dd5
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:dyCqCua0:OG4ZPqrc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dyCqCua0:OG4ZPqrc"
}

