Hints for command arguments don’t show up for words right after slash symbol /
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”
Linked Issues
Created Issue:
Hints for command arguments don’t show up for words right after slash symbol /
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, for example in progress names or in objects added through data packs.
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”
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, for example in progress names or in objects added through data packs.
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”
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, for example in progress names or in objects added through data packs.
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”
duplicates
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, for example in progress names or in objects added through data packs.
In 24w09a, dots have been added to this list of delimiters, meaning that slashes are now the only special character commonly present in commands that is not considered a delimiter.
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”
relates to
duplicates
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, for example in progress names or in objects added through data packs.
In 24w09a, dots have been added to this list of delimiters, meaning that slashes are now the only special character commonly present in commands that is not considered a delimiter.
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”
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, for example in progress names or in objects added through data packs.
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.
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”
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, for example in progress names or in objects added through data packs.
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.
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”
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, for example in progress names or in objects added through data packs.
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.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”
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, for example in progress names or in objects added through data packs.
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.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”
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
, for example in progress names or in objects added through data packs.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.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”
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”
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”
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”
duplicates
relates to
New bug report for slashes only: MC-270650



I've reopened this because dots are now considered a delimiter as of 24w09a. Not sure if Mojang's decision from back then still stands, for that reason.
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.