The command autocompletion tries too much to be helpful and overrides going back and forth in the chat history.
Example: command key
, give @p stone
, Enter
, command key
, up arrow
Expected: Getting a stone, then having chat open with "/give @p stone" in the text box.
Actual result: Getting a stone, then having chat open with "/" and a suggested "xp" in it.
This prevents quickly going back a few entries in the last executed commands list.
Linked issues
is cloned by 1
is duplicated by 6
Comments 8
For now, hitting esc will allow you to use the up and down arrow keys again until another snag is hit. Might be useful to use until this issue gets fixed
Not sure if it's back or if it has always been a different case of the bug, but target selectors used within /scoreboard commands have this bug in pre2 !
Forgot to add that afterwards (I noticed that in pre4 I think) but, still within the /scoreboard command, the bug can also affect the name of the objectives.
For instance, I had the objectives "Hits", "hitsdealt" and "hitstaken". And that must have been with this command that I noticed that :
/scoreboard players set @a 0 Hits
→ (not 100% sure I put the arguments in the right place and all, but it should be good) And it would stop me when looking back in the messages' history, because of the fact I had TWO other objectives (I'm not sure only one would work, but I actually did not try) starting the same way than the one used in that command.
What did you fix exactly, for 1.13-pre6 ? Because both cases of the bug I talked about still are there (so still affects that last release).
In case it's needed to make things clearer :
/scoreboard objectives add Points dummy
/scoreboard objectives add pointsAlt dummy
/scoreboard players reset @a
/scoreboard players reset @a Points
Now press the "Up Arrow" key. The last command displays.
Press the arrow again. It doesn't work. Because "Points" is the first part of "pointsAlt", the game wants to suggest it and hence blocks history navigation.
Press "Escape" key to be able to navigate again.
Press the "Up Arrow" key twice. Now it's the command ending with a target selector that blocks you.
Also in 17w50a.
This is really annoying.
It's possible to select from the commands/arguments list with the mouse, so it doesn't need up/down key navigation.
Whereas losing command history navigation is a real pain.