Game Mechanics Text-Component-Based Client-Sided Localization

This is an alternative way at tackling the localization problem, allowing the problem to be solved much easier.

Currently, client-side mods that operate on game text such as Voices of Wynn and WynnLang must match on text directly. This has problems though:
1. Much of the game's content is one-time only, which causes the translations of these contents to be practically unverifiable.
2. Every patch may contain changes to the game's text, which, even if insignificant, will cause the client translations to fail.
These problems cause any attempt at making a localization mod for the game extremely infeasible, and so people have to rely on largely inaccurate machine translations to play the game.

To solve this problem, instead of directly sending text to clients, the game can instead make full use of Minecraft's text component system and send translatable text components instead, and use the resource pack or fallback for text. With this method, the client can use the resource pack to change game text to whatever they want. (I'm sure this isn't a thing yet since Voices of Wynn still matches text directly)

Since translation fallback was added in 1.19.4 and WynnCraft is now using 1.20.4, it is now completely possible to not reveal secret information until someone encounters it and it is sent to the client. For non-secret information though, it is probably better to either completely use the resource pack instead, or release an official English-only translation resource pack, for ease of translation and avoiding the verifiability problem.

Some examples and proposals:

Spoiler: Quest Dialogue Example 1

Original, section 1 of King's Recruit:
[1/2] Caravan Driver: Agh!
[2/2] Tasim: Hey, <playername>! You alright in there? Looks like we hit something.

Proposed text component form (colors not applied):

Code:

[
  {
    "text": "[1/2]"
  },
  {
    "text": " "
  },
  {
    "translate": "npc.caravan_driver",
    "fallback": "Caravan Driver"
  },
  {
    "text": ": "
  },
  {
    "translate": "quest.kings_recruit.1.1",
    "fallback": "Agh!"
  }
]

Code:

[
  {
    "text": "[2/2]"
  },
  {
    "text": " "
  },
  {
    "translate": "npc.tasim",
    "fallback": "Tasim"
  },
  {
    "text": ": "
  },
  {
    "translate": "quest.kings_recruit.1.2",
    "fallback": "Hey, %1$s! You alright in there? Looks like we hit something.",
    "with": [
      {
        "text": "<playername>"
      }
    ]
  }
]

Spoiler: Item Lore Example 1

Original, Iron String:
Iron String
Many said making a bow out of iron would be slow and wasteful, but the weight of the iron arrow can pierce even stone.

Proposed text component form (colors not applied):

Code:

item_name: {
  "translate": "item.bow.iron_string",
  "fallback": "Iron String"
},
lore: [..., {
  "translate": "item.bow.iron_string.lore",
  "fallback": "Many said making a bow out of iron would be slow and wasteful, but the weight of the iron arrow can pierce even stone."
}]

 

Interesting suggestion. I don't have the programming knowledge to know if it's feasible. Suppose you'll have to wait for CT to chime in (it's the Devs who'd know whether this is possible, and there's only 2 of them, neither active on Forums - they're probably overworked anyway).