Tags
Creators
Details
1.2.1-alpha.1+26.3.folia
Compatibility
Changes
BanHammer 1.2.1-alpha.1 — bStats 3.2.1, service 34724.
Adds optional server/player usage statistics using the official bStats library, relocated into a private namespace. No dummy chart or player identity collection. Official reporting intervals and global opt-out are unchanged. Disable in plugins/BanHammer/metrics.yml (enabled: false); /bh reload for Bukkit, restart for Folia. plugins/bStats/config.yml also controls global opt-out. The metrics worker closes on shutdown/reload; unavailable metrics do not prevent gameplay.
Automatic updater: updates.yml controls enable/disable, automatic download versus notification, startup checks/delay, interval, allowed channels, size limit and JAR backups. Only the official BanHammer project, exact Minecraft version and matching edition are eligible. HTTPS, SHA-512, size and plugin identity/version are verified. A verified file is staged for the NEXT server restart; the server is never forcibly restarted and existing configurations are kept. A previously staged file is never overwritten; removing an unwanted staged update is a manual action.
Exact artifact passed real-server checks for initialization, local count collection, plugin/global opt-out and scheduler cleanup, without submitting test statistics. No new full gameplay certification is claimed for this artifact. Folia native alpha: no Bukkit configuration/crafting GUI, recipes or optional enchantment mode. Production ingestion by bStats is not yet independently verified. Existing servers need this new JAR to report; older downloads are unchanged.
Minecraft 26.3; Java 25; SHA-256 20067c69e599c741d47a61625c8fc90c9cfaa7a3a1e07ffccf4364263b507658.
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:5nNJavDu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dyCqCua0:5nNJavDu"
}

