Bell Claims Reforged

A maintained fork of Bell Claims by Mizarc, rebuilt for Minecraft 26.x and licensed MIT. All original credit goes to Mizarc. This fork exists to keep the plugin running on current server versions, fix what breaks along the way, and build on it.

Claim your land with a bell. No commands to memorise, no chunk grid to fight, no wand to lose. Place a bell, sneak and right-click it, and the block you just put down becomes the heart of your claim.

Why a bell

Most land protection plugins hide your claim behind a command and a coordinate list. BellClaims Reforged puts it in the world. The bell is the claim: you can see it, walk to it, ring it, and break it if you want the land back. Three hits within ten seconds and the claim is gone.

And if that happens by accident, or because someone else did it, you get it back with /bellclaim restore.

Features

Claiming

• Bell-anchored claims. Every claim has a physical centre you can find and defend.
• Bells on demand. Bells can't be crafted, so /bellclaim hands them out: one bell for every claim a player is allowed.
• Grows with playtime. Players start with a set number of claims and blocks of land, and earn more the longer they play, up to a maximum you choose. /bellclaim limits shows where they stand and when the next claim comes.
• Claim bells only (optional). Bells found in villages or bought from villagers can be kept from starting claims, so the allowance is a real limit.
• Bells can't be lost. Drop a claim bell you don't need and it goes back to your /bellclaim. Die with one and it goes back too, safe from lava and other players.
• Non-square borders. Grow your claim in partitions that follow the shape of what you built.
• Visible borders. Claim edges are drawn in the world, so boundary disputes end before they start.
• Web maps. Claims appear on BlueMap and squaremap automatically when either is installed.

Managing

• Menus, not commands. Rename, change the icon, set permissions, transfer ownership, all from the bell. Names and descriptions are typed in the chat.
• Per-player trust and presets. Give specific players specific permissions, or apply a preset in one click. Players can be trusted while offline.
• Fine-grained permissions. Chests, furnaces and workstations (anvils, enchanting tables, smithing tables…) are separate permissions, so you can let a friend smelt without opening your storage.
• Flags. Toggle mob griefing, fire spread, pistons, explosions and more per claim. Animals and villagers have their own flag, so bees still make honey in a claim that blocks hostile mobs.
• PvP flag. Fighting is blocked in claims unless the owner allows it, including arrows, TNT, pets and potions.
• Bans. Keep a player out of your claim: stopped at the border, no teleporting, pearling or riding in.
• Activity log. See who broke, placed or opened what in your claim while you were away, including attempts your claim refused.
• Welcome message. Greet visitors with a title on screen when they walk in.

Neighbours

• Doorbell. Ringing someone's bell notifies the owner and their trusted players.
• Mailbox. Sneak and right-click someone else's bell to leave them items, no trust needed. They collect it from their claim menu.

Safety net

• Restore a destroyed claim. /bellclaim restore brings a claim back whole: shape, flags, trusted players, bans. Breaking your own bell gives it back to you, and restoring puts it back in place.
• Inactive claims. Optionally archive claims of players who stopped playing, restorable if they return.

For server staff

• /bellclaimadmin: list any player's claims with click-to-teleport, inspect, transfer, delete (restorable), view activity logs, and reload the config without a restart.
• Give claims and land. /bellclaimadmin give hands a player extra claims (each with its bell) or extra land, on top of what they earn, and replaces bells that were really lost.
• Server claims. Turn spawn, a market or a public farm into a claim owned by the server, outside everyone's limits. Destroyed server claims can be restored by staff.
• /bellclaimadmin override to bypass protection when moderating.
• Config updates itself. New settings are added to your config.yml automatically on update, with your values kept and a backup of the old file.

Languages

• English and French. Each player sees the plugin in their game's language, or you can show one language to everyone.

Getting started

1. Drop the .jar in your plugins/ folder and restart.
2. Get a bell with /bellclaim and place it.
3. Sneak and right-click it.
4. Type the claim's name in the chat. Done.

Every player command starts with /bellclaim (short form /bc), every staff command with /bellclaimadmin (short form /bcadmin).

Command	What it does
/bellclaim	Get a claim bell
/bellclaim help	List every player command
/bellclaim tool	Get the claim tool to reshape your claims
/bellclaim menu	Menu of everything you own
/bellclaim list	Your claims as text
/bellclaim limits	Your claims and land, and how they grow
/bellclaim restore	Bring back a destroyed claim
/bellclaim trust <player> <permission>	Trust someone in the claim you stand in
/bellclaim ban <player>	Keep someone out of the claim you stand in
/bellclaim greeting <message>	Set your welcome message
/bellclaimadmin help	Staff tools (operators)

Every player feature works out of the box without a permissions plugin. Staff tools default to operators.

Requirements

• Paper or Purpur on Minecraft 26.1, 26.2 or 26.3 (Spigot is not supported)
• Java 25
• Optional: Vault + a permissions plugin such as LuckPerms for per-rank limits; BlueMap or squaremap for web maps

What this fork changes

Upstream Bell Claims 0.5.1 targets 1.21.x and does not run on 26.x.

Menus work again, and should keep working. The bundled menu library had no support for 26.x and nothing opened. It has been removed entirely: menus are built on plain Bukkit inventories and text is typed in the chat, with no version-specific server internals anywhere. A future Minecraft release can no longer take the menus out.

Bugs fixed, including some that predate 26.x:

• The claim list command threw an error for anyone with fewer than eleven claims, and printed the wrong columns.
• The trust list command dropped the last entry of every page and made page two unreachable.
• Vault was listed as optional but required, so servers without it failed to enable the plugin.
• Permissions were undeclared, which locked non-operators out on servers without a permissions plugin.
• Two database connection pools were opened on the same file.

Added: everything under Features that isn't in upstream, from bell dispensing and playtime progression to bans, mailboxes and server claims.