Java Edition data pack

VeinMiner

Ore families, structural tree families and custom groups share one owner-safe queue while keeping their matching rules separate.

Choose versionServer-sideCustom blocksVanilla loot

01 / Install

Install one VeinMiner build

Choose one mining pack. Do not load VeinMiner together with separate OreVeinMiner or TreeVeinMiner builds. They detect the same break and would compete for the same connected blocks.

1

Put the selected ZIP in world/datapacks.

2

Run /reload as an operator.

3

Crouch with the correct tool and mine the first block normally.

02 / Use

One family per operation

Ores

Coal through ancient debris use family-specific matching and harvest tiers.

Trees

Logs, wood, stems and hyphae are included; leaves and wart blocks are not.

Custom

Added IDs use the held tool's registered loot table.

03 / Commands

Player and operator controls

04 / Add blocks

Put connected IDs in the same group

05 / Remove blocks

Exclusions override inclusion

{
  "replace": false,
  "values": [
    "minecraft:ancient_debris",
    { "id": "examplemod:machine_casing", "required": false }
  ]
}

06 / Loot & durability

The held tool remains the loot context

Additional blocks call their registered loot tables with the held tool. Fortune, Silk Touch and modded loot conditions therefore remain part of the result. Ore experience is emitted only where vanilla mining would award it.

07 / Leaves

Leaf cleanup is deliberately separate

VeinMiner's tree-only hook fires for structural tree families and never for ore operations. LeaveDecay listens to that hook, so mining a diamond vein cannot create a leaf-cleanup queue.

Open LeaveDecay documentation →