@MilkBowl

It's quite a big feature, which you probably won't have time to do, I'm not 100% as to whether it's possible, but it would be good if people could use Vault to help with command compatibility, I'll show you a (trimmed) bit of code which is what I mean: (the code is for a plugin using Vault, not Vault itself)

package blah.blah.blah;

import net.milkbowl.compatibility.Compatibility;

public class Blah;

Compatibility compat = Compatibility.getPluginManager();

compat.addCommands(Commands, this);

And basically, Vault would check with the plugin manager if the commands are already registered, and if they are, not register them. It would be great for plugins with a lot of commands, such as Essentials.

you can already check this in your own plugin through the bukkit API can't you? If so, why would I need to add the API for it in Vault? if Not, how would Vualt be able to check it?

Good point that. I think you can, but it would be a lot easier if it was possible to do through Vault, cause so many developers probably can't be bothered to do it via the Bukkit API. At least, especially developers working on plugins with a lot of commands.

I'm still not sure what you're asking for.

No, my bad, I should have closed this, I just meant that it would be good if you could use Vault to check whether a command is already registered, and not register it if so, but as you say, it's possible anyway, and I suppose it's not that hard.