MC-188265The word "blocks" within some "/locate" command feedback messages is always pluralized
The Bug:
The word "blocks" within some "/locate" command feedback messages is always pluralized.
This is an issue because when the value before the given noun is "1", the noun's plural form is used instead of its singular one, therefore making the string grammatically incorrect in some cases.
Affected Strings:
Before reading the table, please note the following:
- Words colored in GREEN are correct.
- Words colored in RED are incorrect.
| Translation Key | Current String | Expected String | String URL on Crowdin |
|---|---|---|---|
| commands.locate.biome.success | The nearest %s is at %s (%s blocks away) | The nearest %s is at %s (%s block(s) away) | https://crowdin.com/translate/minecraft/10038/enus-engb#5341660 |
| commands.locate.poi.success | The nearest %s is at %s (%s blocks away) | The nearest %s is at %s (%s block(s) away) | https://crowdin.com/translate/minecraft/10038/enus-engb#5341666 |
| commands.locate.structure.success | The nearest %s is at %s (%s blocks away) | The nearest %s is at %s (%s block(s) away) | https://crowdin.com/translate/minecraft/10038/enus-engb#5341654 |
Alternatively, instead of having one string cover both the plural and non-plural variants of the word, two separate translation strings could be created, one of which covers the plural variant and the other that covers the non-plural variant.
Steps to Reproduce:
- Display any of the affected strings as listed above by using the command provided below and replacing "XYZ" with the string's translation key.
/tellraw @s {"translate":"XYZ"} - Look closely at the affected word within the string.
- Take note as to whether or not some words within "/clear" command feedback messages are always pluralized.
Observed Behavior:
The word "blocks" is always pluralized.
Expected Behavior:
The word "blocks" would be correctly singularized or pluralized where appropriate.
Linked Issues
- Unresolved
mattp_12- 7
- 3
- Confirmed
Low- Platform
- Commands Text
- grammar pluralization spelling
1.16-pre2 - 25w06a
1.16-pre2 1.19.4-pre3 1.19.4-pre4 1.19.4-rc1 1.19.4-rc2 1.19.4-rc3 1.19.4 23w12a 23w13a 23w14a 23w16a 23w17a 23w18a 1.20-pre1 1.20-pre2 1.20-pre4 1.20-pre5 1.20-pre6 1.20-pre7 1.20-rc1 1.20 1.20.1-rc1 1.20.1 23w31a 23w32a 23w33a 23w35a 1.20.2-pre2 1.20.2-pre3 1.20.2-pre4 1.20.2-rc1 1.20.2-rc2 1.20.2 23w40a 23w41a 23w42a 23w43a 23w43b 23w44a 23w45a 23w46a 1.20.3-pre1 1.20.3-pre2 1.20.3-pre3 1.20.3-pre4 1.20.3-rc1 1.20.3 1.20.4-rc1 1.20.4 23w51b 24w03a 24w03b 24w04a 24w05a 24w06a 24w07a 24w09a 24w10a 24w11a 24w12a 24w13a 24w14a 1.20.5-pre1 1.20.5-pre2 1.20.5-pre3 1.20.5-pre4 1.20.5-rc1 1.20.5-rc2 1.20.5 1.20.6-rc1 1.20.6 24w18a 24w19b 24w20a 24w21a 24w21b 1.21-pre1 1.21-pre2 1.21-pre3 1.21-pre4 1.21-rc1 1.21 24w33a 1.21.1-rc1 1.21.1 24w34a 24w35a 24w36a 24w37a 24w38a 24w39a 24w40a 1.21.2-pre1 1.21.2-pre2 1.21.2-pre3 1.21.2-rc1 1.21.2-rc2 1.21.2 24w44a 1.21.3 24w45a 24w46a 1.21.4-pre1 1.21.4-rc3 1.21.4 25w02a 25w03a 25w04a 25w05a 25w06a
Created Issue:
When using /locate or /locatebiome, "blocks away" isn't properly changed to "block away" when you are 1 block away from target
When you use /locate or /locatebiome and move slightly away from the target, the output of the command says the coordinates of where the destination is, along with "(1 blocks away)". This output should be "(1 block away)".
Environment
Windows 10
Bundled Java version
Attachments2
When using /locate or /locatebiome, "blocks away" isn'tproperlychanged to "block away" when you are 1 block away from target
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
![[Mod] SPGoding](../../../data/avatars/users/44622.png){kind=small}
relates to
![[Mojang] Moesh](../../../data/avatars/users/10122.svg){kind=small}
Low![[Mod] ampolive](../../../data/avatars/users/18949.svg){kind=small}
Windows 10
Bundled Java version
![[Mod] Avoma](../../../data/avatars/users/86198.png){kind=small}
When you use /locate or /locatebiome and move slightly away from the target, the output of the command says the coordinates of where the destination is, along with "(1 blocks away)". This output should be "(1 block away)".The Bug:
The word "blocks" within some "/locate" command feedback messages is always pluralized.
This is an issue because when the value before the given noun is "1", the noun's plural form is used instead of its singular one, therefore making the string grammatically incorrect in some cases.
Affected Strings:
Before reading the table, please note the following:
- Words colored in GREEN are correct.
- Words colored in RED are incorrect.
Translation Key Current String Expected String String URL on Crowdin commands.locate.biome.success The nearest %s is at %s (%s blocks away) The nearest %s is at %s (%s blocks away) commands.locate.poi.success The nearest %s is at %s (%s blocks away) The nearest %s is at %s (%s blocks away) commands.locate.structure.success The nearest %s is at %s (%s blocks away) The nearest %s is at %s (%s blocks away) Alternatively, instead of having one string cover both the plural and non-plural variants of the word, two separate translation strings could be created, one of which covers the plural variant and the other that covers the non-plural variant.
Steps to Reproduce:
- Display any of the affected strings as listed above by using the command provided below and replacing "XYZ" with the string's translation key.
/tellraw @s {"translate":"XYZ"}
- Look closely at the affected word within the string.
- Take note as to whether or not some words within "/clear" command feedback messages are always pluralized.
Observed Behavior:
The word "blocks" is always pluralized.
Expected Behavior:
The word "blocks" would be correctly singularized or pluralized where appropriate.
When using /locate or /locatebiome,"blocks away" isn't changed to "block away" when you are 1 block away from targetThe word "blocks" within some "/locate" command feedback messages is always pluralized
The Bug:
The word "blocks" within some "/locate" command feedback messages is always pluralized.
This is an issue because when the value before the given noun is "1", the noun's plural form is used instead of its singular one, therefore making the string grammatically incorrect in some cases.
Affected Strings:
Before reading the table, please note the following:
- Words colored in GREEN are correct.
- Words colored in RED are incorrect.
Translation Key Current String Expected String String URL on Crowdin commands.locate.biome.success The nearest %s is at %s (%s blocks away) The nearest %s is at %s (%s blocks away) commands.locate.poi.success The nearest %s is at %s (%s blocks away) The nearest %s is at %s (%s blocks away) commands.locate.structure.success The nearest %s is at %s (%s blocks away) The nearest %s is at %s (%s blocks away) Alternatively, instead of having one string cover both the plural and non-plural variants of the word, two separate translation strings could be created, one of which covers the plural variant and the other that covers the non-plural variant.
Steps to Reproduce:
- Display any of the affected strings as listed above by using the command provided below and replacing "XYZ" with the string's translation key.
/tellraw @s {"translate":"XYZ"}
- Look closely at the affected word within the string.
- Take note as to whether or not some words within "/clear" command feedback messages are always pluralized.
Observed Behavior:
The word "blocks" is always pluralized.
Expected Behavior:
The word "blocks" would be correctly singularized or pluralized where appropriate.
The Bug:
The word "blocks" within some "/locate" command feedback messages is always pluralized.
This is an issue because when the value before the given noun is "1", the noun's plural form is used instead of its singular one, therefore making the string grammatically incorrect in some cases.
Affected Strings:
Before reading the table, please note the following:
- Words colored in GREEN are correct.
- Words colored in RED are incorrect.
Translation Key Current String Expected String String URL on Crowdin commands.locate.biome.success The nearest %s is at %s (%s blocks away) The nearest %s is at %s (%s block(s) away) https://crowdin.com/translate/minecraft/10038/enus-engb#5341660 commands.locate.poi.success The nearest %s is at %s (%s blocks away) The nearest %s is at %s (%s block(s) away) https://crowdin.com/translate/minecraft/10038/enus-engb#5341666 commands.locate.structure.success The nearest %s is at %s (%s blocks away) The nearest %s is at %s (%s block(s) away) https://crowdin.com/translate/minecraft/10038/enus-engb#5341654 Alternatively, instead of having one string cover both the plural and non-plural variants of the word, two separate translation strings could be created, one of which covers the plural variant and the other that covers the non-plural variant.
Steps to Reproduce:
- Display any of the affected strings as listed above by using the command provided below and replacing "XYZ" with the string's translation key.
/tellraw @s {"translate":"XYZ"}- Look closely at the affected word within the string.
- Take note as to whether or not some words within "/clear" command feedback messages are always pluralized.
Observed Behavior:
The word "blocks" is always pluralized.
Expected Behavior:
The word "blocks" would be correctly singularized or pluralized where appropriate.
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
is duplicated by
![[Helper] Johnibur](../../../data/avatars/users/28381.png){kind=small}
![[Helper] pine1needle](../../../data/avatars/users/41329.png){kind=small}
This is related to MC-188265.
Thank you for your report!
We're tracking this issue in MC-188265, 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
Why isn't this going to be fixed?
Mojang moves in mysterious ways...
Confirmed in 1.20.1, 1.20.2 and 23w46a.