-
Bug
-
Resolution: Unresolved
-
None
-
1.19 Release Candidate 2, 1.19, 22w24a, 1.19.1 Pre-release 2, 1.19.1 Release Candidate 2, 1.19.1, 1.19.2, 22w42a, 22w43a, 22w44a, 22w45a, 22w46a, 1.19.3, 23w03a, 23w05a, 1.19.4 Pre-release 3, 1.19.4, 23w14a, 1.20.1, 23w33a, 23w35a, 1.20.3 Release Candidate 1, 1.20.4, 24w09a, 24w10a, 24w11a, 24w12a, 24w13a, 24w14a, 1.20.5 Pre-Release 1, 1.20.5 Pre-Release 3, 1.20.5 Pre-Release 4, 1.20.5 Release Candidate 3, 1.20.5, 24w18a, 24w21b, 1.21
-
None
-
Confirmed
-
Commands
-
Low
-
Platform
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)
1.19 (Incorrect behaviour)
