Bukkit

@Eddy_3b1

It does sound like a permissions issue.

If you want post your permission settings I might be able to help you, or another PS user might already be using the same permission setup as you and they will see what you are doing and how to fix it.

Sounds like you are blocking Silk Touch Outside of PS, PS has it's own Silk Touch Blocking, see the Region.NOSILKTOUCH Option on the Configuration Page. If you have silk touch disabled in the PS Configuration, it should only block Silk Touch use on blocks in your PS Blocks List.

Check out some of my new plugins like PropertyGuard.

I'm relaxing at AuthentiCity (acmc.game.nfoservers.com) between plugin updates and creation.

ProtectionStones 1.8b has been uploaded and is awaiting approval.

Changed Command:

"/ps info region" has been updated, and no longer directly calls the WorldGuard Region Info Command

New Command:

"/ps reclaim" which allows players to remove a ProtectionStone just like breaking it.

The player is still required to have the "protectionstones.destroy" permission and this command only works when you have the "Region.AUTOHIDE" Option set to true. If the "Region.NODROP" Option is set to true, the player only removes the WorldGuard Region, they don't get back their ProtectionStone.

@zimko95

No, sorry I have no solution for allowing ProtectionStones to be placed if you are globally blocking players from building. ProtectionStones relies on WorldGuard for protection and to know where players are allowed to build.

@tschagg

I knew this sounded like a familiar request, some where along the way (I'm trying to find it in the change logs but can't) I was asked to make the stones have the option of covering sizes above 50 (50 = 101x101x101). Well I made the changes already and forgot to change the configuration page. I looked at the code and any hard limit has been removed, so in theory you could go quite large. I just tested it with size 120 (120 = 241x241x241).

So the current version already works for sizes larger than 50.

As a reminder:

The size number is the distance from the placement of the ProtectionStone (usually the center of the cube) to the outside edge.

There are a few changes in Bukkit 1.2.5 R3.0 that will now cause errors with some of the PS Commands, so I'm working on those changes now, and a few updates. for the release of 1.8b.

@tschagg

The limit I set was for the size of the cube, and was set to 50 for speed reasons for some of the commands, at 50 you get a 101x101x101 area (unless you set the sky to bedrock option which would be 101x101x255) which is a big area.

I'll think about making the size larger for the next update, possibly a size of 100, which would give you 201x201x201.

The size number is the distance from the placement of the ProtectionStone (usually the center of the cube) to the outside edge.

PS 1.8b Should be released late next week.

It will include some new commands to give even more options to protect against piston exploits.

Also included will be a list of regions when an overlap is detected, instead of just the message about a region overlap.

And it will be compiled with the new Bukkit 1.2.5 - R3.0

@treestompz

Not without some information.

Run "/ps admin version" and tell me the version information it returns to start off with.

@Armani76

You can allow your admins to unhide PS's and if people need to change them they could unhide them for your players.

I would have to add a lot of overhead or completely rewrite PS to do it's own protection separate from WorldGuard to protect against this exploit.

Nothing is fool proof. There are some third-party plugins that protect WG from piston attacks, and maybe WG will add the ability to block those attacks in the future.

@Armani76

WorldGuard doesn't protect from that attack so there is only one thing you can do to protect against those exploits, and that is to hide the ProtectionStones.

In the config.yml set the auto.hide to true.

This is from the configuration page:

Region.AUTOHIDE: Automatically hides ProtectionStones after placement, defaults to false.

To keep players from unhiding stones you would also need to block the "/ps unhide" command for regular players by changing the following permission to false:

protectionstones.unhide