ProtectionStones (Updated for 1.13.2, 1.14, 1.15 + WG7) 2.6.9

The easiest grief prevention method that players will enjoy!

  1. EspiDev
    Native Minecraft Version:
    Tested Minecraft Versions:
    • 1.13
    • 1.14
    • 1.15
    Source Code:
    AxelDios (Original), Vik1395 (2015-2016), Dragoboss (2016-2017), Jerzean (2018)
    Talk to me directly on the M.O.S.S. Discord!

    Ever needed an easy, yet powerful way to prevent grief, and protect a certain area?

    This plugin allows players to protect land using a block that they place down. It creates a WorldGuard region at a set radius (configurable) around where the block is placed. The plugin also allows players to add and remove people to the region, as well as set flags (defined in the config).

    • WorldGuard 7+
    • WorldEdit 7+
    • Vault (Optional)
    • Spigot 1.13.2+
    Appreciate my work?
    Donations are appreciated! :)


    To install ProtectionStones, make sure you have the requirements above already installed. You can simply just add the plugin to the plugins folder, and it will generate the default configuration.

    Adding new blocks:
    To add new protection blocks, go into plugins/ProtectionStones/blocks, and copy and paste the default block1.toml file and rename it (ex. block2.toml). Then, you have to change the "type" and "alias" fields in the new block config, since there cannot be duplicates.

    Configuring flags:
    Flags allow for customisation of region behaviour. ProtectionStones uses WorldGuard flags, meaning that WorldGuard is actually doing the protecting, not ProtectionStones. You can view the list of WorldGuard flags here:

    It is also possible to use other plugins that add flags to WorldGuard, such as WorldGuard Extra Flags and use them in ProtectionStones.

    The permission list is on the wiki: By default, no permissions are given to players, so you have to add them explicitly. You can also view the recommended permissions to give for commands here.

    Other Recommendations:
    WorldGuard by default prevents hoppers from going between regions. I recommend setting "ignore-hopper-item-move-events" in WorldGuard's config to false to fix this.

    If you want to protect against water and lava flow, you can set "high-frequency-flags" and "protect-against-liquid-flow" to true in WorldGuard's config.

    WorldGuard config:

    Default Config Files:




    When I add a new block config, an error occurs!
    Read the error. Most likely you made a configuration mistake, you can read the TOML spec here:, or ask me. Another known issue is that configs made in Notepad (Windows) cause issues with the plugin. Please use a better text editor (ex. Notepad++) for the time being, while I investigate ways to mitigate this.

    When I get the protection block from the creative inventory, it doesn't work (nothing happens when I place it)!
    Since v2.0.0, the config options "restrict-obtaining" is enabled by default. This restricts obtaining the protectionstones to just /ps get and /ps give (and plugins that use the API), since they attach NBT data to the block. That means that when the block is obtained through natural means, it won't work as a protection block. You can set "restrict-obtaining to false to negate this behaviour.

    How can I sell protection blocks in a shop?
    There are many ways to sell protection blocks, with the easiest being setting a price on /ps get (requires Vault, configured in the block config). You can also use external plugins to sell the protection block, either through running a command (/ps give) or giving an item that was obtained through /ps get or /ps give. Known plugins to work are: ShopChest, ChestCommands.

    Why don't players see the region merge menu?
    Be sure to give players the protectionstones.merge permission.

    Why do some flags apply to members of the region as well? (ex. block-break deny)
    By default flags apply to everyone, including members of the region. You have to use region groups (using -g) to change this (ex. set the group to apply to only nonmembers). You can read about this here:

    How do I change the block type of a region after players have already created regions with it?

    You can use the command /ps admin changeblock [world] [fromblock] [toblock] to do this. Create a new config (block.toml file) in the blocks folder with the changed block type, while keeping the old one still loaded. Do /ps reload, and run the command to do the conversion. After it completes, you can remove the block config with the old type.

    Why does [x] flag not work?

    Flags are handled by WorldGuard, and some of their behaviours may not be what you expect. You can read more about WorldGuard flags here:

    I found a bug! How do I get it fixed?
    Please file this issue on either GitHub, or post it on the discussion page.

    I want a new feature!
    Please file this issue on either GitHub, or post it on the discussion page. The feature may not be aligned with the goals of the plugin, so it might also be worth making another plugin that uses the developer API instead.

    Is there a developer API?
    Yes there is! It still is in a beta stage though right now, so methods are bound to change. You can see the WIP wiki page here:


    This plugin is based off of the original ProtectionStones.

    Migrating from older versions of ProtectionStones (<2.x.x)

    The transition from older versions should be seamless, so just drag the plugin in to the plugins folder and enjoy! The plugin will automatically update your configs and regions.

    You can find the original plugin here:

Recent Reviews

  1. ShuT
    Version: 2.6.9
    it's going great! a question how can I do so that admins also apply not to break another player's blocks?
    1. EspiDev
      Author's Response
      Thanks, please ask questions on the discussion page, GitHub, or on the Discord.
      That though is not possible unless you start revoking WorldGuard permissions
  2. PlebexerMC
    Version: 2.6.7
    The best protection plugin!, and the most active developer, he is answering fast, fixing bugs and updating the plugin constantly, and it is free!, better than all the other paid protection plugins, you are the best, EspiDev! <3
    1. EspiDev
  3. aguadelamiseria
    Version: 2.6.7
    Developer is quite active, listening to requests and reports in github. Solid plugin.
    1. EspiDev
  4. TakenNone
    Version: 2.6.6
    So far this plugin is *AMAZING*, I love how you have the option to block different things in claims such as creeper damage, and creeper block damage... like wtf, this is amazingggg!!!
    1. EspiDev
      Author's Response
      Awesome :)
  5. Banit
    Version: 2.6.6
    Response Time: Incredible.
    Took less then 5 Hours to fix a bug. So far im really happy with the Plugin it does exactly what you would expect and is ultra configurable!
    1. EspiDev
  6. Ant4rez
    Version: 2.6.4
    I really like the plugin, you can create as many blocks as you want and also use worldguard flags on the regions, i will expecting more features and fixes =).
    1. EspiDev
  7. Kejker
    Version: 2.6.4
    Great plugin, but please, create integration with Placeholder API. For amount of placed regions etc.
    1. EspiDev
      Author's Response
      Thanks, please discuss any feature requests on the discussion page or on GitHub.
  8. vinxtge
    Version: 2.6.3
    How can I change message which appears when I enter someones plot?
    Anyway, this plugin is great!
    1. EspiDev
      Author's Response
      To change the default message, go to the block config and change the "greeting, greeting-action, farewell, farewell-action" flags in the "flags section.

      Players can change the message in their region with /ps flag

      If you have any other issues, please ask on the discussion page.
  9. Lethal888
    Version: 2.6.3
    Very useful and simple plots plugin. 5 stars.
    1. EspiDev
  10. TheRawrGuy
    Version: 2.6.3
    Could you add for support 1.12.2 please? Will be great! :3
    I would like to use this plugin for my survival..
    1. EspiDev
      Author's Response
      Unfortunately, I'd have to rewrite the entire plugin because it was built for 1.13+ You can use the old version of ProtectionStones though which was before I took over maintenance of the project.