安装 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-game this one also seems give to minor settlements 5 slots. May be a bug.
That shouldn't be the case, this mod doesn't have any changes that could affect Minor settlements. I just checked the mod and it works as expected for me. Do you, by any chance, use any other BSE mod version at the same time with this one? Because you don't need to, this version is standalone. All you need for this mod to work properly is Mixer and Building slot submod for Mixer. Can you please try to start a new campaign with only these three mods active and check if you'll still have 5 slots in Minor settlements?
I did notice that using this mod (BSE Major Settlements) and Alarayn's 4-tier minor settlement mod does cause the minor settlements to have 5 slots. I tried using the compatibility submod you made for Alarayn after that, but I think keeping the 4-slot minor settlements isn't really it's intention.
All said, that was the only thing I noticed. It'd be great if there was an option to use this BSE Major settlement mod with Alarayn's, all while keeping the 4-slot minor settlements.
That is the case and very weird one at that, because everything seems to work just fine without Alarayn's mod. Maybe it has issues interacting with Mixu's building slots submod. it happened before when Mixu's submod added one additional building slot to special settlements like Altdorf, Lothern and Hell Pit. Then I had to hardcode 10 slots for those settlements in my Minor Settlements Only version. Maybe I'll have to do the same here, but I'm not sure if this will fix the issue with Alarayn's mod.
Anyway, I will take a look at that, thank you for your report!
This is probably due to the latest changes CA made to startpos files in 2.2.0. I had to replace the old ones, because they caused various bugs with LLs whose starting positions were changed (like Teclis, Kairos etc.). Nothing we can do about it sadly, unless CA revert their changes in the next patch.