[MC-253741] Chat trust status strings consist of inconsistent concluding punctuation

The Bug:

Chat trust status strings consist of inconsistent concluding punctuation.

In 1.19.1 Pre-release 2, two new chat trust status strings were added to the game. These were "chat.tag.modified" and "chat.tag.not_secure". 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.tag.not_secure	This message is not secure	This message is not secure.
chat.tag.modified	This message has been modified by the server.	This message has been modified by the server.

h3. Steps to Reproduce:

Locate any of the affected strings as listed in the table above.
Take note as to whether or not chat trust status strings consist of inconsistent concluding punctuation.

Observed Behavior:

Chat trust status strings sometimes contain concluding punctuation and sometimes don't.

Expected Behavior:

All chat trust status strings would contain concluding punctuation.

Comments 4

Avoma 2022-06-30T17:35:21Z

This ticket closely relates to MC-252408.

[Mod] turbo 2022-06-30T17:35:59Z

Can confirm.

eowyn36 2022-07-04T14:29:35Z

"chat.tag.modified" is always followed by "chat.tag.modified.original"

Avoma 2022-07-04T14:54:23Z

Ohh I see; thank you for your response. So "chat.tag.modified" has to contain a full stop due to it having additional text on the line(s) below it whereas "chat.tag.not_secure" doesn't and therefore there's no need for a period/full stop. That makes sense; thank you! 🙂