Bukkit

@Pantherita

That's correct, depending on your version of Bukkit or if you use Spigot, when PS tells the block to break naturally per the Bukkit API, some servers will not take the Fortune Enchantment, this appears to be a timing issue on some servers, if you want to avoid it all together just pick different blocks for your PS's and set the Silk Touch option to false.

@YoShIWoZ

No, it can't be done, the coordinate based name is how PS finds the location of the ProtectionStone within the region.

@gv1222

PS 2.0 is slow at this time because too many people want it written in incompatible ways, so I'm going to go ahead and build in the way I want it per usual.

PS 1.9 will see one more copy soon, just to update to UUID's instead of waiting for 2.0 as the plan was set.

PS 2.0 will still use WorldGuard, so existing protection will be in place, and there will be an option for using either the old style blocks, or using new blocks that will work similarly to how my SuperSmelters work, with names, etc.

@hutt132

I see from the error you are using Spigot and PS 1.9i, if that version of Spigot is forcing the use of UUID's then that could be the cause of the error. PS doesn't yet use UUID.

@Squawkers13

No it's not updated to UUID's yet.

@Ivanelias13

Some of my plugins do allow for custom recipes (i.e BoomStick, RubySlippers, etc.). BlastFurnace will probably never have a fully custom build "recipe" but I am testing different options with it, SuperSmelter has always been slated to allow for custom recipes and soon will, and ProtectionStones supports up to 16 different PS Blocks and can use almost all of the Minecraft Block Materials.

As a note PS 2.0 will allow for not only "special" PS Blocks, but will allow for custom recipes to make the blocks, with permission levels to allow or deny crafting each type and for each player group. The blocks will look like basic blocks but have names and lore information much like the SuperSmelters.

@treestompz

It is open source through an MIT License, I'll PM you a link to a temporary repository.

Get ready now for the upcoming player account update that will let players change their account names...

NameDeny can protect your server, even if none of your plugins are updated to handle the new account system. Install it now to start recording your players current player names with their UUID's.

@ViscousSummer88

You should read the Configuration Page (and the other pages before posting here).

Your server either has a very large amount of regions, is over-loaded or very slow disk write speeds.

PS uses WorldGuard for all it's protection, and until they add a save by region to their API PS is forced to save all regions for the current world on placement.

But there is an option to change this behavior, this is from the Configuration Page:

Region.SAVETIMER: WorldGuard Regions for all worlds are saved on server restart or if the plugins are /reload(ed), but this setting allows for more flexibility.

-1 = Save after all PS region changes (which is the default setting and how older versions of PS work).

0 = Don't save PS region changes, which would only get saved on the restart or reload.

n = A number meaning how many minutes to wait until the next PS region save. This number is in minutes. Don't set it to low or you will cause large amounts of server lag, If you use this setting the first save happens five minutes after the server starts, and then once each time your time limit is reached.