-
Bug
-
Resolution: Fixed
-
1.19 Pre-release 5, 1.19 Release Candidate 2, 1.19, 1.19.1 Pre-release 1, 1.19.1 Pre-release 2, 1.19.1 Pre-release 5, 1.19.1, 1.19.2, 22w45a, 1.19.3, 1.19.4
-
Confirmed
-
Text
-
Low
The Bug:
Chat restriction strings consist of inconsistent concluding punctuation.
In 1.19 Pre-release 5, two new strings were added to the game. These were "chat.disabled.profile" and "chat.disabled.profile.moreInfo". Despite being relatively and reasonably similar, only one of the strings consists of a period/full stop, therefore introducing an inconsistency.
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 |
|---|---|---|
| chat.disabled.profile | Chat not allowed by account settings. Press '%s' again for more information | Chat not allowed by account settings. Press '%s' again for more information. |
| chat.disabled.profile.moreInfo | Chat not allowed by account settings. Cannot send or view messages. | Chat not allowed by account settings. Cannot send or view messages. |
Steps to Reproduce:
- Display both of the affected strings by running the commands provided below.
/tellraw @s {"translate":"chat.disabled.profile"}/tellraw @s {"translate":"chat.disabled.profile.moreInfo"} - Look closely at the concluding punctuation within both of the strings.
- Take note as to whether or not chat restriction strings consist of inconsistent concluding punctuation.
Observed Behavior:
Chat restriction strings sometimes contain concluding punctuation and sometimes don't.
Expected Behavior:
All chat restriction strings would contain concluding punctuation.