backstory conflict

Started by roper, September 27, 2016, 12:54:39 PM

Previous topic - Next topic

roper

Wanderer joined group, labeled as "Nurse" with a +5 medical trait, but medicine is disabled.  Social is also supposed to get a boost, but is also disabled.
Noticed that childhood and adulthood backstory conflict:
Childhood:  Vatgrown soldier (shooting and malet boost, social debuff, medicine and warden disabled)
Adulthood:  Nurse (medical and social boost)

Not sure if this is a bug, but it doesn't make much sense.

nccvoyager

Indeed, not particularly logical behaviour.
A quirk of the (current) random backstory generation, if I am not mistaken?

Unimportant self-narration between here...
I suppose working around this would take either coding the random backstory generation to check stat bonuses of adulthood against incapable in childhood backstories, or manually disallowing certain combinations.
(No need to look at childhood backstory bonuses to check for incapable in adulthood backstory. Doesn't matter if you have +5 in something as a child and become incapable of it due to something in adulthood. It kind of sucks, but would still be organic and logical. Being incapable of something due to your childhood, but then becoming someone who does exactly that thing as an adult is not particularly logical, however. It could happen I suppose, but...)

The former might mean more coding upfront but less time cross-checking backstories in the future, while the latter would mean more time in the future cross-checking all the backstories upon adding new ones.

..And here.

Regardless, I myself thank you for helping us (RimWorld players) find more joy in logical and organic* digital suffering.

*Actually virtual, not organic. Usually. Hopefully.

roper

Thanks for the response! 
It seems to me that it could be as simple as *in case of conflict, adulthood traits trump childhood traits*.

Zhentar

This is a known issue: https://ludeon.com/mantis/view.php?id=2460 (and apparently Tynan has just fixed it for the next version!)

Tynan

This has been fixed, thanks.
Tynan Sylvester - @TynanSylvester - Tynan's Blog