Minecraft plugin ProtectionStones

🔌 About ProtectionStones

ProtectionStones — is a Minecraft server plugin that allows players and administrators to protect/claim regions by placing configurable "protection blocks." ProtectionStones provides a simple, block-based claiming workflow for Paper/Spigot servers and integrates with common server tools.

🎯 Purpose

ProtectionStones solves the need for a lightweight, player-friendly land-claim system: when a player places a configured protection block the plugin creates a protected region around that block with configurable radius and flags. The plugin aims at preventing grief (chest access, block breaking, etc.) without requiring complex GUI flows.

⚙ Main features

• Block-based region claiming using user-configurable protection blocks. ()
• Configurable protection radius and default flags for new regions. ()
• Integration with WorldGuard and WorldEdit (required). ()
• Optional integrations: Vault, PlaceholderAPI, LuckPerms. ()
• Events/API for developers (plugin exposes protection-related events). ()

🧩 Who it's for

• Server owners who want a vanilla‑like claiming experience.
• Survival and roleplay servers seeking simple land protection.
• Admins who prefer block-based claims over GUI/command-only systems.

🏗 Usage examples

• Players place a ProtectionStones block to claim a radius‑based home area.
• Server operators set default flags (e.g., chest-access, block-break) in config so newly placed protection blocks automatically apply server policy.
• Integrate with Vault or shop plugins to sell protection stones (integration handled externally).

⌨️ Commands

Note: full command names, arguments and exact permission nodes are documented in the project's official docs and GitHub pages. ()

🔐 Permissions

If you need exact permission nodes or defaults, consult the project's documentation or the included default config/permissions file. ()

⚙ Installation

📥 Installation

• Download the plugin jar from an official source (GitHub releases or Modrinth/Spigot). ()
• Place the .jar into your server's plugins/ directory.
• Restart the server (full restart recommended).
• Verify the plugin loaded without errors in the server console.

📦 Dependencies

• WorldGuard (required). ()
• WorldEdit (required). ()
• Optional: Vault, PlaceholderAPI, LuckPerms. ()
• Supported server cores: Paper / Spigot (see releases for exact Minecraft version compatibility). ()

🧾 Configuration

• The plugin includes default configuration files in the repository and generates config on first run (config location is /plugins/ProtectionStones/). ()
• Many options are configurable: protection block types, radii, default flags, messages and visualisation settings. ()
• Database: no official indication of required external SQL databases in the fetched documentation; typical operation is file/config based. If your server setup needs DB support, check the plugin docs for any persistence options. ()

🧠 Additional information

Known conflicts & limitations

• Requires WorldGuard and WorldEdit; mismatched versions of those dependencies can cause runtime errors. ()
• Newer Minecraft server versions may require the plugin's latest releases; check release notes for Java and Minecraft compatibility (recent releases note Java 21 requirement in some builds). ()

FAQ

Q1: Which Minecraft/Paper versions does ProtectionStones support? A1: Supported versions depend on the plugin release — consult the release notes on GitHub/Modrinth for exact version compatibility. Recent releases target modern 1.20+ / 1.21+ builds. ()

Q2: Does ProtectionStones send usage statistics? A2: The project references bStats for usage statistics in its repository. ()

Q3: Is there a Discord for support? A3: The project lists a community Discord invite for support and discussion. ()

Q4: Can I sell ProtectionStones via shop plugins? A4: The plugin itself handles protection; economy/shop integration is done via Vault/third‑party shop plugins. Confirm interactions in your shop plugin's config. ()

Support & issue tracker

• The project maintains source, releases and issue tracking on GitHub. ()

When authoritative command/permission lists are required, consult the plugin documentation and the repository (links in the URLs section). ()