I think it's unintended site-effect of fixing
a bug which i've reported.
PilotLara sorry to bother you again, but it seems that in addition to fixing those two lines i've listed, the same change from
and to
or was also made here:
Python:
"{image=icon_friend.webp}What's up?" if v10_axel_fight != "ian" and v10_axel_fight != "mikeian" and v9_cindy_shoot != 2:
was changed to
Python:
"{image=icon_friend.webp}What's up?" if v10_axel_fight != "ian" or v10_axel_fight != "mikeian" or v9_cindy_shoot != 2:
But in this particular line the change from
and to
or is actually a mistake -- now this option became selectable even with Ian who took part in the fight, because at least one variant wiill always pass the check. The original version was scripted properly because it was checking for
!= and not
== So this one line should be reverted to how it was.