安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
奖励
3 
This mod uses the base games possession generation logic. If you want pawns to generate with ammo, you should suggest to the mod author of the ammo mod to change how pawn possessions are generated.
The exception stems from this line in base games code:
PawnBioAndNameGenerator.GiveAppropriateBioAndNameTo(pawn, faction.def, request, xenotypeDef);
I assume the faction has NULLed out instead of being a valid value, which coughs up the NullReferenceException in your case. But PfE doesn't touch the pawns faction except for reading it to figure out whether or not to generate possessions. And all the PfE patches are wrapped into try-catch blocks so you would never get a "natural" exception thrown by them.
A simple search over your hugslib did provide multiple different mods that modify faction generation behavior, so I am inclined to suspect one of those are at fault. Specifically faction manager seems like it may be a prime candidate to break factions on pawn generation.
Thanks for the extra details at the top of the link btw, the bugs that you can't reliably reproduce tend to be the hardest ones to fix.
The links are sadly not available, you could try using this site instead:
https://rentry.co/