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 Mar 24, 2013Update please...
-
View User Profile
-
Send Message
Posted Mar 24, 2013re: updating Be patient, it will happen eventually. Better to get it right than rushed and have server problems.
-
View User Profile
-
Send Message
Posted Mar 24, 2013plz update to 1.5.1 I have been using precious stones and it sucks
-
View User Profile
-
Send Message
Posted Mar 24, 2013@DekuHero
AxelDios 1 day, 12 hours ago - 0 likes Like @apersonnamedcaleb
It will be updated next week and also include the new piston blocking feature.
-
View User Profile
-
Send Message
Posted Mar 24, 2013please update. I really don't want to have to switch to precious stones.
that plugin is not as good.
-
View User Profile
-
Send Message
Posted Mar 23, 2013Hello we all need to solve 1.5 problems, can you give us your font code please?
-
View User Profile
-
Send Message
Posted Mar 23, 2013Problem with 1.5 version:
2013-03-23 16:50:22 [WARNING] [Server] The main thread failed to respond after 10 seconds 2013-03-23 16:50:22 [WARNING] [Server] Probable Plugin cause: 'ProtectionStones' 2013-03-23 16:50:22 [WARNING] [Server] What follows is the stack trace of the main thread 2013-03-23 16:50:22 [WARNING] [Server] at java.util.regex.Pattern$CharProperty.match(Pattern.java:3694) 2013-03-23 16:50:22 [WARNING] [Server] at java.util.regex.Pattern$Branch.match(Pattern.java:4502) 2013-03-23 16:50:22 [WARNING] [Server] at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556) 2013-03-23 16:50:22 [WARNING] [Server] at java.util.regex.Pattern$Ques.match(Pattern.java:4079) 2013-03-23 16:50:22 [WARNING] [Server] at java.util.regex.Pattern$Branch.match(Pattern.java:4502) 2013-03-23 16:50:22 [WARNING] [Server] at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556) 2013-03-23 16:50:22 [WARNING] [Server] at java.util.regex.Pattern$Begin.match(Pattern.java:3472) 2013-03-23 16:50:22 [WARNING] [Server] at java.util.regex.Matcher.match(Matcher.java:1221) 2013-03-23 16:50:22 [WARNING] [Server] at java.util.regex.Matcher.matches(Matcher.java:559) 2013-03-23 16:50:22 [WARNING] [Server] at org.yaml.snakeyaml.resolver.Resolver.resolve(Resolver.java:130) 2013-03-23 16:50:22 [WARNING] [Server] at org.yaml.snakeyaml.serializer.Serializer.serializeNode(Serializer.java:174) 2013-03-23 16:50:22 [WARNING] [Server] at org.yaml.snakeyaml.serializer.Serializer.serializeNode(Serializer.java:207) 2013-03-23 16:50:22 [WARNING] [Server] at org.yaml.snakeyaml.serializer.Serializer.serializeNode(Serializer.java:207) 2013-03-23 16:50:22 [WARNING] [Server] at org.yaml.snakeyaml.serializer.Serializer.serializeNode(Serializer.java:207) 2013-03-23 16:50:22 [WARNING] [Server] at org.yaml.snakeyaml.serializer.Serializer.serializeNode(Serializer.java:207) 2013-03-23 16:50:22 [WARNING] [Server] at org.yaml.snakeyaml.serializer.Serializer.serialize(Serializer.java:112) 2013-03-23 16:50:22 [WARNING] [Server] at org.yaml.snakeyaml.Yaml.dumpAll(Yaml.java:271) 2013-03-23 16:50:22 [WARNING] [Server] at org.yaml.snakeyaml.Yaml.dumpAll(Yaml.java:261) 2013-03-23 16:50:22 [WARNING] [Server] at org.yaml.snakeyaml.Yaml.dump(Yaml.java:248) 2013-03-23 16:50:22 [WARNING] [Server] at com.sk89q.util.yaml.YAMLProcessor.save(YAMLProcessor.java:188) 2013-03-23 16:50:22 [WARNING] [Server] at com.sk89q.worldguard.protection.databases.YAMLDatabase.save(YAMLDatabase.java:260) 2013-03-23 16:50:22 [WARNING] [Server] at com.sk89q.worldguard.protection.databases.AbstractProtectionDatabase.save(AbstractProtectionDatabase.java:43) 2013-03-23 16:50:22 [WARNING] [Server] at com.sk89q.worldguard.protection.managers.RegionManager.save(RegionManager.java:69) 2013-03-23 16:50:22 [WARNING] [Server] at com.axeldios.ProtectionStones.ProtectionStonesBlockListener.onBlockPlace(ProtectionStonesBlockListener.java:251) 2013-03-23 16:50:22 [WARNING] [Server] at sun.reflect.GeneratedMethodAccessor250.invoke(Unknown Source) 2013-03-23 16:50:22 [WARNING] [Server] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 2013-03-23 16:50:22 [WARNING] [Server] at java.lang.reflect.Method.invoke(Method.java:601) 2013-03-23 16:50:22 [WARNING] [Server] at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:425) 2013-03-23 16:50:22 [WARNING] [Server] at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62) 2013-03-23 16:50:22 [WARNING] [Server] at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:477) 2013-03-23 16:50:22 [WARNING] [Server] at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:462) 2013-03-23 16:50:22 [WARNING] [Server] at org.bukkit.craftbukkit.v1_5_R1.event.CraftEventFactory.callBlockPlaceEvent(CraftEventFactory.java:100) 2013-03-23 16:50:22 [WARNING] [Server] at net.minecraft.server.v1_5_R1.ItemBlock.processBlockPlace(ItemBlock.java:85) 2013-03-23 16:50:22 [WARNING] [Server] at net.minecraft.server.v1_5_R1.ItemBlock.interactWith(ItemBlock.java:71) 2013-03-23 16:50:22 [WARNING] [Server] at net.minecraft.server.v1_5_R1.ItemStack.placeItem(ItemStack.java:77) 2013-03-23 16:50:22 [WARNING] [Server] at net.minecraft.server.v1_5_R1.PlayerInteractManager.interact(PlayerInteractManager.java:392) 2013-03-23 16:50:22 [WARNING] [Server] at net.minecraft.server.v1_5_R1.PlayerConnection.a(PlayerConnection.java:635) 2013-03-23 16:50:22 [WARNING] [Server] at net.minecraft.server.v1_5_R1.Packet15Place.handle(SourceFile:58) 2013-03-23 16:50:22 [WARNING] [Server] at net.minecraft.server.v1_5_R1.NetworkManager.b(NetworkManager.java:292) 2013-03-23 16:50:22 [WARNING] [Server] at net.minecraft.server.v1_5_R1.PlayerConnection.d(PlayerConnection.java:113) 2013-03-23 16:50:22 [WARNING] [Server] at net.minecraft.server.v1_5_R1.ServerConnection.b(SourceFile:35) 2013-03-23 16:50:22 [WARNING] [Server] at net.minecraft.server.v1_5_R1.DedicatedServerConnection.b(SourceFile:30) 2013-03-23 16:50:22 [WARNING] [Server] at net.minecraft.server.v1_5_R1.MinecraftServer.r(MinecraftServer.java:580) 2013-03-23 16:50:22 [WARNING] [Server] at net.minecraft.server.v1_5_R1.DedicatedServer.r(DedicatedServer.java:225) 2013-03-23 16:50:22 [WARNING] [Server] at net.minecraft.server.v1_5_R1.MinecraftServer.q(MinecraftServer.java:476) 2013-03-23 16:50:22 [WARNING] [Server] at net.minecraft.server.v1_5_R1.MinecraftServer.run(MinecraftServer.java:409) 2013-03-23 16:50:22 [WARNING] [Server] at net.minecraft.server.v1_5_R1.ThreadServerApplication.run(SourceFile:573) 2013-03-23 16:50:23 [SEVERE] Connection reset 2013-03-23 16:50:37 [WARNING] [Server] The main thread is still stuck, current loop line is: 2013-03-23 16:50:37 [WARNING] [Server] at com.sk89q.worldguard.protection.databases.AbstractProtectionDatabase.save(AbstractProtectionDatabase.java:43) 2013-03-23 16:50:37 [WARNING] [Server] This appears to be plugin 'ProtectionStones'!
-
View User Profile
-
Send Message
Posted Mar 22, 2013@apersonnamedcaleb
It will be updated next week and also include the new piston blocking feature.
-
View User Profile
-
Send Message
Posted Mar 22, 2013Please update to 1.5
-
View User Profile
-
Send Message
Posted Mar 20, 2013Piston Protection
With the next version of ProtectionStones will be a new configuration option:
Region.BLOCKPISTONS which is defaulted to false.
If you set it to true, all blocks moved by pistons are checked to see if any of the blocks are in the ProtectionStones Blocks List (meaning a material that could be used as a PS), and if they are the piston won't move.
You will still have the option of auto-hiding ProtectionStones on placement and blocking players from using the "/ps unhide" command.
Both permissions for the hide and unhide commands (protectionstones.hide and protectionstones.unhide) will also now be defaulted to "op", to make it easier for server admins.
-
View User Profile
-
Send Message
Posted Mar 19, 2013@smed2696
As soon as the stable release version of CraftBukkit is out I'll update.
-
View User Profile
-
Send Message
Posted Mar 19, 2013Please update to 1.5 :) there is no issues but an update would be nice. Keep up the good work with my favourite plugin :)
-
View User Profile
-
Send Message
Posted Mar 18, 2013@DekuHero
I'm currently running it on a couple of server's running the 1.5 CraftBukkit Dev Build and it's working fine with both older and the newest dev builds of WorldEdit and WorldGuard.
-
View User Profile
-
Send Message
Posted Mar 17, 2013@Mre30
Not sure what you are trying to do, please explain it so I can see if I can help you.
As a note, by default the permission for addowner, which is "protectionstones.owners" is set to op, so only operators can use it.
When a player places a PS they are automatically set as the owner of that region.
-
View User Profile
-
Send Message
Posted Mar 17, 2013@DekuHero
You're right... Great plugin because it is so easy to use
-
View User Profile
-
Send Message
Posted Mar 16, 2013I prefer this over precious stones because it is more lightweight, efficient, and less confusing to players and admins.
Will you need to update this to work with the new world guard or no?
-
View User Profile
-
Send Message
Posted Mar 15, 2013i take it back.
This is a nightmare. addowner dosnt work. Even after they addowner, they still cant build. Since each block placed is one claim, and the fact that they overlap, makes it a complete nightmare for admins. I cant spent 9 hours a day telling people to type /ps addowner in every single block they placed.
Great idea though.... amazingly compact and VERY easy for players to claim.
-
View User Profile
-
Send Message
Posted Mar 11, 2013I INSTEAD protection of all this in diamondblock and emerald block as do??
-
View User Profile
-
Send Message
Posted Mar 10, 2013@AttestedFaun
From the Commands Page:
To add a member to your ProtectionStones Region: /ps add [player]
The owner must use that command while standing in the region.
If you want them to be another owner of the region do this command:
To add an owner to your ProtectionStones Region: /ps addowner [player]
See the Commands Page and the Permissions Page for more information.
-
View User Profile
-
Send Message
Posted Mar 10, 2013@winduprabbit123
There's a toggle to allow people to place or not place a region and there's World Blocking, at this time I'm not going to a creative check.