BlocksManager - Plugin FREE

About
BlocksManager gives you full control over how players interact with the world. Survival players can only place the blocks you allow, they can only break the blocks you allow, and nobody can place globally blacklisted materials unless they have build mode. Creative players stay free to build, except for that blacklist, so staff can still work while the rest of the server follows your rules.

The plugin is made for survival, PvP, events, spawn areas and any server that needs clean, predictable block behaviour without a heavy claims system. Drop the jar in, edit config.yml, and the whitelist, the blacklist, the drops and the regions all live in one place.

Block control
Placeable blocks decide what survival players are allowed to put down. Anything outside that list is cancelled and the player gets a configurable message. Breakable blocks do the same for mining and griefing. If a survival player placed a block, other survival players can still break it even when that type is not on the breakable list, so player-built cobwebs, planks and similar pieces stay fair to remove.

Non-placeable blocks are a global blacklist. Bedrock, command blocks, barriers and anything else you add cannot be placed by anyone, including creative players, unless that player has build mode enabled. This is the safety net for staff mistakes and for items that should never appear in the world.

Placement checks run at highest priority. If another plugin already cancelled the place event, BlocksManager leaves it cancelled. Breaking follows the same idea for protected vanilla or plugin regions, while still letting survival-placed blocks be removed by other survival players.

Build mode
Staff with permission can run /build and toggle a per-player build mode. While it is on, that player can place any block, including ones on the global blacklist, so builders can work at spawn without turning the whole survival whitelist off. Build mode is cleared when the player quits, so it never stays active by accident after a session.

Custom regions
You can define cuboid regions by world and coordinates, independent from WorldGuard. Each region can deny specific place types and specific break types even if those materials are allowed everywhere else. A spawn box can forbid cobwebs, TNT and lava buckets while still using the global survival lists in the rest of the map. Enable or disable each region from config without a restart if you reload.

Drops and inventory
Custom drops replace the vanilla loot of a block with a material and amount of your choice, for example three diamonds from diamond ore. Random drops go further: one block can roll several outcomes with chances, send the item straight to the inventory, use NULL as a chance to drop nothing, and apply MiniMessage names, gradients and lore on the item. You can mix both systems on the same break.

Direct to inventory skips ground drops and orbs. Broken items go into the player inventory and leftover stacks fall naturally if the inventory is full. Experience is given to the player instead of spawning orbs. You can apply this to every block with ALL or only to a list of materials.

Messages
Every message uses MiniMessage, including the prefix. You can use named colors, hex, bold, italic, underline, strikethrough, obfuscated text and gradients. Leave a message empty to disable it. There is a two second cooldown per player per message so denied placements cannot spam the chat.

Commands
/blocksmanager or /bm and /bm reload reload the configuration, save tracked survival-placed blocks and restore any managed temporary placements. Permission blocksmanager.admin, default OP.

/build toggles build mode for the player who runs it. Permission blocksmanager.build, default OP. Console cannot use this command.

Permissions
blocksmanager.admin is required for reload and the main command. blocksmanager.build is required to enter and leave build mode. Both default to operators. Give build mode to trusted builders without giving them the reload command if you want a split staff setup.

Installation
Put the jar in your plugins folder and start or restart the server. Open plugins/BlocksManager/config.yml and set placeable-blocks, breakable-blocks and non-placeable-blocks to the materials you want. Enable custom drops, random drops, direct-to-inventory or custom regions only when you need them. Run /bm reload after edits. No database and no extra plugin are required.

Configuration
All behaviour lives in one YAML file. Materials use Bukkit names such as OAK_PLANKS or SCULK_SHRIEKER. Regions use min and max corners. Random drop text uses MiniMessage.