Nainstalovat Steam
přihlásit se
|
jazyk
简体中文 (Zjednodušená čínština)
繁體中文 (Tradiční čínština)
日本語 (Japonština)
한국어 (Korejština)
ไทย (Thajština)
български (Bulharština)
Dansk (Dánština)
Deutsch (Němčina)
English (Angličtina)
Español-España (Evropská španělština)
Español-Latinoamérica (Latin. španělština)
Ελληνικά (Řečtina)
Français (Francouzština)
Italiano (Italština)
Bahasa Indonesia (Indonéština)
Magyar (Maďarština)
Nederlands (Nizozemština)
Norsk (Norština)
Polski (Polština)
Português (Evropská portugalština)
Português-Brasil (Brazilská portugalština)
Română (Rumunština)
Русский (Ruština)
Suomi (Finština)
Svenska (Švédština)
Türkçe (Turečtina)
Tiếng Việt (Vietnamština)
Українська (Ukrajinština)
Nahlásit problém s překladem
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!