安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
0 
举报此帖
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).