Unknown command spam in console

[bloggy]

Whenever I execute a console command (via console) I get the "unknown command" warning in the console which spams my server.

This is the script command I am executing:
http://hastebin.com/uheqifowuv.vbs

I am on spigot 1.9.4.

[bensku]

Does using /skript: work?

[bloggy]

Yes, it works and there is no console spam with /skript: before the command. But that is not a good solution. I don't want to change all my console commands to /skript:MYCOMMAND ... this wasn't necessary in the past. How can this be fixed?

[bensku]

Could it be that some other plugin has command with exactly same name? I.e. could you try if that command exists when you're running server without that script?

[TheBentoBox]

I can confirm that I've always had this issue (since long before this fork, but it persists in the fork). Running commands from console tends to work just fine, but it also sends an unknown command message, even if the command isn't registered in a different plugin. e.g. here's me running my Skripted /playtime command on a player

12.07 09:45:29 [Server] INFO Faelisa's total time online is 5 day(s) 4 hour(s) 35 minute(s) 23 second(s).
12.07 09:45:29 [Server] INFO Unknown command. Type "/help" for help.

The Unknown command shows up after the command result, even though it worked just fine.

[Pilvinen]

Yes, I can confirm, I also have this. It's been around for a very long time. Doesn't really break any functionality, just an oddity.

[Nicofisi]

This has been a known bug since the beginning of Skript, and as far as I know Njol finally said that this won't be fixed (by him).
Njol/Skript#194

Edit: The MassiveCraft team has achieved it anyway somehow: https://github.com/MassiveCraft/MassiveCore/blob/master/src/com/massivecraft/massivecore/command/MassiveCommand.java#L40-L54

You can change the command aliases of their plugins while the server is running (and what's fancy in general but wouldn't work with Skript is that all commands are unregistered and re-registered automatically every second without impact on server's performance)

But can't we just set some kind of a console filter to catch these messages and block them? It would be a bit tricky but for sure easier (less advanced) than what they do in their plugins.. just look at that repo xD

[28andrew]

I just saw this. https://www.spigotmc.org/threads/small-easy-register-command-without-plugin-yml.38036/ It uses NMS but could easily be changed to use Reflection to access NMS (for cross-version compatability)

[bloggy]

This still exists, any solutions yet? At least if we could stop the console spam^^

[bensku]

You can use logfilters to get rid of messages. And msybe I will fix this at some point, but low priority.

[28andrew]

It's not closed..

[Adrihun]

Please fix this asap.. Please?

[TheBentoBox]

Why ASAP ...? It's not really a huge issue, just a minor annoyance. There are far more important bugs to worry about than this one.

[Adrihun]

Important bugs?
Show me xd

[TheBentoBox]

#485, or #483, or #482? Those are just from the latest release alone.

[Snow-Pyon]

This can be closed once #1013 is merged. Also, for 1.9.0 users, make sure you have the latest build made for that version, such as there is a specific build where ServerCommandEvent#setCancelled is ignored, and that's what my PR uses to fix this.

By the way, it's kinda hilarious how the such easily fixeable bug been all this time without getting fixed. And actually, it was fixed on #77 but due to how Skript handled command execution, which was executing the command separatedly and then setting the actual executed command to "", the error persisted.

Oh well, I think the 5 hours I spent finding the root cause of this weren't for nothing.

[SlimeDog]

Thanks. I've been using a console filter for years to elide that message. All better now.