Minecraft plugin EssentialsProtect

🔌 About the plugin EssentialsProtect

EssentialsProtect — is an EssentialsX module (a protection submodule) for Minecraft servers that allows fine‑grained control over simple world protections: disabling or customizing creeper/TNT/block damage, fire spread, PvP, specific mob spawning and many damage types. EssentialsProtect is configured via the Essentials config and intended to be used as part of an EssentialsX setup on Spigot/Paper servers.

🎯 Purpose

EssentialsProtect addresses common server needs to prevent world griefing and to customize world physics without installing a full land‑claims system. It helps server owners reduce accidental or malicious block damage (creepers/TNT/fire), control whether players can PvP, restrict specific mob spawns, and toggle damage types globally per world. ()

⚙ Main features

• Toggle creeper/TNT block damage and limit explosion behaviour. ()
• Disable or enable fire spread. ()
• Global PvP enable/disable with permission bypass. ()
• Prevent spawning of specific mob types (creepers, skeletons, zombies, etc.) via config lists. ()
• Disable specific damage types (fall, drowning, suffocation, lava, fire, projectiles, TNT, lightning, etc.). ()
• Per‑world configuration inside the Essentials config (protect section). ()

🧩 Who it's for

• Server administrators who already use EssentialsX and need light protection without a full region/claims plugin.
• Survival, SMP and small‑to‑medium communities that want to tune griefing behaviour.
• Admins who want per‑world, config‑driven toggles for damage and spawn rules.

🏗 Usage examples

• Disable creeper block damage but keep creeper player damage off or on depending on permissions.
• Turn off fire spread to protect wooden builds while keeping natural fires for aesthetics turned off.
• Prevent hostile mob spawns in hub worlds while allowing them in survival worlds.
• Globally disable fall damage on a minigame world.

⌨️ Commands

The module does not add new plugin commands; configuration and reloads are handled via Essentials (e.g. /essentials reload). ()

🔐 Permissions

(Above permission nodes and descriptions are documented in Essentials/EssentialsX resources and community guides; defaults were not explicitly stated in those sources.) ()

⚙ Installation

📥 Installing

• Download EssentialsX (and the EssentialsProtect module if distributed separately) from an official source. ()
• Place the .jar(s) in the server plugins/ folder.
• Fully restart the server (do not use /reload).
• Edit the protect: section inside plugins/Essentials/config.yml to tune protections and then run /essentials reload or restart. ()

📦 Dependencies

• EssentialsProtect is provided as part of the EssentialsX suite and requires the Essentials/EssentialsX core plugin to function. No other runtime dependencies are required by EssentialsProtect itself (check the specific build notes for your distribution). ()

🧾 Configuration

• The module uses the protect: section inside plugins/Essentials/config.yml. The config exposes toggles for creeper‑explosion, fire‑spread, disable.{fall,pvp,drown,...}, and spawn prevention lists per world. ()
• EssentialsProtect will generate or use the existing Essentials config folder on first run. ()
• MySQL/SQLite support: information about database usage for EssentialsProtect specifically is not present in the official Protect docs; general EssentialsX may support data storage for other modules. Information about database support for EssentialsProtect is not present in the official sources.

🧠 Additional information

• Known conflicts: official docs do not list explicit conflicts, but community reports note overlapping responsibilities with region/claim plugins (WorldGuard, GriefPrevention), so test interaction in staging. ()
• Limitations: EssentialsProtect is intended for light, config‑driven fixes; it does not provide GUI claim tools or advanced region protections (use a dedicated region/claim plugin for that). ()

❓ FAQ

Q: Can I disable creeper block damage but keep PvP on?
A: Yes — creeper/TNT block damage and PvP are separate toggles in the protect: section; PvP can also be bypassed per‑player with essentials.protect.pvp. ()

Q: Does EssentialsProtect add commands to manage protections?
A: No — protections are configured in the Essentials config; you control them via config edits and /essentials reload. ()

Q: Will EssentialsProtect conflict with WorldGuard?
A: It can overlap in functionality; WorldGuard provides region‑level flags while EssentialsProtect is global/per‑world. Use both with care and test precedence. Community threads discuss overlapping behavior. ()

Q: Does EssentialsProtect collect metrics (bStats)?
A: Information about metrics (bStats) for EssentialsProtect specifically is not present in the official Protect docs. Information absent in official sources.

Q: Is there Discord support or an official issue tracker?
A: Official EssentialsX project resources and community pages host links for support; specific Discord/issue links for EssentialsProtect should be retrieved from the main EssentialsX project pages. Do not assume addresses — check the EssentialsX project pages. ()

🤝 When to use EssentialsProtect

Use EssentialsProtect when you need quick, config‑driven protection toggles for a Minecraft server that already runs EssentialsX. It’s suitable for administrators who want to reduce griefing or tweak world physics without adding a full claims system. ()