MC-186341Command autocomplete doesn't consider parts after a slash
The bug
In 20w15a command autocomplete was changed to also consider parts after an underscore. Text after a period or slash however, is not included in the suggestion results. This causes some confusing results with the attribute IDs
How to reproduce
- Type "/attribute @s hea"
generic.max_health is correctly suggested - Type "/attribute @s max"
generic.max_health is not shown
Linked Issues
is duplicated by2
![[Helper] Misode](../../../data/avatars/users/93314.png){kind=small}
Created Issue:
Command autocomplete doesn't consider parts after a period
The bug
In 20w15a command autocomplete was changed to also consider parts after an underscore. Text after a period however, is not included in the suggestion results. This causes some confusing results with the attribute ID's
How to reproduce
- Type "/attribute @s hea"
- Type "/attribute @s max"
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
The bug
In 20w15a command autocomplete was changed to also consider parts after an underscore. Text after a period however, is not included in the suggestion results. This causes some confusing results with the attribute ID
'sHow to reproduce
- Type "/attribute @s hea"
- Type "/attribute @s max"
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
Command autocomplete doesn't consider parts after a period or slash
The bug
In 20w15a command autocomplete was changed to also consider parts after an underscore. Text after a period or slash however, is not included in the suggestion results. This causes some confusing results with the attribute IDs
How to reproduce
- Type "/attribute @s hea"
- Type "/attribute @s max"
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
relates to
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
is duplicated by
is duplicated by
relates to
is duplicated by
![[Mojang] Maxime Lebrot](../../../data/avatars/users/18941.svg){kind=small}
is duplicated by
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
relates to
Normal![[Mojang] Gegy](../../../data/avatars/users/10122.svg){kind=small}
[Mojang] GegyCommand autocomplete doesn't consider parts after aperiod orslash
![[Bot] Piston](../../../data/avatars/users/31202.png){kind=small}
Thank you for your report!
We're tracking this issue in MC-186341, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit
The problem:
When typing in a name of an in-game object as a command argument, Minecraft shows hints for possible argument values. Sometimes there are delimiters like underscore (_), dot (.) or colon (:). They are counted as delimiters and one can find an argument by a word coming right after such delimiter. However, it appears that slash (/) is not accounted for, despite it being another delimiter used in some object names.
The same issue was also present for dots before 24w09a, as reported in MC-186341, but in 24w09a this was fixed, meaning that slashes are now the only special character commonly present in commands that is not considered a delimiter.
Most importantly, that affects the advancements. The actual names of the advancements, known by the community, are located after a slash in the resource path, making them impossible to find by the first word of the name.
Steps to reproduce:
- Launch Minecraft in an affected version, create or join a world with commands on
- Pick an advancement (for example, minecraft:husbandry/whole_pack)
- Open chat and type in /advancement grant @s only
- Then add the advancement name after the slash (for example, /advancement grant @s only whole_pack)
Observed behaviour:
No hint shows up for the advancement
Expected behaviour:
One or several hints should show up, including the wanted advancement, the same way as minecraft:husbandry/whole_pack shows up when inputting “pack” or “husbandry/whole_pack”
Thank you for your report!
We're tracking this issue in MC-186341, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
This is a feature request.
No, this is not a feature request, this is a bug report about an inconsistency.
Imagine that jungle fences would open towards the player instead of away like all others. Inconsistencies are bugs.
How is this a feature request? Bugs like
MC-182309are closely related, yet they are apparently "Important". Please reopen this.This was fixed in 24w09a for periods.
Can confirm for slash (/) in 1.20.5 Pre-release 1. Added screenshots 0_hints_whole_pack.png, 1_hint_husbandry_whole_pack.png and 1_hint_pack.png to illustrate
New bug report for slashes only:
MC-270650