安装 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(越南语)
Українська(乌克兰语)
报告翻译问题










-- The upcoming KheOpps Mod (inspired by the GeoscApps project) will make all of that modular approach logical in terms of packaging objectives. THAT one will be built in a single UPK along with necessary unique files. Cuz, it makes senses... in terms of quantity (16 regions with 3-8 Nations each on average, only!) It *IS* still a coding mega-task.
Anyhow... sorry for the wall. Just wanted to make everything clear.
But lemme explain why i choose to split them in some small(er) individual (TO compile) files.
-- I have informal future plans to create an optional/configuration tool that would allow people to pick&select whichever items they'd prefer to activate at any given time. 165+ might feel appealing at first -- but once you have played a few games, you'll soon realize the RNG might not reflect that much variety every so often. Code-wise, it will MUCH easier to deal with the settings and file(s) tagging process in external functions that can handle array driven "chunks" rather than having to scan through a flip-flop stack of extensive data. It's technical -- so to speak.
-- The structure itself (i feel) can be referred to in a more intuitive manner.
(Cont..)