20w18a, 20w20b, 20w21a, 20w22a, 1.16 Pre-release 2, 1.16 Pre-release 3
The command autocomplete feature in the 1.16 snapshots now also considers parts following an underscore when searching for possible completions. However, this causes an issue when quickly typing commands.
For instance, when typing /setblock ~ ~ ~ sandston, the first result is minecraft:chiseled_red_sandstone, which is most likely not the block that should be on top and automatically selected.
This causes annoying delays when typing commands since the user needs to type the word fully (thus making the autocomplete feature superfluous) or use the arrow keys to scroll to the correct (short) word (which takes some time).
Instead, strings that do not start with the given string but have the given string following an underscore should be sorted below the strings that start with the given string.
- /setblock ~ ~ ~ dir
- /setblock ~ ~ ~ ston
- /setblock ~ ~ ~ sandston
- /setblock ~ ~ ~ terracott
- /summon minecar
- relates to
MC-232425 Inconsistency in tab completion for type=
MC-186341 Command autocomplete doesn't consider parts after a period or slash
- testing discovered
MC-182624 Command autocomplete doesn't consider parts after an underscore if a namespace is specified in the command