Crusader Kings III

Crusader Kings III

87 个评价
More Buildings Reboot + AGOT
3
2
   
奖励
收藏
已收藏
取消收藏
文件大小
发表于
更新日期
2.785 MB
2023 年 6 月 23 日 下午 7:57
10 月 4 日 上午 1:36
32 项改动说明 ( 查看 )

订阅以下载
More Buildings Reboot + AGOT

在 Lost Nomad 的 1 个合集中
Lost Nomad collection
19 件物品
描述
More Buildings Reboot + AGOT

This is a fork of More Buildings Reboot it runs independent of MBR, so you do not need to load MBR to run this mod with AGOT.


Checkout my other mods
热门讨论 查看全部(1)
0
2024 年 3 月 13 日 下午 12:34
2.7.0 update notes
Lost Nomad
81 条留言
Lost Nomad  [作者] 10 月 8 日 下午 3:51 
@Noodler
There's almost always a way to make a compatch between two or more mods, some are relatively easy, while some can be quite extensive, you won't know until you start working on them.
Noodler 10 月 8 日 下午 12:28 
@Lost Nomad
To be expected, although moving your mod above LoV solves this issue it messes up holding UI, but it remains functional. So perhaps there is a way to make compatch?
Lost Nomad  [作者] 9 月 29 日 上午 9:05 
@Noodler
Sounds like LoV modifies the holdings file so there's no surprise the two mods conflict with each other.
Noodler 9 月 29 日 上午 8:41 
It seems Legacy of Valyria's ruin reclaiming system conflicts with your mod. The event after clicking reclaim button doesn't show up:gorlak:
Lost Nomad  [作者] 9 月 5 日 上午 8:50 
@TrueSkum
np, glad you got it sorted :steamthumbsup:
TrueSkum 9 月 5 日 上午 6:52 
@Lost Nomad

Thanks for the advice, i skimmed down my playlist and made some changes to the load order and now everything is fine, i still don't know what the culprit was, i tested the load order with and without this mod and with this mod enabled legends don't cause CTD anymore, also my other problem is fixed aswell (artifact illustrations dissapearing).

i removed like 8 mods and made minor changes to the load order, i don't think the load order was the culprit but still just to be sure, from my perspective there was a broken mod somewhere down the line which conflicted with almost every mod because yours wasn't the only mod that caused CTD's and illustrations to dissapear, still thanks and props for the advice and the great mods you published :)
Lost Nomad  [作者] 9 月 5 日 上午 6:08 
@TrueSkum
Also if the suspected conflicting mod does allow legends to start without CTDs, don't just accept it conflicts with MBR + AGOT, start a new game again with AGOT, MBR + AGOT and the conflicting mod to confirm it does conflict with MBR + AGOT because it could be that the two are fine together and it's in fact a combination of the two mods plus another that causes the conflict which is much harder to isolate.
Lost Nomad  [作者] 9 月 5 日 上午 6:05 
@TrueSkum
np, what you'll have to do now is remove other mods one at a time until you can start a legend with no CTD, then you'll know which one is conflicting with MBR + AGOT, however it may not be a conflict, it may be that mod is just broken, so once you identify what you believe is the conflicting mod then do as I said, start a new game with just AGOT and the conflicting mod and see if it CTDs when you start a legend, if so then the mod is broken otherwise it truly is conflicting with MBR + AGOT.

Good luck :steamthumbsup:
TrueSkum 9 月 5 日 上午 5:41 
@Lost Nomad

Yeah i already suspected it was a problem on my end, now i'm sure that it's conflicting with another mod in my playlist, anyway thanks for the fast reply! and again thanks for your great mods and hard work, it's appreciated!
Lost Nomad  [作者] 9 月 5 日 上午 2:53 
@TrueSkum
I just started a legend on day one with King Baelor using AGOT and MBR + AGOT , so whatever is causing your CTD is in another mod.

Also it seems your thought that any mod which touches buildings causes CTDs with legends is also incorrect. Though that depends on what you mean by how buildings work , MBR + AGOT adds buildings with various buffs, it does not change how buildings work .

When you suspect a mod has a bug you should always start the game with only that mod and any dependencies it has, MBR + AGOT has none other than AGOT , to see if your suspicions are correct.

If you then find that bug is in effect your suspicions are correct, otherwise the bug is either in another mod or caused by a mod conflict between mods.