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(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
There isn't any vanilla behavior that tries to generate a pawn when another pawn dies anyway. It's not impossible that this mod would prevent whatever's generating a pawn from failing to generate relations for that pawn (and you can just load this mod and test, it's completely safe to add/remove at any time) but I very much doubt that that's really the core of the issue you're experiencing.
Error while generating pawn. Rethrowing. Exception: System.NullReferenceException: Object reference not set to an instance of an object
[Ref 47650D8D]
at RimWorld.Pawn_RelationsTracker+<get_FamilyByBlood_Internal>d__37.MoveNext () [0x001f5] in <2a40c3593b334f29ac3cb3d32d652351>:0
at ....
Thanks for this mod!
Thank you For the mod I was getting so annoyed by this.
The function that we are replacing got an additional condition under which it gets set to 0 (IsDuplicate) but since we're setting it to 0 under all circumstances anyway, anomaly will work completely fine with this.
giving it some thought, if these new relations are created only whenever a raid or some other incident (like visitors for example) happens, then doing what you said should indeed work for preserving starting relations.
thanks for the input.
I don't know if this is correct, but that is what I believe would happen.
In theory if you have a mod like Character Editor you should be able to go through the global list of all human pawns and I think that the son should exist in that list somewhere.