Affects : Probably anything after which a bracket of any kind can be used, without adding a space first. Such as blocks in /setblock, /fill and /clone, items in /give, /clear and /replaceitem, and target selectors (that's everything I noticed, but there may be things I missed).
After tab-completing an argument (like /setblock ~ ~ ~ furna [TAB]), the bracket suggestions do not appear like they would if it was typed out manually. This also applies to the selector suggestions, e.g. (/kill @a[gamemode=survi [TAB])
Attachments
Comments 9
migrated
I'm not sure what to think. It seems to have only been partially fixed, in the sense that you can for example write "minecraft:acacia_button{}" without having an error being displayed, but the game still doesn't suggest opening a curly bracket. Of course, this block would have no use of it (and it seems to be why that bracket isn't suggested, the same way " { " and " [ " are both "missing" for blocks such as carpets). But I guess a mod could add one ? Maybe that in this case, the curly bracket would then automatically start being suggested as well ? That would be a nice thing, but I am unable to test if that's the way it works.
To make it clear though, now " [ " does show in most cases for /fill, /setblock and /clone, as well as " { " for /give, /replaceitem and /clear (normal blocks only for the last one). And if the fact that they don't appear for any block is intended, then I guess we're still missing the suggestion " { " for all "#blocks" in /clear commands (but then I think it would be the only thing missing).
As for the part of the bug where I talked about brackets not showing after a tab-completion, I realized it must be WAI since "Tab" can be used to move between the suggestions. Of course it won't both allow to navigate through the block suggestions but only suggest the brackets at the same time.
It would have been nice if the game could provide the bracket suggestions in a more intuitive way, but both solutions I thought of are bad (keeping in mind a player not knowing about these brackets should still easily see them being suggested).
Anyway, maybe I should remove that part ?
I'm not sure what to think. It seems to have only been partially fixed, in the sense that you can for example write "minecraft:acacia_button{}" without having an error being displayed, but the game still doesn't suggest opening a curly bracket. Of course, this block would have no use of it (and it seems to be why that bracket isn't suggested, the same way " { " and " [ " are both "missing" for blocks such as carpets). But I guess a mod could add one ? Maybe that in this case, the curly bracket would then automatically start being suggested as well ? That would be a nice thing, but I am unable to test if that's the way it works.
To make it clear though, now " [ " does show in most cases for /fill, /setblock and /clone, as well as " { " for /give, /replaceitem and /clear (normal blocks only for the last one). And if the fact that they don't appear for any block is intended, then I guess we're still missing the suggestion " { " for all "#blocks" in /clear commands (but then I think it would be the only thing missing).
As for the part of the bug where I talked about brackets not showing after a tab-completion, I realized it must be WAI since "Tab" can be used to move between the suggestions. Of course it won't both allow to navigate through the block suggestions but only suggest the brackets at the same time.
It would have been nice if the game could provide the bracket suggestions in a more intuitive way, but both solutions I thought of are bad (keeping in mind a player not knowing about these brackets should still easily see them being suggested).
Anyway, maybe I should remove that part ?
The item tag issue is MC-237306 (now fixed), so I've removed it from this ticket.