Minecraft plugin EssentialsAntiBuild

🔌 About the plugin EssentialsAntiBuild

EssentialsAntiBuild — is a plugin for Minecraft servers that allows server operators to block placing, breaking and using specific blocks or items using blacklist and permission‑based rules. EssentialsAntiBuild extracts and expands the anti‑build features previously bundled in EssentialsProtect and focuses on configurable block/item restrictions and alerts.

🎯 Purpose

EssentialsAntiBuild addresses griefing and unwanted block/item interactions by giving admins fine‑grained control over what players may place, break or use on a Spigot/Paper Minecraft server. It solves problems such as accidental or malicious placement of restricted blocks, misuse of interactable items, and piston‑based movement of protected blocks. EssentialsAntiBuild is suitable where server operators need per‑item permissions and global blacklists.

⚙ Main features

• Block place blacklist (server‑wide list of blocked block types). ()
• Block break blacklist. ()
• Item use blacklist (prevent use/interact of specific items). ()
• Piston block move blacklist (prevent pistons pushing certain blocks). ()
• Permission system for per‑item place/break/use/craft/drop/pickup control (e.g., essentials.build.place.). ()
• Build alert system: configurable alert lists that notify staff when certain items are placed/broken/used. ()

🧩 Who it fits

EssentialsAntiBuild fits server admins and moderators who run Spigot, Paper or Bukkit servers and need:

• per‑item permission control, blacklists and alerts;
• lightweight, module‑style protection integrated with the EssentialsX suite;
• non‑region‑based protections for global item/block restrictions. EssentialsAntiBuild is not a region manager replacement (use WorldGuard/region plugins for per‑region protections). ()

🏗 Usage examples

• Prevent all players from placing pistons or TNT globally by adding those IDs to the placement blacklist. ()
• Allow only staff to place certain decorative blocks by granting essentials.build.place. to trusted groups. ()
• Configure alerts so moderators receive notifications if a player attempts to place a restricted item. ()

⌨️ Commands

The plugin does not add new commands. EssentialsAntiBuild is configured via the Essentials/AntiBuild config and permissions rather than separate plugin commands. ()

🔐 Permissions

(Notes: the permission nodes above are documented in the AntiBuild/Essentials docs. Exact default assignments depend on your permissions plugin and server setup; official docs do not state a single default for these nodes.) ()

⚙ Installation

📥 Install

• Obtain the EssentialsX AntiBuild jar and the required EssentialsX core module.
• Place EssentialsXAntiBuild-*.jar into your server's plugins/ folder (alongside EssentialsX). ()
• Fully restart the server (do not use /reload).

📦 Dependencies

• EssentialsX (the main EssentialsX module) is required — AntiBuild is a submodule that expects EssentialsX present. ()
• Platforms: Bukkit, Spigot, Paper (plugin metadata lists these platforms). ()

🧾 Configuration

• AntiBuild uses Essentials/AntiBuild configuration sections (blacklist, alert, and permission rules). The wiki documents the blacklist: and alert: sections and gives examples for placement/usage/break/piston entries. EssentialsAntiBuild supports legacy EssProtect blacklist syntax. ()
• The plugin generates or uses the Essentials config area (check your /plugins/Essentials or /plugins/EssentialsX folders after first run). Specific config filename/location is managed by EssentialsX. ()
• Database: official sources do not indicate MySQL/SQLite support specifically for AntiBuild; configuration focuses on blacklist and permission rules. If persistent storage is required for other EssentialsX modules, consult their docs. Information on DB support for AntiBuild is not present in the referenced sources. ()

🧠 Additional information

Known conflicts & limitations

• AntiBuild is not a region plugin — for region‑specific protections use WorldGuard or similar. AntiBuild enforces global blacklists and permission checks. ()
• Some permission managers (older PEX versions) may treat '' style permissions differently; the wiki documents caveats and legacy PEX handling. Test in your environment. ()

FAQ

Q1: Does EssentialsAntiBuild add its own commands? A1: No — it is configured via Essentials/AntiBuild config and permissions. ()

Q2: Can I use AntiBuild with Paper/Spigot 1.20+? A2: EssentialsX/AntiBuild releases list support for many Minecraft versions; check the module release metadata for exact supported game versions for the release you download. Example releases document support for modern versions (see Modrinth/CurseForge metadata). ()

Q3: Where do I list blocked items? A3: Use the blacklist: section (placement, usage, break, piston) in the AntiBuild config as shown in the Essentials wiki. IDs or names may be used. ()

Q4: Does AntiBuild notify staff when a restricted item is used? A4: Yes — the build alert system can notify players with essentials.protect.alerts when configured items are triggered. ()

Telemetry / bStats

Information about bStats telemetry for the AntiBuild module is not present in the official sources referenced. Official EssentialsX project pages link to source and community resources but do not clearly state module‑specific telemetry. Information not present in official sources. ()

Support & community

EssentialsX provides a GitHub issue tracker and a community Discord referenced from module pages. For issues or contributions use the main EssentialsX project resources. ()

When to use EssentialsAntiBuild

If you need permission‑level control over specific blocks/items and a lightweight global blacklist/alert system integrated with EssentialsX, EssentialsAntiBuild is appropriate. It complements region managers rather than replacing them and is best used for global restrictions and per‑item permissions on Spigot/Paper servers. ()