Bukkit and the plugins are great and all people concerned (developers, bukkit team, people helping in the forums) are doing a great job. But bukkit is on a rocky road and the usuability for the admin and user isn't at the point where it should be. This thread is ONE part of several threads, please do me the favour and read them all and only reply in here with information which help this thread become productive. Thanks.. Bukkit has the following issues: Permissions... different plugins, different concepts, complicated, error prone and shattered Help.. complicated, not to the point, not really translatable / customizable. Aliases.. Complicated and plugin specific Forums.. Difficult to navigate and missing structures Plugins.. Plugin Standards allow for to many issues A lot of problems for admins and users come from commands which are complicated, not self explenatory or duplicate. There is already a basic approach to register two commands like /tp and /dctp or /dc tp for the same command, but that can still generate issues when you have 2 plugins which use the same command, sometimes even for different things. Some plugins like DefaultCommands from Vildaberper use a quite good approach to make all commands alias able. I would like to see the alias function as an API in bukkit and make it a requirement to support it by approved plugins. The alias api should support: registering of plugin command and alias from pluginalias.yml conflict handling if command is already registered (either automatic (first come first served), semiautomatic (aliasorder.yml which contains hirachy of plugins, higher plugins will have the command),manual (error message in log and chat or via option dialog in chat) Using a pluginalias.yml file in the plugindirectory would allow for full translation to other languages than english. What do you think?