In the new command engine, typing a command with no arguments, or with missing arguments, returns an "Unknown command" error message – previously it would print the syntax of the command. This message is technically wrong, as it doesn't differentiate between correct commands that are simply incomplete and those that really do not exist. This is misleading in that it doesn't point exactly what's wrong, which goes against the new engine's "philosophy".

Despite the engine displaying the next field dinamically as you type the command, in some cases it's easier to be able to look at the whole syntax at a glance and verify everything that's required for the command to work. Not only is it easier for beginners to learn the syntax this way, but such error message there looks out of place, as the command is not "wrong", just incomplete.

Pulling the correct syntax according to the typed command wouldn't be difficult, as that's already done for the /help output. These lines of text would just have to override the default "Unknown command" message when a correct command is typed partially.