Ludeon Forums

RimWorld => Bugs => Topic started by: Jacuza on October 15, 2018, 11:41:33 PM

Title: [1.0.2057] Allied faction pawn self-tend infection after being rescued.
Post by: Jacuza on October 15, 2018, 11:41:33 PM
Had a few instances where after saving a pawn that went unconscious/pain shock/incapacitated from a raid or transport pod crash, and got an infection, they will self tend their infection if they are awake, thus leading to a really bad quality of tending if their medical level is not decent and eventually die from it.
Title: Re: [1.0.2057] Allied faction pawn self-tend even when being rescued.
Post by: 5thHorseman on October 16, 2018, 12:16:07 AM
Wait how do you rescue someone who's up and walking around?
Title: Re: [1.0.2057] Allied faction pawn self-tend infection after being rescued.
Post by: Jacuza on October 16, 2018, 12:37:37 AM
You don't. It used to be that they'll just stay in bed until they fully recovered. You need to feed and tend them. The problem here is that if they get an infection after being rescued, they are still injured but they are awake, they will self tend their infection.
Title: Re: [1.0.2057] Allied faction pawn self-tend infection after being rescued.
Post by: 5thHorseman on October 16, 2018, 02:01:55 AM
And I can see how this sucks but, they're not your pawn and you can't tell them what to do. Once they can walk they get to decide, are they in your colony or not. That one decided not, and at that moment they became a visitor.
Title: Re: [1.0.2057] Allied faction pawn self-tend infection after being rescued.
Post by: Jacuza on October 16, 2018, 03:10:58 AM
True, but this applies to transport pod crash too. They don't immediately join you as you rescue them, so you might end up getting a colonist that's just about to die from an infection.
Title: Re: [1.0.2057] Allied faction pawn self-tend infection after being rescued.
Post by: Kenneth on December 06, 2018, 03:11:09 PM
I've recently changed self-tending to be impossible if lying in the host faction's medical bed. That should fix this. Thanks for reporting! ;)