Instalar Steam
iniciar sesión
|
idioma
简体中文 (chino simplificado)
繁體中文 (chino tradicional)
日本語 (japonés)
한국어 (coreano)
ไทย (tailandés)
Български (búlgaro)
Čeština (checo)
Dansk (danés)
Deutsch (alemán)
English (inglés)
Español de Hispanoamérica
Ελληνικά (griego)
Français (francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (húngaro)
Nederlands (holandés)
Norsk (noruego)
Polski (polaco)
Português (Portugués de Portugal)
Português-Brasil (portugués de Brasil)
Română (rumano)
Русский (ruso)
Suomi (finés)
Svenska (sueco)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraniano)
Comunicar un error de traducción
zero information being given in the description leaves me not knowing what to do, as i haven't tested the new update before updating my modlist
But anyone is free to fork this mod and continue it, no credits are necessary.
you'd just have had to look into the "needs" tab of character editor, activate the "-" to delete memories and then scroll down a bit ;)
I think that mod ultimately removes divorce from all couples though, but in a different way than yours.
https://gtm.steamproxy.vip/sharedfiles/filedetails/?id=2975068661&searchtext=divorce
r/RimWorld/comments/oxjcms/how_to_change_your_pawns_compatibility/
there are apparently some edits you can do to make pawns more compatible, so the divorce problem is solved "at the root". Apparently it involves a lot of searching and tinkering and trial and error though. I wonder if one could make a mod, maybe separate or as part of character editor, that does that work for you - that is, to create two pawns with high compatibility or change their compatibility in the game.
https://gtm.steamproxy.vip/sharedfiles/filedetails/?id=2578520697
That is truly annoying.
at (wrapper managed-to-native) System.Reflection.MonoCMethod:InternalInvoke (object,object[],System.Exception&)
at System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in <filename unknown>:0
--- End of inner exception stack trace ---
Other types of break up might occur from events but I'm not aware of those.