Bukkit

@TylerS1066

Yes, with hundreds of thousands of downloads of my plugins and my custom plugins that aren't on Bukkit I might not get to everyone right away.

First of all you are using 1.9e, try the current version which is 1.9i.

You can also not use the no Silk Touch Option and change your ProtectionsStones to other block types, please read the Configuration Page.

@JackzMc

Do you have the permission to use the unhide command, it was changed about 5 releases back to "op" as the default.

This is from the Permissions Page:

"protectionstones.unhide" for ProtectionStones Unhide Command (default set to op, changed from true).

@fisherman77

Either use the "Region.NOSILKTOUCH" option, see the Configuration Page for more information.

Or change the ProtectionStones to a different Material, also on the Configuration Page.

@DarthRiddle

If they are inheriting perms from other groups, you would need to get rid of the perm for the PS Group you don't want and add the new one.

For example if you are using PermissionsEX it has a "-" sign to remove a perm, here's a short example:

  guest:
    default: true
    prefix: '&f[&bGUEST&f] &b'
    permissions:
    - commandbook.rules
    - commandbook.motd
    - commandbook.time.check
    - -bukkit.command.version
    - -bukkit.command.plugins
    - bukkit.broadcast.user
    - -protectionstones.*
    options:
      rank: '1000'
  nomad:
    prefix: '&7[&2Nomad&7] &a'
    inheritance:
    - guest
    permissions:
    - commandbook.whereami
    - commandbook.whereami.compass
    - commandbook.msg
    - commandbook.spawn
    - protectionstones.create
    - protectionstones.destroy
    - protectionstones.members
    - protectionstones.view
    - protectionstones.flags
    - protectionstones.flag.greeting
    - protectionstones.flag.farewell
    - protectionstones.group1
    - realmail.user.sendmail
    options:
      rank: '800'
  serf:
    prefix: '&7[&2Serf&7] &a'
    inheritance:
    - nomad
    permissions:
    - -protectionstones.group1
    - protectionstones.group2
    options:
      rank: '750'

If you look at the line that says "- -protectionstones.group1", that line removed the inherited group1 perm, and the one after it "- protectionstones.group2" gives the Serf Rank the group2 perm.

Each rank or player can only be in one PS Group, you can have multiple players and ranks in the same group, but only one each.

PM me if you need more help.

Uploaded an update to PS, and awaiting it's approval from the DevBukkit Team:

ProtectionStones 1.9i

Added a new option in the config.yml:

In the Region Section you will now see "PRIORITYOVERRIDE: false"

If you change this to true and reload your plugins or restart the server you will allow players to place protected "sub-regions" within other regions. The parent region would need to have it's priority set to -1 for this to be allowed.

For example, a player called "townowner" would create a large PS protected region, then set other sub regions up to protect restricted areas in their town, for example, their home. Then "townowner" would use the "/ps priority -1" command to set the large "town" region's priority to the correct number to allow players to claim regions there.

Then "homeowner" would go to the town and place their PS to create their "plot" in the town.

@PippaSmith

It uses WorldGuard for protection, so you will need to install WorldGuard (and WG requires WorldEdit).

A few releases back I changed the timing of ProtectionStones placement, so on worlds with Towny (also Residence) and if it's a town blocking a player from building, then they would also be blocked from placing a PS.

Otherwise they should have no problems together, and it shouldn't effect Towny.

@Bow_Boss

Please don't post here and PM me at the same time, I've answered your PM.

@Rindersteak

At this time you can't, PS requires the player have the ability to "build" when they place the PS. I'm working on different ways for a future version to allow this, more than likely based on a WorldGuard Region Priority level.

@ImJasonH

I've used it on Tekkit, as long as you have a copy of WorldGuard (and WorldGuard requires WorldEdit) that works for your version of Tekkit you should have no problems.

@DaMaN8987 It will work fine if you use a version of WorldGuard that supports 1.7.9.