First of all, congratulations to the Bukkit crew with their 1000th build. I am glad to have used Bukkit and also wrote plugins for as well. However, I am a bit flustered and frustrated over the recent inclusion of Permissions as an API within Bukkit. I am posting this so others can understand my view point. I'm not interested in an argument. Here are the main reasons: Groups Option Nodes Persistence Groups Using groups is incredibly useful as we check (for LocalShops) if a user is within a list of groups to restrict access to a shop. The groups are configured in game by a command issued by the players. My problem is in the line that groups provide an amazingly flexible avenue for heirarchy, bundling, and convenience. Considering a node as a replacement just simply doesn't provide enough. For example, let us assume we have a group named "admin", what node should I check of the following? "admin", "group.admin", the possibilities are endless and groups become meaningless between plugins as devs define them differently. More importantly, a node doesn't provide ability to group permissions together. Option Nodes Option nodes provide the ability to store a parameter (String, Integer, Boolean, etc) along with a node. This allows the ability to provide additional customization of plugins. So why is this such a disappointment? Imagine being able to set limits on the number of times someone can use a command or how often someone can chat or the number of chests someone can protect. With option nodes we can simply define a key and obtain a value. Many plugin developers know and understand the value that Maps give us these days, this is literally what Option Nodes provide us. Imagine the insanity of checking all permissions on "myplugin.mynode.100" through "myplugin.mynode.0" or whatever your values are instead of simply providing a map. Option Nodes can provide limitations and work exceptionally well as a permission based system (while some plugins do not use it this way, some do). Persistence I am personally baffled that Permissions are not persistent in Bukkit. Why would they simply not be persistent? What value does it bring to require an additional plugin thats sole purpose is to provide persistence? Seems that instead of downloading Permission plugins we will not see the cluster of "Permission Persistence" plugins and that completely defeats any plausible points of integrating Permissions into Bukkit. Overall I can understand if built in Permissions provides a simpler avenue for some plugin developers and I personally am glad for such a system. However it lacks features that ALL permission plugins have in common these days and more importantly, it does not simplify the use of Bukkit for server operators. I believe it only adds yet another system to code for instead of replacing the need for Permission plugins altogether. These are just my thoughts and I'm sure others also have their own. Again, I'm not interested in arguments and simply wanted to share my opinions.