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






In fairness I'm running a lot of mods along with LWOTC, so might be an incompatibility somewhere. I've been testing, disabling this mod stops the bug from occurring for me at least.
I know there was a big fixed in the LWOTC mod at some point that caused this, I wonder if this mod is somehow regressing that bugfix.
However, there might be a problem. I've set the str and vig in the config to be 2 and 2, in line with a legend start. Everything worked as described - I got the region that I wanted and the str and vig were 2 and 2. However, I did three missions in this starting region, and the vigilance has not increased - it is still 2. Should I disable the mod after I start a campaign, or how does is work? LWOTC, no game altering mods. Thanks!