Command "/extinguish" is already bound to plugin "Essentials".

[mathwhiz1212]

In my understanding WorldEdit should only be binding to //extinguish and not /extinguish and there should be no conflict. I get this error every time I start my server:

Warn [16:48:20] Stack trace:
Warn [16:48:20]   [C](-1): BindCommand
Warn [16:48:20]   Plugins/InfoReg.lua(139): RegisterSubcommands
Warn [16:48:20]   Plugins/InfoReg.lua(162): RegisterPluginInfoCommands
Warn [16:48:20]   Plugins/WorldEdit/main.lua(58): (no name)
Warn [16:48:20] Stack trace end
Warn [16:48:20] Command "/extinguish" is already bound to plugin "Essentials".
Warn [16:48:20] Stack trace:
Warn [16:48:20]   [C](-1): BindCommand
Warn [16:48:20]   Plugins/InfoReg.lua(139): RegisterSubcommands
Warn [16:48:20]   Plugins/InfoReg.lua(162): RegisterPluginInfoCommands
Warn [16:48:20]   Plugins/WorldEdit/main.lua(58): (no name)
Warn [16:48:20] Stack trace end

[NiLSPACE]

I believe that instead of making WorldEdit only bind to //extinguish we should add an option to Cuberite where admins can tell the server who they want to handle a command.

I'm also planning on adding a configuration option to make WorldEdit only bind // commands, but that will come later as I'm kinda busy.

[mathwhiz1212]

@NiLSPACE It's no big deal for me at least. Thanks for responding!

[HelenaKitty]

I do believe something should be done to fix this, however take your time with it, it's nothing major.

[NiLSPACE]

I don't think WorldEdit should be the one to take care of this. Personally I think the server should notice that two plugins try to bind the same command and that there should be a specific configuration file where an admin can tell the server which plugin he prefers to bind the command to.

[HelenaKitty]

You should also be able to disable commands you don't want, or need.

[NiLSPACE]

But I don't think it's the job of the plugin to provide the option to disable one of it's commands. The server should manage this.

[HelenaKitty]

Yeah, that actually makes more sense!