Summary
The main plugin localization work is now in place, but one notable gap remains: challenge text that comes directly from challenges.yml is still server-authored config text and is not translated automatically.
This currently affects fields such as:
- challenge
name
- challenge
description
- reward
text
As a result, non-English servers can still see English challenge strings in the challenge GUI unless admins translate those entries manually.
Current behavior
These values are loaded directly from challenges.yml and shown to players as-is. They are not part of the normal PO/Crowdin translation pipeline.
Goal
Decide and implement a proper approach for localizing default challenge-pack text. Possible directions include:
- making default challenge definitions locale-aware
- moving bundled default challenge text into the i18n system
- reducing freeform reward text in favor of more structured/generated UI text
Notes
This is intentionally split out from the larger i18n umbrella because the general localization overhaul has already shipped in 3.3.0, while this remaining gap needs its own design and follow-up.
Summary
The main plugin localization work is now in place, but one notable gap remains: challenge text that comes directly from
challenges.ymlis still server-authored config text and is not translated automatically.This currently affects fields such as:
namedescriptiontextAs a result, non-English servers can still see English challenge strings in the challenge GUI unless admins translate those entries manually.
Current behavior
These values are loaded directly from
challenges.ymland shown to players as-is. They are not part of the normal PO/Crowdin translation pipeline.Goal
Decide and implement a proper approach for localizing default challenge-pack text. Possible directions include:
Notes
This is intentionally split out from the larger i18n umbrella because the general localization overhaul has already shipped in 3.3.0, while this remaining gap needs its own design and follow-up.