Command autocomplete overrides command history navigation
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 duplicated by6
Created Issue:
Command autocomplete overrides command history navigation
The command autocompletion tries too much to be helpful and overrides going back and forth in the chat history.
Example: chat key, Hi!, Enter, chat key, /give @s stone, Enter, chat key, up arrow, up arrow
Expected: Saying "Hi!", then getting a stone, then having chat open with "Hi!" in the text box.
Actual result: Saying "Hi!", then getting a stone, then having chat open with "/give @s stone" and a suggested "{" in it. Pressing up arrow more often doesn't change anything.
This prevents quickly going back a few entries in the last executed commands list.
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
The command autocompletion tries too much to be helpful and overrides going back and forth in the chat history.
Example: c
hatkey, Hi!,Enter,chat key, /give @s stone, Enter, chatkey, up arrow, up arrowExpected:
Saying "Hi!", then getting a stone, then having chat open with "Hi!" in the text box.Actual result: Saying "Hi!", then getting a stone, then having chat open with "/give @s stone" and a suggested "{" in it. Pressing up arrow more often doesn't change anything.
This prevents quickly going back a few entries in the last executed commands list.
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.
is cloned by
Affects 1.13-pre4
Affects 1.13-pre5
relates to
Resolving in favor of the more descriptive MC-122596 ![]()
Thank you for your report!
However, this issue is a Duplicate of MC-122596.
If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Can confirm for pressing tab after already entering at least one letter of the name. Otherwise it appears on the left end of the chat.
Might be caused by the "fix" for MC-122596 (which wasn't really a fix).
When pressing the command key (the one that opens the chat with a pre-written /), autocomplete doesn't open (to suggest words like advancement, bossbar, clear, …).
Deleting and re-typing the slash doesn't open autocomplete either. Writing something after the slash and deleting it again also doesn't open autocomplete. Only pressing the chat key and manually typing the slash opens autocomplete.
This was caused by the fix for MC-122596. A better solution than working around all these inconsistencies and bugs would be to just make arrow keys not go through suggestions. Tab and Shift+Tab are enough. (Or mouse, haha.)
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.
No, mouse isn't fast enough to be efficient. But tab and shift+tab are enough.
Still in 18w01a
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
Thought it got fixed at some point but it's still in 18w08b.
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 :