The block and item name changes listed in the Vanilla Parity section of the 1.21.30.22 Preview Changelog were not applied to the English (UK) language. They only affected the English (US) language.
Also, the Stone Mason villager occupation was not renamed to Mason in the English (UK) language.
Steps to reproduce:
From the main menu, select Settings > Language and select language English (UK).
Create a world with game mode Creative and Cheats enabled. Load it.
In creative inventory, look at each of the blocks and items listed in the changelog and note the name in its tooltip.
Run the command /give @s light_block_0. In your hotbar, note the name in the light block's tooltip.
Place a bed and a stonecutter nearby.
Spawn a villager and allow it to claim the bed and stonecutter. If it's a nitwit (green cloaked villager), kill it and repeat until you get a mason. Open the mason's trading interface and note its occupation.
Expected results:
All the blocks and items have the new names shown in the changelog. The villager's occupation is shown as "Mason".
Observed results:
None of the names have been changed.
Linked issues
relates to 2
Attachments
Comments 5
migrated
This happens for all translations whenever the same key gets a new English (US) translation. This is usually fixed in the next preview/beta. Same problem in Java Edition, that languages other than English (US) are a version behind due to how language translations work (it's just how translations are made available and when they are pushed).
@unknown: Thank you for your interest in helping the bug tracker staff. However, please understand that while we appreciate getting updates about affected versions, confirmations from the community for the originally reported version are not usually helpful. Confirming bug reports is the responsibility of the staff, and we normally have to confirm a report ourselves before it can be passed on to the devs. The only time a confirmation from the community is helpful is when aren't able to confirm it ourselves. In such cases we need to know that it's not just a misunderstanding or mistake by the bug report creator, and if others confirm it we give it the special confirmation status of "Community Consensus" instead of "Confirmed".