[zisunny104]

Brings lang/cht/lang.ini back in line with lang/eng/lang.ini and cleans it up to standard Taiwan Traditional Chinese usage.

Missing and untranslated entries

• Add the 16 keys that were missing from cht: newer potion/effect names (levitation, conduit power, slow falling, bad omen, hero of the village, darkness, trial omen, wind charged, weaving, oozing, infested, raid omen, breath of the nautilus), commands.summon.success/failed and commands.gamemode.fail.invalid (it was showing as a raw key in game).
• Translate 10 entries that were still English: six death messages, the /clear description, usage and success message, and the plugin resource pack loading message.
• Effect and death message wording follows Mojang's official Traditional Chinese strings (Java wording where the Java and Bedrock strings differ).

Wording and punctuation

• Replace mainland wording with the Taiwan equivalents: 加載→載入, 文件→檔案, 設置→設定, 創建→建立, 坐標→座標, 數據→資料, 檢測→偵測, 許可→授權, 運行→執行, 用戶端→客戶端. "Load" is 載入 everywhere (was a mix of 加載 and 讀取), and the server start message is 啟動完成（{%0} 秒）.
• Use full-width punctuation and 「」 for quotes, with no spaces next to them; ellipses stay ..., like in the other languages; put a space between Chinese and Latin text or numbers.
• A "level" is now 世界 everywhere (it was a mix of 地圖 and 世界), and the "opening server" and "logged in" console messages read more naturally.
• Operator is 伺服器管理員 in the op and deop descriptions, like in the other op messages.
• Remove a stray zero-width character in nukkit.resources.unknown-format.
• Remove nukkit.command.saveoff.description and nukkit.command.saveon.description: they don't exist in eng and nothing in the code references them.

Usage strings

The usage strings now say what the English text says, with one Chinese word for one English word:

• "player" is 玩家 everywhere ("name" stays 玩家代號 in /ban, /pardon and /ban-ip), "value" is 數值, "OR" is 或.
• Fixed translations that did not match the English or what the command does: /particle takes a particle name (it said 玩家代號), /tp target and destination player (they were swapped), /give takes tags, /enchant takes an enchantment level, /me takes an action, and /banlist [ips|players] keeps the words the player has to type.
• Fixed nukkit.mistranslations: commands.give.item.notFound is a lookup by name, not ID; "implementing API" in nukkit.server.info.extended is now 實作; the whitelist description said "the admin allows" instead of "manages the list".
• commands.effect.success now takes the four values the code passes. The English text still takes five, that is fixed in the follow-up PR.

Checks

• Every key in eng exists in cht, and no key exists only in cht.
• {%N} placeholders match the English entries for every key except commands.effect.success (see above).
• Line endings stay CRLF as before. Command usage lines such as /list are left as they are.

Only src/main/resources/lang/cht/lang.ini is touched. Not tested in a running server.

Review

The Traditional Chinese (zh_TW) texts were drafted with the help of an AI assistant (Claude Code). They were then reviewed item by item by a human, a native zh_TW speaker from Taiwan (@zisunny104), and compared with Mojang's official zh_TW strings wherever an official string exists.

Sources

• Mojang bedrock-samples, resource_pack/texts/zh_TW.lang and en_US.lang (https://github.com/Mojang/bedrock-samples): wording of the command messages and of the effect names.
• Minecraft: Java Edition 1.21.11 zh_tw.json (read from the public mirror https://github.com/InventivetalentDev/minecraft-assets): effect names and two death messages, where it differs from Bedrock.
• Minecraft Wiki command pages, e.g. https://minecraft.wiki/w/Commands/effect: the official parameter names.

---

審閱

繁體中文（zh_TW）由 AI 助理（Claude Code）協助起草，之後由真人逐項核對，核對者是來自台灣的 zh_TW 母語者（@zisunny104），並在有官方字串時與 Mojang 官方繁中對照。

參考來源

• Mojang bedrock-samples 的 zh_TW.lang 與 en_US.lang：指令訊息與效果名稱的用詞。
• Minecraft Java 版 1.21.11 的 zh_tw.json（從公開鏡像讀取）：效果名稱與兩條死亡訊息，在與基岩版不同時採用。
• Minecraft 維基的指令頁：官方的參數名稱。

🤖 Generated with Claude Code

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.