trigger · is_subject_of

Hands-On Usage

is_subject_of is commonly used to check conditions related to subject/puppet relationships, such as determining in decisions or national focuses whether a country is a subject of a specific overlord, thereby unlocking or restricting specific diplomatic options. Typical scenarios include: availability checks in decisions where the overlord provides aid to its subjects, or trigger conditions when a subject seeks independence.

# Example of available condition in a decision for a subject requesting independence
available = {
    is_subject_of = ROOT          # Check if the executing country is a subject of ROOT
    NOT = { has_autonomy_state = autonomy_free }
}

Synergy

• [has_autonomy_state](/wiki/trigger/has_autonomy_state): Combined with is_subject_of, this allows you to further refine subject types (puppet, dominion, etc.) and avoid treating all subject relationships uniformly.
• [compare_autonomy_progress_ratio](/wiki/trigger/compare_autonomy_progress_ratio): After confirming a subject relationship exists, use this to further evaluate autonomy progress ratio, useful for designing progressive independence event chains.
• [any_subject_country](/wiki/trigger/any_subject_country): When iterating through all subjects from the overlord's perspective, this is often paired with is_subject_of in nested scopes for reverse verification to ensure bidirectional logical consistency.
• [end_puppet](/wiki/effect/end_puppet): When the is_subject_of condition is met, trigger this to end the subject relationship—a standard partner in the result block of "independence events."

Common Pitfalls

1. Scope direction confusion: The scope of is_subject_of must be the subject country itself, with the target being the overlord; beginners often write this trigger directly under the overlord's scope, causing the condition to always evaluate false. The correct approach is to first switch to the subject's scope (such as through every_subject_country or event FROM scope) before checking the condition.
2. Target written as tag string: The target only supports scope keywords (THIS, ROOT, PREV, etc.) and cannot directly use country tags (such as GER); if you need to check a specific country tag, use any_subject_country combined with tag = XXX instead.