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
1) just my mods
2) the error-implicated roster of mods applied to the same save file
3) a brand new save file using the error roster from the very start
4) or a brand new save file using the error roster from the very start, with Big and Small - Framework above Odyssey
Therefore, the actual culprit(s) are hidden elsewhere in your modlist, and whatever is causing the error occurs so far up the chain of logic that's supposed to occur on kill it can't be directly seen in the error log. Sorry.
For your woes, however, I suggest you press "Auto-sort mods". Big and Small - Framework should be below Odyssey, and the fact that it's above Odyssey in your modlist suggests to me that other mods that should be below others aren't in the right positions either, which is liable to cause all sorts of errors when you have tons of mods running.
https://gist.github.com/lordmuff/12f39e37386331dd2be2a9cfd1368a03
note how you have a Harmony patch on RecordsUtility.Notify_PawnKilled, and the error is happening around RimWorld.Pawn_RelationsTracker.Notify_PawnKilled
hope this is useful and not a red herring
https://gist.github.com/HugsLibRecordKeeper/2b20e5099cabb522aec4d9e5d2a87b9c