安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题
And some titles are wrong named in other ranks, these are just some of my thought about the game content, just for your reference
gualish: d_middlesex -> d_bedford (c_middlesex in capital)
bangladeshi: d_tamralipti -> d_suhma (c_tamralipti in capital)
lower_saxon: d_lubeck -> d_holstein (c_lubeck in capital) in 00_names.txt file
austrian_hybrid: d_austria -> k_austria or d_osterreich (c_vienna in capital)
kochi: d_kacharia -> d_para_lauhitya (eng loc name: Kachari Raj), trigger maybe also can add d_sutiya nearby?
muscovite: title:k_opoyle (error) -> title:k_opolye (correct)
mamluks: title:k_jurusalem -> title:k_jerusalem
iraq: title:k_mespotamia -> title:k_mesopotamia
judios: culture:shepardi -> culture:sephardi
kochi, bangladeshi: title:d_kamarupanaga -> title:d_kamarupanagara
madridian: d_toldedo -> d_toledo
porto: d_combria -> d_coimbra
Another issue is capital_county scope problem in kham and vlaemsch hybrid culture triggers.
Yes anyone may use this work and add their own local translations. All you should do is edit the localization file and just change the names inside the “ “.
I’m not play ck3 as frequently. I do plan to always revisit on dlc updates. I am always adding names and possible combinations as each play through has the AI do funky things. Most recently I adjusted the “romantic” catch all for Iberians and French to narrow a trigger in for Pyrenees( I’m seeing it occur frequently here)
I’m also always open to suggestions or point out frequent hybrids that the AI does with no good name or poor naming.