Bukkit

Just wanted to say kudos and thanks again, it's amazing how fast you react and fix bugs reported. You put a lot of work and effort in to this and it's greatly appreciated by all users of your plugin. Unfortunately I'm piss poor otherwise I'd make a hefty PayPal donation, for now though you will ahve to settle for my gratitude. :)

@Rocologo Can you provide support for Residence plugin ? (flags like use and container) Player should be able to lock only his own chests , door etc.

Hi, the Backpack feature and all works nice! But is it possible to set the amount of fields you can buy for the backpack? I think the space as 2 chests is a bit too much, so would it be possible to set in the config hoch much fields/rows a user can have? I hope you understand what I mean - bad english -.- :D

I'm not sure how to disable tools & bucket stacking. Removing ids from config did not help nor giving negative permission nodes

this is a cool plug great work ! Very multiurpose 5/5 stars one suggestion for ya , could we get "cost to use" with an option? ie: toggle pay player or just standard pay server. that way when a player makes a ride or something that costs to initiate he makes some cash from it and would be payed the next time the owner uses his button or whatever the cost was added to.

then your shop system would be open for players to use, not just admins and it would be very handy not just for a simple dispenser shop but also rides or access, whatever our crazy players want to charge for :)

No problem thanks you really are good on the bugs.

I know you inherited that buggy backpack which for some reason wasn't as buggy until you got it and had to integrate it, but your doing your best here to get these things done and we all appreciate that.

Was going to reply to a fixed ticket you did but a comment is better suited to this.

I'm super impressed how much stuff Rocologo has to put up this plugin and backpack by someone else with bugs, in my opinion sticking it out etc and how fast he works on stuff here has earned my respect more than I can put in words, most people wold just put it in the trash or start from scratch, it is very brilliant that Rocologo is sticking this out to see it through.

I was thinking last night more on the node thing with pex etc.

In most plugins to name big ones essentials and worldedit with 150 plus nodes in each if you do not have the node in pex bukkit will tell you you don't have access and block you from using the command.

On our server we have allot of conflicting nodes and last thing we want is to put in 1000+ negating nodes for the first rank then set the rest up like normal or even put a negate * on guest and unnegate in the same rank.

The plugins here I have to negate everything or else it is active like chest locking and auto sort on players inventories which are enabled without the node (bukitinventorytools.sortinventory.use).

So in the case above there is no point to have a access to sort permission nodes or chest lock nodes if its going to be enabled anyway even by the guest rank.

Now if essentials or worldedit and multiverse did this there would be massive uproar and the point of having a permissions system would be mute or would be the 'reverse permissions' if you were auto given permissions unless you negated the nodes.

Even when I used spoutbackpack from the other dev it worked like this and I use Lockette to only fix the chest bug in 1.8, that even doesn't do anything without the access nodes.

I guess what I ask is this plugin in permissions to be more inline with most bukkit plugins and if you don't have the permissions bukkit tells you you either cant do the command or just does nothing cause having to negate and zero all permissions first then add them back in is not how most plugins work. Not even bukkit itself with ban reload etc.

I know you might have other views but think about if essentials, worldedit or multiworld etc did this and why most plugins are written this way to block all unless have the specific access nodes and the fact you don't need to negate everything you do not use.

You give permissions nodes when needed if you don't have the node then you shouldn't have access to that feature.

Rocologo you have done marvelous things with this plugin and are always trying to improve it and you do have my respect. I just want to see this plugin get better and more inline with the way permissions normally work for most users as well as see the features in the plugin bug free.

@Rocologo

Odd, I'm SURE I made a ticket earlier for this, but now I can't find it (Then I ahvenät sleept for 2 days so might be going blind). Anyway, after wiping all data and reinstalling a fresh copy of 2.8.8 together with removing 3 permissions lines that was duplicated from my first install (before backpack was added) it now seems to work properly. Not sure if the dupe permissions was the problem or something bugged with the older database. Sorry again for wasting your time. At least this gives you two more suggestions to try for others with similar problems.