Assistance with annoying command message(1.13.2)

[Randomizable]

Anyone know how to remove it from saying this when you run a command? It seems to just log the command you are running into the chat and its really annoying. If you know an easy fix, as I have never seen this before, please let me know down below.

 

[Marchi]

Anyone know how to remove it from saying this when you run a command? It seems to just log the command you are running into the chat and its really annoying. If you know an easy fix, as I have never seen this before, please let me know down below.

Fix what? send us a screen shoot

 

[Randomizable]

Fix what? send us a screen shoot

I did there's an Imgur.

 

[Marchi]

I did there's an Imgur.

Oh, i think that's because you are using 1.13 version.

 

[Randomizable]

Oh, i think that's because you are using 1.13 version.

So there is no actual fix to this its just 1.13?

 

[Marchi]

So there is no actual fix to this its just 1.13?

I don't think so.

 

[onlyspitfire]

That has nothing todo with the version. It's a problem with the plugin, command isn't registered in the plugin.yml or command isn't imported properly.

 

[Zyger]

Whoever coded that plugin must be making it return false or whatever when it's executed.

 

[Zyger]

Wouldn't matter what it returns, it's just not properly registered as said above.

Nah it does matter, you should check the spigot wiki.[DOUBLEPOST=1554279655][/DOUBLEPOST]Randomizable change the return from "false" to "true" at the end of the commands code.

 

[Norska]

Your command isn't properly registered, it doesn't matter the slightest whether you have false or true at the end of onCommand. The above suggestions that true or false plays any role are completely false.

Make sure you register your command in onEnable like this:

getCommand("yourcommand").setExecutor(new YourCommandClass());

 

[Spoch]

Quote from JavaDocs:

Executes the given command, returning its success.
If false is returned, then the "usage" plugin.yml entry for this command (if defined) will be sent to the player.

 

[Zyger]

Your command isn't properly registered, it doesn't matter the slightest whether you have false or true at the end of onCommand. The above suggestions that true or false plays any role are completely false.

Make sure you register your command in onEnable like this:

getCommand("yourcommand").setExecutor(new YourCommandClass());

 

[Norska]

Quote from JavaDocs:

"if defined", it's not required in any way. Commands will still work whether you have it set to true or false, he just didn't register it.

Either way, the thread starter never mentioned that his plugin.yml contains "usage" so changing true from false wouldn't do anything either. Usage isn't the only way or requisite to display that debug message.

 

[Spoch]

"if defined", it's not required in any way. Commands will still work whether you have it set to true or false, he just didn't register it.

They work, but it will send the usage defined in the plugin.yml.

 

[Zyger]

"if defined", it's not required in any way. Commands will still work whether you have it set to true or false, he just didn't register it.

Either way, the thread starter never mentioned that his plugin.yml contains "usage" so changing true from false wouldn't do anything either. Usage isn't the only way or requisite to display that debug message.

If it's not registered, it'd say that it's an unknown command.

(thought you were talking about it being registered in the plugin.yml, dw)

 

[Norska]

They work, but it will send the usage defined in the plugin.yml.

I'm not saying that it won't work, Zyger just assumed that it was usage while it also may not be that. Not registering your commands properly can also lead to that debug message showing.

 

[Randomizable]

"if defined", it's not required in any way. Commands will still work whether you have it set to true or false, he just didn't register it.

Either way, the thread starter never mentioned that his plugin.yml contains "usage" so changing true from false wouldn't do anything either. Usage isn't the only way or requisite to display that debug message.

It is registered properly