Ideology bug

[Ellelarondelle]

this happens with charitable colonies EVERY time a pilgrim shows up "Pilgrims not helped -2"

only vanilla, Phoebe Chillax, Peaceful

[Pheanox]

The pilgrims that show up, specifically, are the pilgrims that show up to view your relic?  Just want to make sure I'm clear.

[glass zebra]

The pilgrims that show up to visit your relic triggers this.

https://steamuserimages-a.akamaihd.net/ugc/1841409371003040816/DEF32EC8F6BF6725547A8F9FFCE57D88D5693D5D/
https://steamuserimages-a.akamaihd.net/ugc/1841409371003047903/ACEE65A5D9C23110ABDB8A688AB48068FE72B0BA/
https://steamuserimages-a.akamaihd.net/ugc/1841409371003041936/0DC95BF114DB5EA582719FE2501A1E83EEFD28BB/

I am not even sure what the message means since you have no option to deny it. She went into my shrine, looked at the relic for a bit and went away. My people got the debuff. (ignore that there are two debuffs. I added one charity precept with dev mode and forgot that I already had one)

[Ark]

Core + Ideology 1.3.3200, no mods. I just had this happen. The moment the pilgrims spawn colonists get Pilgrims not helped -8 mood debuff.
The quest has not failed, and can end successfully.
These are the first reliquary pilgrims that arrived to this colony. Doing the Archonexus questline, two relics were brought from the previous colony, working on the third one.

Beware that this save was started in 1.3.3069. It has been edited both with dev mode and text editor.

Pilgrims spawned naturally without dev mode: https://easyupload.io/vpwxpl
Autosave just before that: https://easyupload.io/ayl7s0

Tried reproducing it with a new game in 1.3.3200 without success.
It seems that it doesn't fix itself after one firing and consequent pilgrim events also trigger -8 mood, so I'll just add

Code Select Expand


<savedscenario>
<scenario>
<parts>
<li Class="ScenPart_DisableIncident">
<def>DisableIncident</def>
<incident>GiveQuest_ReliquaryPilgrims</incident>
</li>

to the savefile and pretend that everything is fine.

[Pheanox]

Ark, thanks for the additional information.  So this may be a bug from cross-version games?  I will see if I can reproduce it on 1.3.3200 as well, but if its only on cross-update games I can bring that up with the devs as an angle of attack.  We do try to make updates compatible, though I will be honest it tends to make lower priority bugs even lower priority.