ToolCore

The items a player holds that do something a vanilla item cannot — defined entirely in
YAML, and built to cooperate with the plugins you already run.

A catalogue, not a hardcoded list. Every item lives in items.yml: its kind, its
tuning, its name and its lore. Add an entry, reload, and the item exists. The shipped
3×3 and 5×5 pickaxes are the same code with a different radius — write radius: 3 and
you have a 7×7 without touching Java.

Identity that survives everything. An item is recognised by a hidden persistent-data
id, never by its display name. Rename it in an anvil, park it in a shulker box for a
month, restart the server — it is still what it was. And renaming a plain pickaxe to
look like one grants nothing.

Tree feller. A bounded, iterative flood fill that travels through logs and leaves,
so it finds the branch on the far side of a canopy, but breaks only the logs. Hard-capped
at max-blocks, and it refuses to look into unloaded chunks.

Area pickaxes. A flat slab in the plane you are looking at: mine a wall and you tunnel
a corridor, mine the floor and you strip a layer.

Selector wand. Two corners per player, persistent across restarts, with a block
count. Right-click, sneak-right-click or left-click — all three conventions work. It
never breaks, places or opens anything.

Mob stacking, optional. A deliberately small stacking core — count, lock, name,
split, merge — plus a stack nametag, a mob cage and a mobstack separator. It does not
scale experience or loot, which is exactly what lets it sit next to other plugins. Already
run a stacker? Switch the whole module off and keep everything else.

The reason to buy this one

Protection that actually works, with any plugin.

Most area tools hook one specific protection plugin's API. That works until you run a
different one, or two, or one they never tested against.

ToolCore fires a real, cancellable BlockBreakEvent for every extra block before
breaking it. Your claim plugin, your logging plugin and your anti-xray plugin all see an
area swing as what it is: a series of ordinary player block breaks. Each keeps exactly
the control it already had.

• A cancellation skips exactly that block — the sweep continues, so a 5×5 at a claim
  border breaks the outside and leaves the inside untouched.
• If the block the player actually mined is denied, no sweep starts at all.
• setDropItems(false) is honoured too.
• CoreProtect logs every block. Rollback works.
• No API version to keep up with, and nothing to break on a Minecraft update.

There is a five-minute verification in the bundled docs so you can prove it on your own
server before you go live.

Also worth knowing

• No dependencies. Nothing in depend:, nothing in softdepend:. No database, no
  GUI library, no permission plugin required.
• No recipes, deliberately. Items are handed out with /customitem give, which any
  crate, shop, quest or rank plugin can run as console. ToolCore hands out items; it does
  not decide how players earn them.
• Permission-driven, never rank-driven. One node per item, defaulting to on, each
  overridable in the catalogue. No rank name anywhere in the plugin.
• Bilingual out of the box. English and Dutch ship configured. Every message, item
  name and lore line takes one value or one per language, and a player's language drives
  both chat and the text on the item they are handed.
• Bounded by design. max-blocks is a hard cap, the flood fill is iterative and
  never recursive, the stacking scan is interval-based with a per-scan merge budget, and
  caged mobs live in the item's data rather than as entities that could leak.
• Two modules, each switchable, with one clear log line when a dependency is off —
  never a half-started module.

Commands

| Command | What it does |
|---|---|
| /customitem give <player> <id> [amount] | Hand out a catalogue item |
| /customitem get <id> [amount] | Give one to yourself |
| /customitem list · info <id> | What exists, and how it is tuned |
| /customitem pos | Your wand selection and its block count |
| /stackablemobs [page] | Which mob types can stack |
| /toolcore <status\|reload> | Status and a live reload of everything |

Full command and permission reference in the bundled docs/.

Requirements

• Paper 1.21 or newer
• Java 21 or newer
• No dependencies

Spigot and Folia are not supported.