mojira.dev

takatalvi

Assigned

No issues.

Reported

MC-195467 Missing death message "death.fell.accident.water" and its localization Confirmed MC-195465 "Connection throttled..." string not localized Duplicate MC-168170 Text on signs does not change shade with the sign texture Confirmed MC-168169 Text on signs shows different colors if dyed manually or by command Confirmed MC-152341 Item names not translated in string commands.enchant.failed.incompatible (Server only) Duplicate MC-151857 Wrong string displayed upon /give used for multiple players Confirmed MC-146776 Typo in Difficulty lock (Difficulity lock) Fixed MC-128048 The brain coral looks nothing like a brain coral Invalid MC-107330 Attribute modifiers on items after swapping hands don't work Duplicate

Comments

After some testing, I've found that if you upgrade a world from 1.19.2 to 1.19.3, eye of ender points to different coordinates. When you open the same world back on 1.19.2 (downgrade it), eye of ender points again to the original correct coordinates. The same goes for /locate. Upgrading a world does not overwrite anything in region files.

I've compared stronghold locations using chunkbase. I've projected the same seed on 1.19-1.19.2 (red dots) and on 1.19.3 (orange dots). It appears that the difference in stronghold locations gets bigger depending on how far you are from the map center:

[media]

Can confirm on 1.19.3 - even worlds from 1.19.2 will have their strongholds relocated in 1.19.3, so when you upgrade a world from 1.19.2 to 1.19.3, eyes of ender do not work. Stronghold definitions should stay written in the region files and not be replaced when a world is upgraded. Personally, it's kind of hard to believe this has been raised over 4 years ago and no changes have been made to fix this.

Affects 1.19.1. The signs are shaded depending on their rotation, but this doesn't shade the text, which causes certain dyes to be illegible on signs of certain rotation.

After some thought, I feel like this is not a bug, but rather a feature. However, this would need to be confirmed by the devs who could close this as "works as intended".

We don't need to discuss whether there is this kind of death in Minecraft, because there is no doubt about it. But instead of a nice localized message, the game only displays a technical name of the string. Why? Because it's missing in the /assets/minecraft/lang/ json files. That's the whole issue. This death is not a new one, it's been in the game for a long time. And several major versions ago, the death message was displayed correctly, because it was in the lang jsons. It's even in Crowdin and it has been for at least 8 years (see attached picture 1). The only issue here is that this specific string somehow fell out of the localization process and even the original EN_US string is missing. A simple fix would be to make sure that it's included in the lang jsons. I made a mockup of what that should look like (picture 2).

Picture 1: The string has been introduced a long time ago and it even has translations

[media]

 

Picture 2: This single string simply didn't make it into the lang files

[media]

I searched before submitting this ticket, but couldn't find anything. I voted for MC-18060, thank you.

It's really hard to replicate, but it involves combined damage from fall and from water in a short period of time. I can see that in some older versions it had a string "%s fell out of water" but that's currently missing in assets\minecraft\lang\en_us.json". The string has even been in Crowdin for at least 2 years, but for some reason it's not used now, while it's still possible to get this message.

The colors are indeed identical, the problem is that signs rotated differently have a different brightness, while the text remains the same. This results in some signs being unreadable, as the same text color can be lighter or darker than the background. The description of this bug should be changed to "text on signs does not change its brightness along with the sign's texture". I opened another issue, https://bugs.mojang.com/browse/MC-168170

You're right, I wasn't able to find it. I hope it will get fixed in the next release. Thanks!