Bukkit

@wallofchaos

Thank you, page has been revised a lot so often typos come up.

Very little time to update.

Thanks.

@BSPiotr

Yes, more performance issue then work on my end.

As it is people would like the PS Regions to have different WorldGuard Region Names, but to keep the performance of the server I opted to use a set naming convention.

For now the only check is during block break events, then PS gets the block type by checking region size vs. your block list sizes.

Sorry I can't really make the block limiting down to a number of blocks via block types but it's now close with block groups able to limit both region counts and over all block types.

@BSPiotr

First off the LIMIT# limits the total number of ProtectionStones/WorldGuard Regions for that group, there is no limiting for the number of allowed block types for that group, the way ProtectionStones is written there is no way to add separate block type limits per block type because PS uses WorldGuard's Database and there is no means to easily and efficiently keep track of that information.

As far as block names, the first set you show in the BLOCKS# are the correct names, not the second group you show.

The last note is that a player can only be assigned to one group as per the configuration notes on the configuration page. Assigning more than one group defaults to the first group found.

ProtectionStones 1.7f - SNAPSHOT

Fixed:

There was a reported problem with the nosilktouch option on blocks in non-protected areas dropping multiple items and ore.

Fixed a someone related problem and recompiled under the newest 1.2.4 Dev Snapshot.

This problem is really related to the Bukkit breakNaturally(); function having problems with events being cancelled.

The fix will require you to update to the latest 1.2.4 Build.

This is unsupported, use at your own risk, always backup your servers!

Tested with latest dev snapshot of 1.2.4 and all seems to be working correctly.

@funk1983

I've never seen it have that problem, but between plugin interactions, lag, permissions, etc. anything is possible.

If you are able to catch this, please report, the player's permissions, like op, etc.

And what you are using for settings in PS, like blocking silk touch, types of stones, etc.

Don't forget to get info from the "/ps admin version" command.

Thanks

@funk1983

How are you running it (web front end to a remote server etc.)?, you say copy it over locally.

Please give me more information on where it works and where it doesn't work.

@zimko95

Okay, now there are 9 groups, and that's the limit unless Bukkit changes the permissions infrastructure.

ProtectionStones 1.7e - SNAPSHOT

Fixed:

"/ps flag greeting" and "/ps flag farewell" not updating correctly

Changes:

"/ps info region" command permission changed from "protectionstones.admin" to "protectionstones.region"

ProtectionStones Groups (in permissions) changed from 1..5 to 1..9.

So now you have an additional four new groups, so the last group is now "protectionstones.group9".

Additions:

New block type limiting for groups, one for each of the groups.

For Example:

Blocks:

- COAL_ORE 5

- LAPIS_ORE 10

- DIAMOND_ORE 20

Groups:

LIMIT1: 1

LIMIT2: 3

BLOCKS1: COAL_ORE

BLOCKS2: COAL_ORE DIAMOND_ORE

The blocks listed in the blocks must have a space between them if there is more than one. They must also appear in the Blocks Section of the config.yml. The Limit Number is the total PS/World Guard Regions the player in this group can own, the blocks are the only blocks that the player in this group can place.

This is unsupported, use at your own risk, always backup your servers!

@funk1983

The "/ps flag greeting" like all the flags was changed so if you put no information it would unset the flag. But as you pointed out a bug has slipped into the code making it unset even with a value. I'll fix it ASAP, and create an early release with some new group limiting additions and changes.

Thanks for the feedback.

@zimko95

No it's actually not that simple, because you need to do a check vs. each permission to see which one is set, the more you check each time every user uses a block equals more delay.

If every plugin does this you would create major lag.

If PS was the only plugin running then it wouldn't matter as much.