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).
Not passing my testing phase... so 1.4 is still not released.
There are some problems with my region flags.
Okay, 1.4 will be out soon (in about six hours max if all goes well), sorry for the delays.
Total rewrite of the blocks used for ProtectionStones and the flags used in each region.
I've added lots of changes and additions that were requested.
It's currently in the final stages of testing, and as soon as I feel it appears stable I will post it.
So please bear with me.
Thanks for all the comments, suggestions, and support!
@Artemu
Sorry about not understanding question #4 I read it quickly and I keep getting asked to add a sell feature.
WorldEdit's Selections could show the area quickly but I don't want to use the Undo feature to remove it again, too intensive on the server, just like drawing the bounding boxes with blocks.
I haven't looked at PreciousStones Code but the way it draws the bounding areas is very slow and intensive on the server so for now I don't do it at all.
And #3 1.4 will allow you to set permissions on a flag by flag basis what you want people to set.
@Artemu
I do believe the per-flag permissions will be used in 1.4, The other stones protection system had something like what you want for showing the protected area, but it was VERY buggy and lag inducing for the client, also glass blocks can be mined with silk touch now.
Hi thanks 1 & 2 is cool however I think there has been a misunderstanding
3. I don't want people to access every flag, only PVP and Mob-Spawning. So as an example I would like to give them access to node protectionstones.flags.pvp and protectionstones.flags.mobspawning
4./rg sel is not a sell, it is a select command, which sends a information to World Edit CUI, and shows you the demarcation of your region. However most normal users don't have this, so a solution was to edit the chunk before it was sent to the client (thus not editing the actual world) to include a glass block at each corner of the region. If that is too complex, even just placing a glass block in the actual map, as it can't be harvested back
@Artemu
1. At the moment due to potential speed problems people will still be able to overlap areas, I'm working on different solutions to that problem.
2. Version 1.4 has the ability to select any block as a ProtectionStone, admins beware what you select.
3. Version 1.4 allows any valid WorldGuard Flag to be used and each has its own permissions.
4. Selling will most likely never be included in this plugin, as mentioned below, you can always sell it in game by removing your ProtectionStone and letting the new owner place theirs.
Hi,
This plugin is epic! There are however some suggestions I have.
1. Config Setting to check that when Ore is placed, that it is not being placed into a region that is owned by someone else. Users can place ore, and override someone else's region atm.
2. Allow ore's to be changed, for example I would like to replace diamond with redstone. So have them as variables rather than fixed values.
3. Nodes for each flag & wildcard flag if you want all. For example I only want players to be able to disable mob-spawning and pvp
4. Comand to /rg sel or another possibility is when a user does a select command that the plugin sends a modified chunk, that includes glass markers
Otherwise, this is honestly an awesome plugin!
Love the plugin the way it is :D very helpfull
@alexdude99
I'm sorry to say I won't be adding any support for selling regions, you can already sell the stones in game for example using shops or Essentials [BUY} Signs, etc.
Or you can use plugins like Simple Region Market to sell your region.
Adding support for "extras" has already tripled the size of version 1.4 compared to 1.0 and it's still not done.
Ive got one suggestion for maybe 1.5. I would be grateful if you added in support for iConomy so we could make the users pay to claim a place. Also please could you make it so if they place for example a redstone torch it charges them a certain configurable amount of money. Thanks!
@NolanSyKinsley
Here's How ProtectionStones Works with Owners and Permissions...
When you place a ProtectionStone you create a WorldGuard Region with you as the owner, ProtectionStones allows players with the protectionstones.members permission to view their members, and also add and remove them. The only way without using WorldGuard's /region command to change the owner would be for the player to break the block and let another player place a block there. This is buy design.
They can also set their own flags if they have the protectionstones.flags permission (1.4 will allow any valid WorldGuard Region Flag).
The ProtectionStones config.yml lets you set the default flags used to create a new region. For now there won't be a per flag permission, just a set or not set type permission, but I'll think about the permission per flag you are asking about.
Thanks for the compliments and using ProtectionStones!
My compliments to the chef! You have been one of the most responsive and active maintainers that I have seen!
On a side note, 1 suggestion and 1 question. The suggestion is for per flag permissions. The question is, does PS set all added players as owners or members? We currently have permissions set up to allow worldguard region owners to add/remove members, seeing as how this uses worldguard I would hope that it only adds members.
@DiAmOnDaGgEr
I thought 1.4 would be out in the next few hours but it will have to be put off for at least 24 hours and as late as the beginning of next week..
Currently repairing a couple of downed servers for a friend.
Between reloads and copies I'm going back and forth finishing up 1.4.
You will be able to use any block type you want, there are lots of blocks I would never use but that would be up the you to pick which ones.
As far as flags I use WorldGuard Regions as my back-end database and region protection, so I can only add the flags that WorldGuard Regions support, like USE, ENTRY, CHEST_ACCESS, etc.
WorldGuard has a PDF you can download/print with all the flags on it.
@AxelDios
thats great mate, yes thats the thing we were hoping to circumvent, i was wondering about whether or not blocks gained with silk touch would be useable but that was answered earlier and thats why I was wondering if it could be changeable :) its great stuff we are all looking forward to the release, just one other thing, where you mention "Finishing the rewrite of the flag parsing/creation system, which will give me the flexibility to add any and all flags." does this mean you will be able to control things individually ? like chests, doors, switches ? instead of chest-access locking eveything that counts as a container including furnaces, and use locking everything you toggle like doors buttons and switches ?
@DiAmOnDaGgEr
At this moment I'm trying to push out 1.4 and one of the extras I was going to see if I can get into this build was a rewrite of the Materials to give people flexibility in block type they can use, as a gap stop measure I might just allow the addition of Iron, Redstone, and Gold Ores as I've talked about before, but I'm aiming for any block you would like, this opens a large hole in the plugins use, if you pick a readily available block, players could exploit this and really mess up your map.
Hi, loving the plugin its marvelous, just wondering about the ores, the admin on our server tried adding other ores so we could have more sizes available like adding redstone and gold etc. but he wasnt able to, a little help would be greatly appreciated if its possible to add more :) not sure if this has been touched on, didnt see any other comments with this.
Edit: well i have in my eyes you posted that your adding this already so i guess we'll wait patiently :) keep up the good work :)
@XeonG8
Thank you for using it!
I am looking into creating limits by "group", more info will be on the page in about 12 hours about how the new "global" limit works.
Version 1.4 will be out sometime within the next 12 hours, won't be able to work on it for about six more hours, but after that 1.4 will definitely have the following features:
More flags (aiming for all flags, and better flag parsing and creating (more on this later)
New /ps region command for region counts, lists, remove, etc.
New block placement limiting to control the number of regions a player can create.
What I'm working on later tonight my time:
Fine tuning the region commands, and adding a "regen" command that will remove the ProtectionStones (WorldGuard) Region like the "remove" command but also regenerate the map via the seed for that region only.
Finishing the rewrite of the flag parsing/creation system, which will give me the flexibility to add any and all flags.
Reworking how the block types are loaded to allow for any block type you would like to use as ProtectionStones, it will be up to users if they cause unforeseen problems due to conflicts, etc.
Then after all this I have to copy my updates here to the web site :)
I'm working folks, any and all feed back is appreciated!
This plugin is awesome! The only thing that keep me from using it is the per block type permission!
I would love to see this because i don't want normal player to get a city wide protection but some others i want them to...
Is this something you are implementing soon?
@AxelDios
OK another thing is I edited the config to this:
Material: SPONGE: 17
And on server start got this:
Material: SPONGE: 17 COAL_ORE: 5 LAPIS_ORE: 10 DIAMOND_ORE: 20
the Sponge block still didn't work :D .. I really don't want to use OREs due to Silk touch enchant, and how easy they can blend into the ground even with xray, making removing them by hand added hassle... also potential region greifing lol. As you said you're still working on more admin commands to better deal with managing this stuff. Will there be something to just remove a region+block(s) while standing in someones region for OPs to use?
@XeonG8
Version 1.4 will have block limiting (by region count), and several admin commands, one will allow you to list all the regions a player owns, and allow you to also remove all of their regions and also I may add the ability to remove their region by selecting and cutting it and then regenerating the map in the region from the original map seed.
I thought of using a naming convention like you mention (except written as ps{x}x{y}y{z}z_{playername}) but the name is already pretty long, so instead my plan has been to get the owner names from WorldGuard's Region Database.
This would be faster, more efficient and also make the region naming less complicated.
I've dropped my other plugins for a moment to work on 1.4's early release.
Though I need to get on Minecraft and play on some of my favorite servers for a bit!
Don't forget the ProtectionStones Region naming is the middle of the region (except if you use Region.SKYBEDROCK, then the vertical position can be anywhere). So if you break a stone simply check your current position then check WorldGuard for that region name.