Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-199998

Villager profession translation keys do not include namespaces

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • None
    • 1.16.3, 21w03a, 1.16.5, 21w11a, 21w17a, 1.17 Pre-release 2, 1.17 Pre-release 3, 1.17 Pre-release 4, 1.17 Pre-release 5, 1.17 Release Candidate 1, 1.17 Release Candidate 2, 1.17, 1.17.1 Pre-release 1, 1.17.1 Pre-release 2, 1.17.1 Pre-release 3, 1.17.1, 1.18 Pre-release 1, 1.19.4, 23w16a, 1.20.1, 1.20.2 Pre-release 1, 24w07a, 24w10a, 1.21 Pre-Release 1, 24w34a, 24w36a, 24w40a, 25w02a
    • None
    • Confirmed
    • Internationalisation

      The translation key used for villager professions is of the form: entity.minecraft.villager.<profession>. Because of this, two villager professions with IDs of the same path but different namespaces (such as foo:developer and bar:developer) will have the same translation key, entity.minecraft.villager.developer.

      This is inconsistent with other registries' translation keys in that it does not have a namespace, and less importantly, is not top-level (villager_profession.<namespace>.<path>).

      Steps to reproduce

      1. Execute the following command: /tellraw @s {"translate":"entity.minecraft.villager.librarian"}
      2. Notice that the text is translated, despite the translation key not including a namespace for the minecraft:librarian identifier.

            Unassigned Unassigned
            haykam haykam
            Votes:
            5 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              CHK: