Here is the problem with Bukkit plugins. Each one must be written from scratch in Java using methods from Bukkit that change with certain updates. Each developer must update his(/her?) own plugin, and they usually do not unless it is a very active developer. Also, you need to be pretty good with Java to make a plugin! I'm proposing that the whole system be run by ONE plugin (well, it could be built in to Bukkit actually). That plugin would look for YML files that have scripts for plugins in a much more abstract and user-friendly manner. Bukkit would take stuff like "when a person dies, log it in this file, and spawn a chest with his inventory in it" and do the required methods. Of course, it would be something uniform and specific. Basically, you would take listener events and do things based on that. You can also have variables and such and math. The advantages of this: It's very easy, especially for simple plugins. It's faster than writing a whole Java program each time. It's uniform. It only requires one update of the master plugin to make the same plugin scripts work for new CraftBukkit versions because it can update the methods. A very simple GUI can be made for this, too! Lastly, I'd find it less boring than doing it in Java. What I'm proposing is pretty radical, but please think before you make a hate comment! Post a rational opinion on this! Agh, I wanted to add to the pole a "no for technical reasons" and a "yes for technical reasons" thing, but you can't ed it anymore. Oh well. EDIT by Moderator: merged posts, please use the edit button instead of double posting.