Ludeon Forums

RimWorld => General Discussion => Topic started by: zandadoum on September 08, 2020, 05:43:42 AM

Title: Fibrous Mechanites prevent from meditating?
Post by: zandadoum on September 08, 2020, 05:43:42 AM
Hello,

I have had this thing ocurring for the past ingame days where my most important psycasters don't seem to go meditate, even when i set their whole schedule to meditating...

apparently all those psycasters have fibrous mechanites right now.

so my question is: is this normal, is this intended or a bug?
Title: Re: Fibrous Mechanites prevent from meditating?
Post by: Canute on September 08, 2020, 05:45:26 AM
A fast search at the General Discussion about meditate and you would found
https://ludeon.com/forums/index.php?topic=52921.0
Title: Re: Fibrous Mechanites prevent from meditating?
Post by: zandadoum on September 08, 2020, 06:22:24 AM
Quote from: Canute on September 08, 2020, 05:45:26 AM
A fast search at the General Discussion about meditate and you would found
https://ludeon.com/forums/index.php?topic=52921.0
some other forum users (with even less post count than i do) wondering "why this is happening" and then directly assuming this is a bug, does hardly answer my question
Quote
so my question is: is this normal, is this intended or a bug?
i'd like a definitive answer, not speculation. thank you very much.
Title: Re: Fibrous Mechanites prevent from meditating?
Post by: Mr_Fission on September 09, 2020, 07:14:06 PM
Discord patch notes for build 1.2.2744 states "- Improve meditation and medical rest priorities to allow meditation for pawns with healing injuries if they're on meditation schedule."

That's not terribly descriptive, so I used dev mode to add Fibrous Mechanites to my caster on the unstable server.

I found that when the caster has the affliction, and it is *NOT* treated, she will not meditate.  However, as soon as I treat the affliction, she will begin to meditate.

This behavior differs from the stable build, where the caster will not meditate with Fibrous Mechanites, regardless of whether it's been treated or not.

Given this change in behavior on the unstable server, combined with the patch note on the Discord, from my perspective, the stable build's behavior seems to be the bug, and the unstable build's behavior seems to be the correctly-implemented feature.