CK3 DatabaseCrusader Kings III · 1.20.1.2 “Crozier” · unofficial
Silk & Silverout Tue, Nov 17What's free, what needs the DLC, price →

Scripted effect · The Fate of Iberia files

fp2_lyonese_monk_return_territories_effect

fp2_lyonese_monk_return_territories_effect = yes

game/common/scripted_effects/03_dlc_fp2_scripted_effects.txt, line 1483 (21 lines). No parameters.

fp2_lyonese_monk_return_territories_effect is a scripted effect in Crusader Kings III, in the The Fate of Iberia files, written at line 1483 of its file. It takes no parameters: fp2_lyonese_monk_return_territories_effect = yes. The game's script calls it in 1 place, among them fp2_lyonese_monk_cancel_chain_effect (scripted effect). Patch 1.20.1.2, from game/common/scripted_effects/03_dlc_fp2_scripted_effects.txt.

What it does

  • If

    Then

    • scope:acolyte › Every held title:
      • title_tier >= county
      • Gains the … Title (acolyte host)

• the game's own tooltip text · ◦ our reading of the script line · code the script where neither exists

“They” is whatever it runs on (the scope it is called in). The scripted triggers and effects it calls link to their own pages; $PARAMETERS$ stay as written: each call fills them in.

The script as written (21 lines of game script)
fp2_lyonese_monk_return_territories_effect = {
	if = {
		limit = {
			scope:acolyte = { is_playable_character = yes }
		}
		create_title_and_vassal_change = {
			type = granted
			save_scope_as = change
		}
		scope:acolyte = {
			every_held_title = {
				title_tier >= county
				change_title_holder = {
					holder = scope:acolyte_host
					change = scope:change
				}
			}
			resolve_title_and_vassal_change = scope:change
		}
	}
}

As written in game/common/scripted_effects/03_dlc_fp2_scripted_effects.txt.

Where it is used

Every place in common/, events/ and history/ that calls fp2_lyonese_monk_return_territories_effect.

Source: game/common/scripted_effects/03_dlc_fp2_scripted_effects.txt and every file of common/, events/ and history/ that calls it, Crusader Kings III 1.20.1.2.

Spotted a mistake on this page?