[MC-112602] "disconnect.spam" kick message is untranslated

The message that is displayed when kicked for spamming is not translated, instead appearing as disconnect.spam. This has been an issue since the creation of that message in Minecraft 1.3.

Reproduction

Connect to a server, and start spamming the chat. After roughly 10-12 messages, you will be disconnected for spam. (You must not be OP on the server, as OPs are exempt from the spam check, although I've found that spamming a lot as an op and then deoping myself can trigger the spam check in a way that more consistently creates this behavior).

You should receive a disconnection screen saying disconnect.spam. If it says instead "Disconnected" (disconnect.genericReason) or "Disconnected by Server" (disconnect.disconnected), try again.

Cause

disconnect takes a String which is used to create a text component, not a translation component. While there is a translation value defined for disconnect.spam (Kicked for spamming), it goes unused because the text is not translated.

Possible fixes:

Send a translation component instead of a text component, so that disconnect.spam is actually translated (like the other disconnect translation keys)
Pre-translate that message (as with other messages sent in that context) to the current English version ("Kicked for spamming")

Linked issues

relates to

MC-18060 Several realms strings are untranslatable

MC-14923 Players can be kicked for spamming in a singleplayer world with cheats disabled

Attachments

Comments

marcono1234 2017-01-18T17:42:47Z

Relates to MC-14923

migrated 2023-12-01T12:46:52Z

This should be re-opened, it's still untranslated in 1.20, and is unrelated to MC-14923 (this is about a missing translation key, not about being kicked in single player).

pokechu22 2023-12-01T18:35:48Z

I'm pretty sure the that this was fixed in 1.12 (in that I tested it and confirmed that "Kicked for Spamming" shows up). I also can confirm that there is a disconnect.spam translation key (and I'm pretty sure if that existed in the past too, it just wasn't being translated).

If this has started occurring again in more recent versions, it'd be better to create a new ticket, as it probably regressed due to something else. If I instead messed up with my testing and it also occurs in 1.12, I can reopen this ticket.