Console command output is emitted to the logger

[dktapps]

Issue description

This is a problem which also exists on the vanilla PC server. When the console writes a command, the output is recorded to the log instead of being emitted directly to the console. This is annoying for multiple reasons:

• Useless messages get written to the server.log like output from help.
• Plugins like my own ClientConsole will relay command output from the CLI to players because it can't tell the difference between a log message and a command output.

Ideally, the CLI and the log output should be emitted to two independent windows, a bit like RCON. However, this is challenging to implement in a manner which is cross-platform.

For what it's worth, the MCPE vanilla server doesn't emit command output to the log.

Steps to reproduce the issue

1. Write a command in the console like help.
2. Notice that the output lands in your log file for no good reason.

Problems with changing this

PocketMine-MP has historically attempted to mimic PC vanilla, particularly with respect to command output. This is because some PC server tools like Multicrap rely on the specifics of the logger output. However, I don't believe we should allow this problem to stand in the way of improving PocketMine-MP.

[Frago9876543210]

What about continuous logging? For example, when you enter a command and several players write to the chat at the same time, the command moves several lines.

[dktapps]

That nut is difficult to crack. This also comes from the problem that CLI and logger are on the same page when they shouldn't be.

[dktapps]

I tried to implement this and ran into a few issues:

• Broadcasted messages are received by the ConsoleCommandSender. This is a problem because broadcasted messages should land in the log file too.
• Command output audit messages are problematic for the same reason.

It would seem logical that an extension to this would be to separate the command-output part of CommandSender from the rest of it.