Revise how we handle permissions.

[dumptruckman]

Not so much change the permission nodes, just make handling them a bit saner.

The current way we are handling them is very likely causing permission issues for many users. However, many users are also able to use them successfully so this is not going to be fixed in 2.5. If you're having any kind of permission issues then just know that they will be probably be fixed after we release 2.5-AB.

[ammaraskar]

btw permissions for command should be set up in plugin.yml like so

commands:
  awesomecommand:
    usage: blarg
    permission: permission.node

This allows craftbukkit to display the command only if you have the permission in /help and only tab completes it if you have the permission

[hades200082]

The Gamemode bypass permission issue is a real PITA for my builders. It only seems to be an issue when travelling to a "non-primary" world. i.e. any world that is not specified in server.properties file.

I use GroupManager if that helps.

[fernferret]

This allows craftbukkit to display the command only if you have the permission in /help and only tab completes it if you have the permission

Can't do this for all, dynamic permission allocation (world perms) :( unless it will read the permission structure that is injected at runtime, but I doubt it. That seems like a rabbit hole I wouldn't go down.

[ammaraskar]

Actually, it will if you are adding those permissions with parenting and such and registering them internally to bukkit, it will work.