安裝 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!