CK III - Beneficial title integration chancellor events require incorrect, excellent skill level.

[CyberSpyder]

Short summary of your issue Beneficial title integration chancellor events require incorrect, excellent skill level.

Game Version 1.2.1

What OS are you playing on?
Windows

What platform are you using?
Steam

Do you have mods enabled? No

Have you tried verifying your game files (Steam only)?
Yes

How much "pain" is this causing you?
2

Please explain the issue you experienced in the most condensed way possible
The chancellor events that can fire to aid integration of a title are supposed to be able to trigger when their skill is better than mediocre (>8); instead, they are currently requiring better than high (>15).

Compare the triggered descriptions:

			desc = council_task_possible_side_effects
			triggered_desc = {
				trigger = {
					diplomacy > mediocre_skill_rating
				}
				desc = task_integrate_title_nobles_support_integration
			}
			triggered_desc = {
				trigger = {
					diplomacy > mediocre_skill_rating
				}
				desc = task_integrate_title_culture_supports_integration
			}

To the actual event trigger

	trigger = {
		NOT = { has_character_flag = had_event_chancellor_task_2102 }
		exists = cp:councillor_chancellor
		scope:councillor = cp:councillor_chancellor
		scope:councillor = {
			diplomacy > high_skill_rating
		}

In the original release there was an error that this condition had been copied over from the *bad* events, and required diplomacy < high_skill_rating. At some point that was 'fixed,' flipping the inequality - but it's still making a comparison to the wrong value.

To fix it, events/councillor_task_events/chancellor_task_events.txt needs to be modified on line 943, 1055, and 1178, changing the existing "diplomacy > high_skill_rating" lines to be "diplomacy > mediocre_skill_rating"

Please explain how to reproduce the issue


Is there anything else you think could help us identify/replicate the issue?


I have attached a save game
No

 

[Mr.Tarreth]

Hello, CyberSpyder!

Thank you for your report!

We have added the issue to our bug database.