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).
@owenftw
Nothing is ever fully protected, and I rely on WorldGuard's Protection to do the real work.
As a note 1.5 is in testing now, and will be out before the end of the week, here are the new features included:
Region Overlap Checking (Blocks overlapping regions when placing ProtectionStones). No more players overlapping your area. You can only overlap regions you own.
ProtectionStones No Drop (one time use option) Breaking a ProtectionStone still removes your region but you won't get the ProtectionStone back. Default is the old behavior of dropping the ProtectionStone to be reused.
Group Block Limiting (you will be able to use the Global Region.LIMIT or the new Group Limits). This allows you to place a player in one of five groups, and each group has it's own configurable block limit, which also includes "0" for no blocks, and "-1" for unlimited blocks just like Region.LIMIT.
Two New Commands:
"/ps view" displays four glass blocks at the height of the players feet for thirty seconds. This will allow you to check your region's boundaries. This command is temporary until I can create a better and faster version. Use at your own risk the four blocks created are the four corners inside your region, and are destructive. So whatever blocks are in those locations are destroyed and replaced with glass blocks, after thirty seconds the glass blocks are destroyed, the original blocks are not replaced.
Also, there is no "cool down" period, so a player could fire this command over and over again causing server lag.
"/ps heal" will replace a missing ProtectionStone. For example: you allow TNT to be used on your server and someone blows up your ProtectionStone. The WorldGuard Region still exists, so just enter your region and use the command and the missing stone will be replaced.
I'm doing it this way because of the amount of server lag that could be produced by constantly checking if a stone gets broken by all the means that could destroy it.
Both the new commands have their own permissions also.
@AxelDios
Cant wait for 1.5 :) Peoples stuff will be fully protected then.
@Flydevice
At the moment I'm trying to find a good way to release all the source code.
@AxelDios
Would you mind uploading the source code?
@TeamAss
A user can put any ProtectionStones he wants inside other areas he owns. I'll think about a future version allowing parent and priority levels.
Version 1.5 will add the detection of overlapping regions and prevent you from intersecting regions you don't own.
As far as naming, you can't change the name of a ProtectionStone Region, that is how it knows that the WorldGuard Region was created with a ProtectionStone.
If you rename it then it is no longer a ProtectionStone Region, just a regular WorldGuard Region, ProtectionStones uses WorldGuard's Region Database for all it's information.
@AxelDios
Could you also make it so that u can allow smaller protection stones inside the others? Kinda like setparent in worldguard but automatic. Could be like the owner who has a 64x64 protection stone. Allow smaller 16x16 stones inside his area by typing /ps allow [name of the user] [size of the protection from that ore].
Also could you add a feature where u can track the activity of a protection stone, so that if the protection stone which is not taken from its current spot and has users frequently going in and out of it will be eligible to making a new name instead of having the coords as its name by typing /ps name [Name]. Then the user will tap the ores which he placed down to make the coords of those ores combine into one single plot and have the name. And when he wants to expand, he does the same thing, just the same name. And those that are inactive would be purged from the database in configured number of days in the config.
ProtectionStones 1.5 will be out before the end of the week if the testing phase passes.
Here's currently what is done, but not fully tested:
Region Overlap Checking (Can't overlap other owners regions)
ProtectionStones No Drop (one time use option)
ProtectionStones Group Block Limiting (with five groups)
"/ps view" command (Working on this feature at this time, more on this later)
I would still like to get an alert system and logging in place, but this can be very complicated and time consuming so I'm still in the planning stage, so it will probably have to wait for a later version.
@andrewzhang
It's not "CB 1.0.1RB" it's " CB 1.0.1-R1" and that's what all my builds have been.
World guard doesnt have a "build" which has the CB 1.0.1RB one. Will it still work?
@AxelDios
Okay MrSerios, I uploaded 1.4b with fixes for everything that was a problem, fixed the permission typo on the web site too.
Here's the information from the uploaded file:
ProtectionStones 1.4b
Blocked all commands from console:
The region commands require a player to figure out which world you are in and the other commands require you to be inside a region.
Fixed Destroy Permission Information on website:
The permission in the program was correct "protectionstones.destroy" but the website had a typo.
Fixed block placement limits: Fixed a simple coding problem where a logic statement got moved during the rebuild.
Region Count and List are both working correctly:
They are designed to report back all the WorldGuard Regions Owned by the player (both ProtectionStones and Regular WorldGuard Regions). Does not include regions that the player is a member of, only owned regions.
@MrSerios
I didn't think it would be the config, just wanted to make sure.
My code is a little convoluted at the moment because I had to rush out a large number of internal changes, I will be able to spend some time on it in a few hours and will fix it, ASAP.
And as a note, my call for counts and lists is to WorldGuard directly, and it is supposed to return owners, so I'll take a look to see what's going on.
Thank you for the reply and the info.
@MrSerios
None of the commands were ever made to run from console.
Can you paste your config.yml file here so I can see if part of the problem is a configuration file issue, particularly the block types.
@user777
The group limiting would be the first way, it would be a number of stones, not the type of stones.
And there will be five groups controlled by permissions.
@AxelDios
You mention in 1.5 the ability to group based block limiting. Does this then mean that group A could be limited to 1 coal ore, while group B could have 5?
Or group A only gets coal, while group B gets Lapis?
Thanks,
@TeamAss
I'll think about adding that to 1.5.
I've been so busy with other projects and this was a major overhaul to all the internal code to add all the requested features so I forgot to mention:
If you have an old version, rename the config.yml or delete it.
The new version has some rather large changes and it will merge the new information with the old. It will still work fine, just your old settings will make the file confusing if you need to make manual changes, and the old information will be ignored.
Can there be a feature where you can disable dropback of the ores that the user has placed to make it so that it is somewhat ULTRA Valuable and is one time usage?
1.4 is up, waiting for it to be to be approved.
Can use any block type as ProtectionStones, admins beware what you choose. Has permissions for all WorldGuard Region Flags and all can be set
New Admin "/ps region" commands.
1.5 will have group based block limiting, intersecting region detection, etc.