Protection Plugins

BusyMining has no hooks for WorldGuard, GriefPrevention, Lands, Towny or other protection plugins, and doesn't need them: everything that changes blocks goes through the standard Bukkit events those plugins already watch. Here's how each part of the plugin interacts with them.

Normal mining

Rewards (XP, Zeta, gemstones, fluxes, artifacts, Mysterious Dust) are handled at the end of the block-break event and skip any break that another plugin cancelled. If a player can't break a block in a claim, they earn nothing from it.

Enchantment extra-breaks

Explosive, Vein Miner and Sonic break extra blocks. Each extra block fires its own ExtraBlockBreakEvent, a subclass of Bukkit's BlockBreakEvent, before it's broken. Protection plugins see it as a normal break by that player and can cancel it; a cancelled extra block is left alone. Extra blocks never give rewards.

If your protection plugin only checks the first block a player breaks, test Explosive and Vein Miner at a claim edge before letting players use them on a busy server.

Minions

Minions are checked like their owner:

  • Placing uses vanilla's armour stand placement, so a player can't place a minion where their protection plugin wouldn't let them place an armour stand.
  • Mining fires an ExtraBlockBreakEvent with the owner as the player before each block. If the protection plugin cancels it, the minion leaves that block alone and tries another. A minion next to someone else's claim mines only the ores outside it.
  • A protection plugin can only answer for an online player, so a minion pauses while its owner is offline.

Plugins that log or reward breaks (CoreProtect, Jobs, mcMMO) also see these events, so minion breaks show up under the owner's name there, the same as Explosive and Vein Miner breaks.

Summons and mobs

Rune Guardians, Oracles and Vessel bosses are summoned on the block the player clicks, and Thralls spawn where the player is mining. BusyMining doesn't check claims for these. Use Settings.DisableCustomMobWorlds in modules/core/config.yml to keep them out of whole worlds, and your protection plugin's mob-spawning flags for smaller areas.