Feature to unregister all commands that conflict

[soshimee]

Description

It would be nice to have something to unregister all the commands that conflict, or even unregister a specific command. I think this will be a good addition because CommandAPI commands tend to have lower priority and the other plugins which aren't as important (such as Essentials and WorldEdit) tend to overwrite them. It's definitely very annoying to type minecraft: every time this happens.

Expected code

No response

Extra details

I was making a plugin with /info and then WorldEdit decided to take priority. It wasn't a good experience.

[JorelAli]

For converted commands (e.g. using the CommandAPI plugin command converter for Essentials/WorldEdit), the CommandAPI still has to be able to access the underlying command in order to run it. If we unregister the underlying command, then the CommandAPI won't be able to run it!

For everything else, this seems like a very nuclear option. What would be ideal is to try and get namespaces working, so the commands are registered via your plugin namespace instead of minecraft:, and command resolving comes down to however Bukkit decides to handle that

[soshimee]

Mmmm yeah I would love to see it not in just generic minecraft: namespace.