Nudists stop and stand indefinitely

Started by espeon1, May 04, 2016, 05:22:48 AM

Previous topic - Next topic

espeon1

One of my characters was a nudist so I set them as nudist but it bugged out and they would stand all day all night till they passed out or needed to eat. When it happen the 2nd time to a new recruit who was a nudist set to nudism I suspected there must be a bug. When I set them to standard clothing they went back on their merry way .

Shinzy

I saw this happen once, had several pawns set to nudist (don't ask)
they all dumped their clothing into the stockpile then clumped together and just stood still like dummies
even though there was lot of hauling for them to do. They all resumed their duties after I set them non nudist, again

I haven't been able to recreate this again
but I can confirm espeon ain't crazy!

Tynan

Anyone got a savegame where this is happening?
Tynan Sylvester - @TynanSylvester - Tynan's Blog

espeon1


espeon1

Poukuram or something till freeze up when set to nudist.

[attachment deleted by admin - too old]

Tynan

Quote from: espeon1 on May 05, 2016, 11:58:01 AM
Poukuram or something till freeze up when set to nudist.

What? I'm sorry, I don't understand what you're saying...
Tynan Sylvester - @TynanSylvester - Tynan's Blog

milon

I'm guessing that's the colonist who will freeze up when set to nudist.  ;)

StorymasterQ

Maybe they're just appreciating each other's bits. That's what I'd do.
I like how this game can result in quotes that would be quite unnerving when said in public, out of context. - Myself

The dubious quotes list is now public. See it here

ison

Quote from: espeon1 on May 05, 2016, 11:58:01 AM
Poukuram or something till freeze up when set to nudist.

I can't reproduce it, Poukram seems to behave normally. Could you please upload the logfile?

Tynan

Tynan Sylvester - @TynanSylvester - Tynan's Blog

ison

#10
Is anyone else experiencing similar issues? It would be great if someone could provide a logfile. It's possible that this bug is already fixed though.

// ok, I'm going to lock this thread now, it's possible that this bug is already fixed as I couldn't reproduce it