When trying to run an invalid command, the printout of the command in the resulting error message does not contain a slash (/
) character before the command name.
This was not the case in 1.18.2.
To reproduce
Try to run a command that doesn't exist: /invalid
Expected behaviour
Unknown or incomplete command, see below for error
/invalid<--[HERE]
Observed behaviour
Unknown or incomplete command, see below for error
invalid<--[HERE]
Screenshots
Screenshots provided by Avoma
1.18.2 (Correct behaviour)
[media]1.19 (Incorrect behaviour)
[media]Attachments
Comments 3
I can confirm this. I've attached two screenshots that show the difference in behavior between 1.18.2 and 1.19 Release Candidate 2.
[media][media]
Relates to MC-251890