Bukkit

@edan87

You're are not giving me enough information to know what's wrong.

First of all, did you change the Region.Limit to -2 to tell PS that you are using group limits?

And in your permissions plugin did you assign each player group to just one PS Group?

@user_716797

config.yml files use the yml encoding, which can easily be corrupted with a simple typo in the file.

As far as the equal sign goes, you are correct the word "set" and the "=" sign are not used. This is just the explanation of setting the config.yml.

If you look at the config.yml files, Bukkit doesn't use equal signs, and also the "region.limit" in the file would look like this:

Region:
  SKYBEDROCK: false
  NODROP: false
  NOSILKTOUCH: false
  LIMIT: 1

With the "Limit" statement in with all the other "Region" Configurations.

@maddyn99

No sorry there isn't a way to do either, and I probably won't be the default flags feature for different stones.

But in the past I mentioned I might create a means for players to update their members and flags for all their PS's that are already placed with one command.

@deforum

Some permissions plugins like PEX allow you to override all defaults. But overriding can create unforeseen problems. You would be better off to manually set the PS Defaults to whatever you need, like defaulting to false.

I've posted how to do this many times and I will be adding it to the Permissions Pages...

To do this to any permission in PS do the following:

Open the protectionstones.jar with an archive program like 7zip, then edit the plugin.yml file inside the jar.

Find the permission section you want to change like the one controlling all flags commands...

protectionstones.flags:

description: Allows Use of Flags Commands

default: true

And change the "default: true" to "default: false"

Don't forget to reload your plugins so it will take effect.

As an additional note, if you go this route you will need to do this each time you update PS to a new version.

@user_716797

This has been answered and even has a section on the Configuration Page which walks you through the steps.

As far as making a video or explaining more, I would need to cover all the permissions plugins and all the ways you can misconfigure them.

The reason in the past I've asked people for their permissions file, what permission plugin they are using and for the PS config.yml is simple, it's easier for me to find the mistake and tell them what it is then to try to explain every possible scenario out there.

As a note there is no "region.limit" permission.

What results are you getting with group2, how many can they place if any, because it sounds like a permissions issue, like they are set to more than one group.

@zippenmarble2

Sounds like PS isn't running, first check your running plugins with the /pl command.

Also make sure you have WorldGuard installed (and WG needs WorldEdit).

@QuantumReZz

Sorry I won't switch it to glowstone, because I'm rendering the blocks in game, so they can be exploited with a silk touch pickaxe, I already have people complaining about the use (which is a big waste of silk touch) of silk touch to mine the glass blocks.

@zx636ninja

You can't, to make PS small and lite, it doesn't have it's own database, it uses WorldGuard's Region Database, so PS has no way to tell which direction you are placing the blocks in relation to the database coordinates, so it uses cube shapes only.

As a note you can use a cube that is sky to bedrock, see the Configuration Page for more information.

@excalios

You just have to copy the ProtectionStones.jar file to your plugins folder, start or restart your server.

As a note WorldGuard requires WorldEdit.

@ToxicAirEvent

Let me answer this in two parts, but first as a note If you look on the Permissions Page all the permission you need are there, like to stop all flag changes you can not give a player the "protectionstones.flags" which will block viewing and changing all flags. Also you can limit any individual flag.

Part One: Some permissions plugins allow for permission removal by using a minus sign or other options, or even to turn off all plugins default permissions. Use the latter with care, for it will often create more issues than you may expect.

Part Two:

PS was created with the most common permission defaults preset. To make PS easy to configure or to use it without a permissions plugin. All the PS Permissions are listed on the Permissions Page with their defaults of either, true (allowed), false (denied), or op (operator allowed).

To change these defaults you would either need to allow a false or op permission in your permissions plugin by adding that permission to the players group or the player directly for unique situations.

But for permissions that are set as true (allowed) many people may find it easier or the only way to deny a player would be to alter PS's defaults directly in the plugin.

To do this to any permission in PS do the following:

Open the protectionstones.jar with an archive program like 7zip, then edit the plugin.yml file inside the jar.

Find the permission section you want to change like the one controlling all flags commands...

protectionstones.flags:

description: Allows Use of Flags Commands

default: true

And change the "default: true" to "default: false"

Don't forget to reload your plugins so it will take effect.

As an additional note, if you go this route you will need to do this each time you update PS to a new version.