BanHammer 🔨

Make every fight count — and give your staff a hammer that means business.

Defeat a rival with the Ban Hammer to ban them. To bring them back, defeat their attacker with the Pardon Hammer, then choose one or all eligible players to pardon. Build a survival challenge around these items, or enable a separate staff mode for everyday moderation.

Download your server's edition · Wiki

Survival hammers, your rules

• Temporary or permanent bans, configurable cooldowns and a custom reason.
• Independent switches for Ban and Pardon gameplay, world exclusions, optional operator/bypass protection, survival-only rules and kill-attribution settings.
• Keep or consume the Ban Hammer after a successful action.
• Customize materials, names, lore, vanilla enchantments, attributes, glow, unbreakability, model data, sounds and particles.
• Create your recipes in game: /bh craft opens the crafting editor directly. Place the ingredients and result, save and enable the recipe; saved recipes survive restart. Ingredient matching uses vanilla material identity rather than ingredient names/lore.
• /bh opens the administration menu; /bh doctor checks the installation and recipe state.

Before Minecraft's mace exists, the default item falls back to a netherite axe. An optional resource pack can give it a hammer appearance; it does not add newer vanilla smash mechanics to an older server.

Staff moderation 🛡️

Staff mode is explicitly enabled on a hammer, keeping ordinary survival items separate. Right-click a player to use the selected ban preset; left-click for a kick or jail action. Sneak-click to cycle the independent presets, or select one with /bh preset. Short-range left-click targeting checks solid-block obstruction and is capped at five blocks.

• Bans and IP bans: reasons, temporary/permanent durations, automatic expiry and manual release.
• Clear ban screen: configurable colored lines with player, reason, staff member, remaining time, expiration date and server placeholders.
• Mutes: configurable blocking of chat, commands, sign edits and book edits.
• Jail: a saved location, movement boundary, command/teleport restrictions, damage protection and return to the previous position. /bh setjail sets the built-in location.
• Warnings: expiration, configurable thresholds and an automatic temporary ban policy; consumed warnings prevent the same threshold from being reused indefinitely.
• Appeals: connected players can submit an appeal; staff can view, approve or deny it. Approval releases the specific linked sanction. Banned players need your external appeal process because they cannot join to type a command.
• Records: persistent history, active-sanction lists, staff statistics, a leaderboard and a protected moderation dashboard.
• Presets: duration, reason, IP-ban mode, sound, visual lightning, particles and bounded knockback. Optional staff-hammer block protection helps avoid accidental breaks.

Administrative bans are protected from ordinary survival Pardon gameplay by default. Individual permissions, self-target protection, optional operator/bypass protection and an action cooldown control access.

Optional weapon effects

Prefer using an ordinary sword or axe? Enable the server-managed Ban/Pardon enchantment effect through configuration or /bh enchant on. It is disabled by default.

Configure allowed weapons, effect names, maximum level, XP-level cost, command application and the ban-duration multiplier per level. /bh enchant ban 2 applies the ban effect to the held eligible weapon; /bh enchant pardon 1 applies the pardon effect; /bh enchant remove removes it. Disabling the feature pauses existing effects until re-enabled.

This is a persistent plugin effect, not an enchantment registered in the vanilla enchanting table. It does not create enchanted books, anvil transfer or new client content. Pardon levels are stored/displayed but do not increase the number pardoned.

Optional resource packs

You can supply your own compatible pack through an HTTPS URL and SHA-1 in moderation.yml, with a custom prompt and optional join offer. /bh pack offers it; refusing never disconnects the player. /bh pack apply updates model data on existing genuine hammers.

Model values default to 710001 for Ban and 710002 for Pardon. The separate original BanHammer Visuals alpha includes MACE/NETHERITE_AXE models in exact-version ZIPs. Its archive/JSON checks passed; graphical Minecraft rendering remains unverified. Other materials require matching models. Merge item definitions with an existing server pack when necessary; optional ViaVersion protocol variants can be configured, but mixed-client integration is not separately certified.

Languages and configuration 🌍

English and French survival message files are provided. Moderation message presets include English, French and German. You can translate editable UTF-8 message values into your server's language, choose lang and reload. Missing survival language files receive an editable English template; moderation message keys fall back to English. Some command feedback and GUI labels remain fixed-language, so this is partial localization, not automatic translation into every language.

First startup generates configuration automatically in plugins/BanHammer/. Commented files separate gameplay, moderation, optional statistics and automatic updates. Customize item appearance, recipes, protections, permissions, durations, XP costs, presets, messages, storage, history retention and pack delivery. Existing gameplay settings are preserved across updates.

Performance, persistence and safeguards

• Event-driven gameplay and cached active sanctions; no per-tick world/inventory scan.
• Background database work; new moderation sanctions are persisted before enforcement. SQLite uses WAL; the MySQL-compatible backend was tested with MariaDB.
• Periodic configurable expiry/synchronization checks, bounded webhook work and action cooldowns.
• Prepared SQL statements, configurable IP-display privacy and keyed HMAC matching for IP sanctions. HMAC is pseudonymization; server/proxy logs can still contain IP addresses.
• Protected inventory menus and tested prevention of retaining a duplicate victim hammer after ban/death/pardon/rejoin.
• Cancellable pre-punishment API events, applied/released events, and optional Discord notifications. Discord delivery and Essentials jail lookup are implemented but not externally runtime-certified.
• Optional bStats and configurable matching-version update downloads, applied on the next server restart. Neither is required to play; updates do not force a restart.

Use a dedicated database per server. Full proxy/shared-network unban reconciliation is not supported in 1.3; a distant database release can leave another server's permanent native ban in place. No universal compatibility, zero-lag or player-capacity guarantee is claimed.

/bh give YourName ban 1
/bh craft [ban|pardon]
/bh staff
/bh staff give YourName
/bh preset <ban|utility> <name>
/bh modgui
/bh ban|ipban|mute|jail <player> <duration> [reason]
/bh kick|warn <player> [reason]
/bh unban|unmute|unjail <player>
/bh history|warnings <player>
/bh stats [player]
/bh top
/bh active [type]
/bh setjail
/bh appeal <message>
/bh appeals
/bh approve|deny <appeal-id> [note]
/bh enchant <on|off|ban|pardon|remove>
/bh pack [apply]
/bh cooldown|reset|reload|info|help
/bh doctor

Also from Raylix2: KarmaCore · SmartLoot.