Nothing sums it up better than this: "It's not that PEX handles wildcards better, it's that bPermissions doesn't handle wildcards at all. The only time the wildcard node will work in bPermissions is if that plugin is still using Permissions 2.X bPermissions has group inheritance in 2.0." So it's come down to this, bPermissions must do exactly the same as PEX in order to keep people happy. Superperms was a nice idea, but no-one is totally happy with how it works and it could be improved upon, but won't be. If I want bPermissions to handle permissions how I think they should be handled, it requires me to override the default system in place, which, while possible easily a definite hassle and requires supporting extra things for it to work with systems such as Spout. The only thing bPermissions does different than PEX now is to have different files per-world (which some people see as a bad thing anyway). I'm considering hanging up my bPermissions shoes, thanks superperms! What I'm looking for is feedback from bPermissions users, suggestions from devs, anything really. NOTE: I probably won't hang up my bPermissions shoes, so don't worry about that, I'm just annoyed that I keep banging my head against this same wall over and over again. Also @t3hk0d3 you were doing it right all along, keep things up YOUR way. EDIT: Update on my situation, I will no longer be writing for Superperms. People should write for the Vault API and no other.