Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Shieldwall is a full game overhaul. Mods which are not intended to be used alongside it will probably cause anything from minor problems, to massive imbalances, to crashes. Unless a mod specifically says it is meant to be used with shieldwall overhaul, then you should not be using it with shieldwall.
Like, we edit more than 150 tables, including basically every game system, and many of them are changed to the point that they don't share any data with vanilla. If you're using other people's mods, expect to have serious issues.
This particular problem is caused by using a mod which edits startpos.esf, which would include turn per year mods. As mentioned by the poster above me, they are also unncessary as shieldwall is 12 turns per year by default. Unlike other total war games, unit mods in Thrones of Britannia also require startpos.esf edits, so those will also break the campaign (on top of being game-breakingly unbalanced due to shieldwall's very different unit stats scale from vanilla).