what's with all the permissionsex hate.

i read this linked in the vanishnopacket forum
http://goo.gl/MHhbl

i'm not a permissionsex fanboi i would really like to know what's up with this.
here's my personal experience.

load bpermissions.jar without editing anything.
essentials
esentials spawn
herochat
multiverse
vanishnopacket
worldedit
worldguard

set myself as op.
log in
get my console spammed with bpermissions errors cant use a single command due to errors spamming so hard that it eventually crashes bukkit so i don't even know if op works.

2. load permissionsex without editing anything
superpermsbridge-1.2
vault essentials
essentials spawn
herochat
multiverse
vanishnopacket
worldedit
worldguard
set myself as op log in, 0 errors can use every command

are other admins really having that many problems with permissionsex that people are railing against it?

 

I've never heard anyone hate on it.

Personally, I use GroupManager. I used to use PermissionsBukkit, and it worked great, but it didn't have a prefix feature.

 

PEX used to not support Bukkit Perms and send it's issues to other plugin developers when it wasn't their issue at all since they were supporting proper Bukkit Perms compliance.

Heroes doesn't support PEX because it doesn't natively handle Bukkit Permissions the right way. We've had several occurrences in the past where users were on PEX and couldnt use Heroes properly - when they switched to bPerms, it fixed their issue. (This may not be the case now but was 100% the case in the past)

I've never had issues with bPerms in this respect.

When these issues were brought to the devs attention he still assumed that his plugin wasn't the one broken.

 

What Kainzo said. Pretty much every permissions problem report for ScrollingMenuSign was coming from PEX users (this was a few months ago - I had to basically rework my permission node hierarchy because PEX couldn't handle certain permission node inheritance, when bPermissions/PermissionsBukkit/GroupManager didn't have a problem). And I believe PEX still breaks the Bukkit.broadcast() method due to some highly dubious injection. mbaxter can possibly expand on that one...

I guess server admins love PEX since the config syntax is like the old Permissions 3. Plugin developers tend to be... less fond of PEX

 

desht is correct. I wrote up a simple demo plugin that shows PEX's breaking of the broadcast method.

With PEX:


Without PEX:

 

well then i must be doing something horribly wrong, because when i try to run bperms with empty groups files the server just dies. and my console spams so much that i can't log in.
but when running pex with empty files i can log in i just can't do anything.

is there really such an absolutely massive difference between how these plugins work that would cause this?

 

You should paste the errors in a new thread so someone can help.

 

all of the errors are playerjoin events or playermove events.
my question is should bperms be working with with empty default generated files?
or is this an issue with the update not liking the playerjoin and playermove events?

i would post the server logs, but i don't think i can upload zips.

 

In a word: Yes.

You'd probably be better served by asking for help from the bPerms authors at http://dev.bukkit.org/server-mods/bpermissions/ - there's some information on how to get support there. (Actually I think you've already found the forums there )

 

mbaxter has a very detailed complaint about PermissionsEX.
You can find it here: https://docs.google.com/document/d/1BIgAU7senSG1hY0BjQAQFAnbuOqFhpln7ffN6pkOp4s/edit

 

He linked to that:3