ProtectionStones
Anti-Griefing at it's Easiest!

Griefing Protection
ProtectionStones allows a player to place a special block, and this protects their area from griefing.
This small plugin was inspired by PreciousStones but only has the property protection blocks. This allows players to place one of three types of ore blocks to protect their property.
The player doesn't require any special permissions, they just need to get one of the three following ore blocks which you can give or sell in game using other plugins:
Coal Ore gives 11x11x11 protection area.
Lapis Ore gives 21x21x21 protection area.
Diamond Ore gives 41x41x41 protection area.
See the Configuration Page if you would like to change the block types, the dimensions or even set the Y-Axis to be from sky to bedrock, set group limiting, etc.
When the player places the block it creates a WorldGuard Region that gives the player ownership of that area and in turn grief protection. If the player breaks the ProtectionStone then they get the stone back and the region is removed from WorldGuard's Region List.
To install simply copy the ProtectionStones.jar file to your plugins folder, no configuration necessary. The following Ore Blocks are supported as the defaults: Coal Ore, Lapis Ore, Diamond Ore.
ProtectionStones Regions
ProtectionStones Creates WorldGuard Regions with the following naming convention:
ps{x-coordinate}x{y-coordinate}y{z-coordinate}z
i.e.
ps279x67y40z
The x, y, and z coordinates are the location of the placed ProtectionStone which is in the center of the WorldGuard Region it creates. If the Region.SKYBEDROCK Setting is set to "true" (see the Configuration Page) then Y-Axis of the ProtectionStone isn't necessarily the vertical center of the region.
Incompatible with PreciousStones
Both plugins act on the same kind of ore blocks and have the same command name of "/ps".
Requires WorldGuard
WorldGuard is used to create and remove regions when the blocks are placed, otherwise ProtectionStones won't do anything (set not to load if WorldGuard isn't found).

-
View User Profile
-
Send Message
Posted Jan 1, 2013Im having a problem where, users can place a protection stone, but if they remove it and place it again, it counts as 2 stones in their limit. If that doesnt make sense, lets say someone has a limit of 20 protection stones. They placed their 20th stone and wanted to move it. They got rid of it, and placed it again but it said he reached his limit. Also, when they do the ps count command it only shows that he used 15 stones, when his limit is 20. Any idea whats causing this?
-
View User Profile
-
Send Message
Posted Dec 30, 2012@joshwenke
Thanks. Will update it an give it a test.
-
View User Profile
-
Send Message
Posted Dec 30, 2012I was wondering if you could add a feature (configurable) that makes it so if you place a protection stone in faction land it will not work? I think this would be a great addition to an otherwise amazing plugin.
-
View User Profile
-
Send Message
Posted Dec 29, 2012@Relicum
Works fully on a 1.4.6 production server!
-
View User Profile
-
Send Message
Posted Dec 27, 2012Has anybody tested this on 1.4.6 ?? Thanks
-
View User Profile
-
Send Message
Posted Dec 26, 2012Can you add compability to custom flags from WGCustomFlags?
-
View User Profile
-
Send Message
Posted Dec 26, 2012Is it possible to give users a /ps home command?
-
View User Profile
-
Send Message
Posted Dec 26, 2012@dropposite
Not possible if a user can have more then 1 plot :D
-
View User Profile
-
Send Message
Posted Dec 26, 2012will we be able to change that default zone name to something more friendly like "plot_$username" ?
-
View User Profile
-
Send Message
Posted Dec 26, 2012would this work with tekkit ?
-
View User Profile
-
Send Message
Posted Dec 25, 2012Worldexlusion (which should be changed to worldinclusion) doesnt work... Either
,
or
does not disable the plugin on those worlds... Please change the Exclusion.WORLDS to be a yml valid list and no space seperated array, this is causin eye cancer to me!
How do i disallow building outside of protections? (Because they should still be able to place the protectionstones)
-
View User Profile
-
Send Message
Posted Dec 23, 2012@gv1222
I replied to your PM and it's a know exploit against WorldGuard that has been around since the beginning of PS and is easily blocked as I mention about 1 every few months.
PS uses WorldGuard for all is't protection, and to keep PS fast and lite, it doesn't have it's own database.
So there is no means to constantly protect the PS's since this is the role of WorldGuard.
You can set PS's to autohide and block players from unhiding them to prevent this exploit against WG, you can also use other plugins to block Piston Attacks on WorldGuard Regions, and one day WG will probably add this feature.
-
View User Profile
-
Send Message
Posted Dec 23, 2012@AxelDios
AxelDios, I have PM'd you a major protection stone duplication bug. I would usually submit a ticket but would rather keep this from the public. Thanks, gv1222
-
View User Profile
-
Send Message
Posted Dec 21, 2012You should enable protection against pistons... Users can plop or move any PS stone to get a "free" field.
-
View User Profile
-
Send Message
Posted Dec 20, 2012@norge4everxx98
See the Exclusion.WORLDS List and the Exclusion.PLACEMENT Options at the bottom of the Configuration Page to exclude worlds or change the way ProtectionStones Work on excluded worlds.
-
View User Profile
-
Send Message
Posted Dec 20, 2012@sayoui
By default the unhide command is set to allow anyone to use it, this is so people not running a permissions plugin, or not wanting to configure the plugin can run it without changing anything.
If you open the protectionstones.jar file in an archive program like 7zip, you can edit the plugin.yml.
Simply find the the "protectionstones.unhide" permission in the plugin.yml and either change the default to false or op.
Here's what it looks like before you change it:
protectionstones.unhide:
description: Allows Use of the Unhide Command
default: true
Also many permissions plugins like PermissionsEX allow you to set a mode that by passes the permission defaults in the plugins plugin.yml file, you would need to determine that by checking your permissions plugin.
Please see the Permissions Page for more information.
-
View User Profile
-
Send Message
Posted Dec 18, 2012Hey!
Im sorry if this has been talked about! And my english is wery bad!
Can i remove the ProtectionStones from a world? Like you can do whit the Faction plugin? Like if you have 2 worlds, and i use MultiWorld, so i want to have the ProtectionStones in 1 world and factions in the other..
I dont want to lose the ProtectionStones from my server becuse i love it! But all the players want Factions and protectionstones, or just factions..
Pliss answere fast!
-
View User Profile
-
Send Message
Posted Dec 17, 2012how to disable the unhide command?
Thank you very much
-
View User Profile
-
Send Message
Posted Dec 17, 2012@sayoui
What you are showing is a known piston exploit against WorldGuard, since PS uses WorldGuard for all it's protection anything that works against WorldGuard will work against PS.
You have the option of disabling the unhide command, and also using other PS Features like autohide (with unhide), autohide with single use, etc. to stop such exploits, there are even other plugins that block piston exploits.
PS is written to be as fast and efficient as possible, so it doesn't have it's own database and also doesn't monitor all the possible exploits that could be done to a region or the PS itself.
-
View User Profile
-
Send Message
Posted Dec 17, 2012@dropposite
I'll answer them with your question numbers...
1. The limit is for all WorldGuard Regions the player has ProtectionStones and Regular WorldGuard Regions.
2. There is no way to change the default naming, to make PS faster it uses WG's Database, so to keep track of the stones it needs the coordinates stored in the name. (As a note if you change the name of a PS Region via WG's Region Command then it will no longer function as a PS Region).
3. The max number of PS's are by world, and world's can be excluded, please read the Configuration Page for more information.