The bug
Before 17w45a if you typed a command incompletely it send you the syntax, now it just says "unknown command at position X:" (for example /setblock)
It's a better error message for when you end an argument set early
"Incomplete (expected......) at position X:" (for example /setblock ~)
Linked issues
is duplicated by 5
MC-121995
If you don't provide any syntax, no syntax error will occur
Resolved
MC-124451
Typing an incomplete command returns "Unknown command" instead of syntax help
Resolved
MC-133409
Command feedback says "Unkown command" when parameters are incomplete
Resolved
MC-145634
/playsound doesn't work
Resolved
MC-145969
Unknow command.
Resolved
relates to 2
Attachments
Comments 9
It's a part of MC-128449.
Confirmed in 32a and many other versions.
You'd better add a tag "brigadier" to this issue.