Bugs and weirdities in lovers_events.txt

[richvh]

• Event 64005 (Sick lover: Pneumonic or ill)
  • The effect for option D should select a female lover, to match the trigger and option text.
• Event 64010 (You have become infatuated by someone in the same court)
  • Should not trigger if ROOT is a eunuch or incapable
  • Should not trigger for an opposite sex courtier who is either incapable or a eunuch
• Event 64015 (Old and ugly wife, take a mistress?)
  • Should not trigger for a female courtier that is incapable
  • Should trigger for a spouse that is incapable
  • If spouse is incapable, the angry opinion should probably not be applied, nor event 64016 triggered, in options A and B
  • Is adding celibate really appropriate for option C (No, it's a sin)? I should think chaste would be more appropriate.
• Event 64025 (You have fallen in love with your spouse)
  • Event should not trigger for a ruler or spouse that is a eunuch
• Event 64030 (A week with your lover)
  • Should not trigger for a lover that is incapable or a prisoner
  • The spouse reaction should come I think if ROOT has any lover that is not ROOT's spouse, rather than if the ROOT is not one of the spouse's lovers
• Event 64035 (You lover complains you never do anything exciting)
  • Should not trigger for a lover that is incapable or a prisoner
  • In the case that ROOT's spouse is his lover, and he has another lover, additional logic is needed for the courtier's angry reactions, depending on which lover he brought
  • The option B and C limits for the lover don't match the event triggers
• Event 64040 (Ruler confronts cheating spouse)
  • Should not trigger for an incapable spouse, or a lover that is incapable or a prisoner
• Event 64041 (Spouse confronted)
  • If the above changes are made to the lover's triggers, the matching changes should be done to the lover's triggers in this event
• Event 64045 (You have lost that loving feeling
  • Should possibly not trigger for a lover that is incapable or a prisoner (or maybe a new event/event chain should be written for the case where one lover is incapable, imprisoned, or abroad)
• Event 64050 (Infatuation turned into love?)
  • Should not trigger for a sweetheart who is imprisoned or incapable (or perhaps only option B should be available if imprisoned or incapable)
• Event 64055 (Child is infatuated with courtier)
  • Should not trigger if child is incapable or a ruler (thus not in parent's court), or courtier is incapable
• Event 64060 (Loving a married woman is being quite a pain to your soul)
  • Should not trigger for a lover who is incapable or a prisoner
  • In option B, the test should be for religion_group = muslim, not religion = muslim
• Event 64065 (This kind of unsatisfying relationship to a married woman is really becoming irksome to you)
  • Should not trigger for a lover who is incapable or a prisoner
  • Should not be restricted to married rules (nothing in the event text says the ruler is married, and unmarried people can have moral qualms about having an affair with a married woman)
• Event 64070 (Seeing another woman behind your spouse's back is becoming quite troublesome for you)
  • Should not trigger for a spouse that is incapable, or a lover who is incapable, a consort or a prisoner (I know consorts are not in the vanilla game, but an official consort is not a lover you are seeing behind your spouse's back)
• Event 64075 (You are having a special occasion with your lover in the near future, but your wife is insistent on alternate plans)
  • Should not trigger for a female ruler
  • Should not trigger for an incapable wife or lover
• Event 64076 (Spouse meets lover)
  • ROOT (the wife) should become the rival of FROM's lover, not FROM (the cheating husband)
• Event 64077 (Spouse hates you)
  • Going along with the above suggestion for 64077, I think there should be an opinion modifier applied toward the husband, rather than becoming a rival
• Event 64080 (Your wife has retired to the convent for a short while)
  • Should not trigger for a spouse that is not Christian or is incapable, or for a lover this is male, incapable or a prisoner
  • In option A, should not add lustful or notify lustful if already lustful
  • In option B, should not add and notify deceitful if already deceitful
  • In option C, should not add and notify craven if already craven
• Event 64085 (Two adult character are lovers and neither are married)
  • Should not fire for a prisoner, or if the lover is incapable or a prisoner
• Event 64086 (Liege is notified)
  • In the 25 weight chance, where the spouse is sent event 64088, the tooltip should match
• Event 64090 (Childless marriage)
  • Should not trigger if spouse is incapable
• Event 64095 (Wife is pregnant, you are not the father)
  • Option A should not apply and notify wroth if already wroth, or cruel if already cruel
  • Option B should not apply and notify kind if already kind, and the spouse is AI (is_ruler = no) so no need to notify her of celibate
  • Option C should not apply and notify kind if already kind
  *]Event 64100 (Your lover is eager to comfort you after you have had a particularly fiery row with your wife)
  • Should not trigger if lover is male, incapable or a prisoner
  • Option C should not add and notify proud if already proud
  • Either event 64100 should trigger on spouse being not a ruler, or event 64102 should notify wroth if not already wroth
• Event 64110 (Your spouse has grown suspicious of your behaviour)
  • Spouse should not be incapable, lover should not be incapable or prisoner or a consort
  • Option A should not add/notify proud if already proud
  • Options B and C should not add/notify deceitful if already deceiful
  • Option D should not add/notify humble if already humble
• Event 64115 (Lover thinks you love spouse more than him/her)
  • Spouse and lover should not be incapable
  • Option B should not add/notify lustful if already lustful
  • Option C should not add/notify slothful if already slothful
  • Option D should not add/notify cruel if already cruel, or honest if already honest

 

[PeterSkager]

I'm finally done making reports out of all of the event issues Took some hours since I had to separate them for individual reports, but thanks for the report! If you have the opportunity in the future however, it would ease our workflow if we got these issues as separate reports. But I get why it might be easier for you to make a master post. In any case, really nice work! Let's hope these get fixed soon.