[Wattls]

Adds i18n/zh-CN.json — the complete Simplified Chinese catalog.

Scope: this PR touches only i18n/zh-CN.json. It has the same keys, in the same order, as i18n/pt-BR.json in this repository (1.20.1, 5,254 keys). node scripts/validate-i18n.mjs passes locally.

@meta kept as you asked: "lang": "zh-CN", "machine": true, "reviewed": false, with the sourceHash of the current i18n/pt-BR.json.

About the translation

I am a native Simplified Chinese speaker, playing Aion 2 on the Global client. I have been maintaining a Chinese build of AionCore locally since 1.15.1, so this catalog is not a fresh machine run: it has been through every release since, and the game nouns come from the official Aion 2 client's own zh-Hans strings rather than transliteration.

Game terms kept in Chinese (deliberate)

Most keys read the same as what already ships. The differences are mainly game nouns, which I translated instead of leaving in English:

Source term	Chinese	Why
Cubo Oculto / Hidden Cube	隐藏背包	That is the item's name on the Chinese client. 方块 / 立方体 would be a mistranslation.
Kinah	基纳	Currency name.
Combat Power	战斗力	The client uses 战斗力.
Odyle energy	奥德能量
Abyss Points	深渊点数

One more: inside the rDPS tooltip, the English "gain" (ganho) appears twice meaning two different things — the gain a player gets from the party's buffs, and the gain the party gets from that player's buffs. Translating both as 增益 produces duplicated wording (「增益带来的增益」), so I used 收益 for gain and 增益 for buff. If your glossary prefers another pair, say so and I will change it in one pass.

If you would rather keep the English names for the items above, tell me — it is a mechanical replace and I will send it.

Regarding 1.20.5

i18n/pt-BR.json here is 1.20.1. My local catalog is already synced to 1.20.5 (5,583 keys): the 329 keys added since 1.20.1 are translated and validated the same way. I kept this PR aligned with the 1.20.1 source so the automated check stays green. The 10 keys that exist only in the 1.20.1 source are included here too, so nothing is lost. When i18n/pt-BR.json is refreshed to the current release, I can send the delta — or the full catalog — immediately.

Consent / legal / privacy

Included with the rest, but I understand you review consent.*, legal.*, site.* and firstrun.* yourselves before importing. I am happy to do a second pass on those with you, in the wording you want for the consent flow.

Credit and terms

• Credit: Wattls (GitHub).
• Contribution terms (2026-10-19): read and agreed.

Thanks for opening the i18n/ route — keeping a language in sync across releases is much easier this way.