Hands-On Usage
core_compliance is commonly used in mods involving occupation or annexation systems. It's particularly useful when you want to unlock specific decisions or national focuses based on your nation's average compliance level in an occupied country. For example, you can use it to check whether the player has raised Italy's compliance to a sufficiently high level before allowing further annexation or autonomy adjustments.
# Example: Only allow this decision to trigger if your nation's core compliance with Italy exceeds 50
available = {
core_compliance = {
occupied_country_tag = ITA
value > 50
}
}
Synergy
[has_collaboration](/wiki/trigger/has_collaboration): Compliance and collaboration typically increase in tandem. Checking both together allows more precise determination of your occupation policy progression stage.
[any_occupied_country](/wiki/trigger/any_occupied_country): Use any_occupied_country to iterate through and find your target occupied nation, then apply core_compliance within its scope for fine-grained condition filtering.
[add_collaboration](/wiki/effect/add_collaboration): When compliance thresholds are met, use it as an effect reward to further increase collaboration, creating a positive feedback loop of "compliance → reward → higher collaboration".
[add_autonomy_score](/wiki/effect/add_autonomy_score): Once compliance conditions are satisfied, award autonomy score changes, commonly used to implement "high compliance unlocks autonomy changes" mod mechanics.
Common Pitfalls
- Incorrect
value comparison operators: Beginners often write value = 50 instead of value > 50. The = operator checks for exact equality in value comparisons; the probability of compliance being precisely equal to an integer is extremely low, making the condition almost never trigger. Use comparison operators like >, <, >= instead.
- Incorrect scope targeting: The primary scope for
core_compliance must be the nation holding occupation rights (the occupier), while occupied_country_tag specifies the occupied nation. Beginners often mistakenly switch the scope to the occupied country before using this trigger, resulting in inverted logic or outright errors.