Hunt event where same-sex, heterosexual relative becomes romantic partner?

[celtek]

This has happened a few times. I do a Hunting event and out of nowhere, a same-sex heterosexual relative becomes a romantic partner out of the blue and gives me some trinket. I'm wondering what pre-empted this or if it's a bug.

I've crossed out some PII in the above screenshot.

 

[Tiax]

        # Fetch lover
        scope:activity = {
            random_in_list = {
                variable = potential_hunt_participants
                limit = { 
                    has_relation_soulmate = root # prioritise soulmates
                    is_alive = yes 
                    is_ai = yes 
                }
                alternative_limit = {
                    is_powerful_vassal = yes  # second priority is characters that are interesting gameplay-wise
                    is_alive = yes 
                    is_ai = yes 
                }
                alternative_limit = {
                    has_secret_relation_lover = root 
                    is_alive = yes 
                    is_ai = yes 
                }
                alternative_limit = { 
                    has_relation_lover = root # Fallback is boring lover 
                    is_alive = yes 
                    is_ai = yes 
                }
                save_scope_as = hunting_courtier
            }
        }

It looks like this event weirdly includes powerful vassals as an option alongside lovers.

 

[vitek69]

This has happened a few times. I do a Hunting event and out of nowhere, a same-sex heterosexual relative becomes a romantic partner out of the blue and gives me some trinket. I'm wondering what pre-empted this or if it's a bug.

View attachment 891459


I've crossed out some PII in the above screenshot.

At least he's you character's nephew. I had this happen with my character's son
Thanks to @Tiax I now know that he doesn't have some weird father-son fetish

 

[celtek]

        # Fetch lover
        scope:activity = {
            random_in_list = {
                variable = potential_hunt_participants
                limit = {
                    has_relation_soulmate = root # prioritise soulmates
                    is_alive = yes
                    is_ai = yes
                }
                alternative_limit = {
                    is_powerful_vassal = yes  # second priority is characters that are interesting gameplay-wise
                    is_alive = yes
                    is_ai = yes
                }
                alternative_limit = {
                    has_secret_relation_lover = root
                    is_alive = yes
                    is_ai = yes
                }
                alternative_limit = {
                    has_relation_lover = root # Fallback is boring lover
                    is_alive = yes
                    is_ai = yes
                }
                save_scope_as = hunting_courtier
            }
        }

It looks like this event weirdly includes powerful vassals as an option alongside lovers.

That's interesting. Thanks for digging this up. Clarifying yet still confusing as to why it was designed like this.

 

[Tiax]

That's interesting. Thanks for digging this up. Clarifying yet still confusing as to why it was designed like this.

My guess is someone set out to make more events prioritize important characters and accidentally dropped it in places it didn't belong.

 

[EphemeralToast]

I reported this as a bug some time ago... guess it wasn't fixed

CK III - Hunting event wrongly identifying non-lovers as lovers

Short summary of your issue Hunting event wrongly identifying non-lovers as lovers Game Version 1.5.1 What OS are you playing on? Mac What platform are you using? Steam What DLC do you have installed? Royal Court, Do you have...

forum.paradoxplaza.com

 

[Voy]

It's missing this.

                alternative_limit = {
                    is_powerful_vassal = yes  # second priority is characters that are interesting gameplay-wise
                    OR = {
                    has_secret_relation_lover = root
                    has_relation_lover = root
                    }
                    is_alive = yes
                    is_ai = yes
                }

And if one is to be picky all of the is_ai checks should be is_available_ai_adult to prevent them from being occupied, a carrier of some plague, in jail, or incapable (braindead). Actually, the "potential_hunt_participants" already covers this.

 

[dsendorek]

I'm more interested in why OP felt the need to censor his primary title and Targaryen House name.

 

[Maxwell Tornado]

I'm more interested in why OP felt the need to censor his primary title and Targaryen House name.

Maybe he's a tester for the GoT mod. I don't know why he'd post here, instead of talking with the mod devs, though. (Even though this instance happens to be a vanilla bug.)

 

[kawamuratc]

My guess is someone set out to make more events prioritize important characters and accidentally dropped it in places it didn't belong.

Yeah. They may have confused this event for one that gives a option to have a quick tumble on a hunt. Or maybe it was a copy/paste job gone wrong.

I reported this as a bug some time ago... guess it wasn't fixed

CK III - Hunting event wrongly identifying non-lovers as lovers

Short summary of your issue Hunting event wrongly identifying non-lovers as lovers Game Version 1.5.1 What OS are you playing on? Mac What platform are you using? Steam What DLC do you have installed? Royal Court, Do you have...

forum.paradoxplaza.com

Thanks for the link. If I remember, I’ll try and bump it with a save game showing the bug is still there.

 

[Studoku]

Paradox have stated that they refuse to do QA- sometimes this slips through the cracks.