05-18-2015, 04:26 AM
Let's say you are using info.lua to setup your permission system.
When you have the permission for a subcommand, you can only use that subcommand. Fairly reasonable.
Although, I think that if you have permission to the command then you should be granted access to all sub commands.
Why?
It's conveniant so I can do something like plugin.* as a permission to grant all permissions. This is useful for ranks to be assigned full use of plugins without adding each one one by one. This was very tedious for me when I used bukkit when plugins didn't include it. It's also a much easier solution than doing permission checking in each handler function.
When you have the permission for a subcommand, you can only use that subcommand. Fairly reasonable.
Although, I think that if you have permission to the command then you should be granted access to all sub commands.
Why?
It's conveniant so I can do something like plugin.* as a permission to grant all permissions. This is useful for ranks to be assigned full use of plugins without adding each one one by one. This was very tedious for me when I used bukkit when plugins didn't include it. It's also a much easier solution than doing permission checking in each handler function.