Wiki

trigger · pc_turn

Definition

  • Supported scope:any
  • Supported target:none

Description

Checks turn number in PC.
Example:
pc_turn > 20

Hands-On Notes

Hands-on notes are AI-generated and checked against the vanilla command vocabulary — treat them as a starting point, not authoritative reference. The definition above is the game's own documentation.

Hands-On Usage

pc_turn is commonly used in mods featuring a Power Balance system, dynamically triggering events or unlocking options based on in-game round count. For example, certain faction actions may only be permitted after a specific round. It can also be used for phased logic in PC systems, such as restricting player options within a set number of rounds to create a narrative sense of "time pressure."

available = {
    pc_turn > 20
    is_power_balance_in_range = {
        id = my_power_balance
        range = { min = 0.5 max = 1.0 }
    }
}

Synergy

  • [is_power_balance_in_range](/wiki/trigger/is_power_balance_in_range): The PC system typically coordinates with power balance values. Check the current round first, then verify faction leanings to implement logic like "trigger if the scale tips toward a faction after round X."
  • [power_balance_value](/wiki/trigger/power_balance_value): Pair with round count to read the current power balance value at specific round phases, enabling fine-grained comparisons that avoid premature or delayed triggering.
  • [check_variable](/wiki/trigger/check_variable): When tracking cross-round cumulative states (such as cumulative action counts for a faction), combining with pc_turn constructs "conditional thresholds within a round window."
  • [add_power_balance_value](/wiki/effect/add_power_balance_value): Execute within effect blocks that satisfy round conditions to drive power balance changes at specific round nodes, forming a trigger-execution loop with pc_turn triggers.

Common Pitfalls

  1. Using pc_turn in ordinary nation events: pc_turn is exclusive to the PC (Power Contention) system's round counting and is unrelated to in-game dates (date) or global variables. Using it in non-PC events or decisions causes conditions to never trigger or results in undefined behavior. Always confirm your content actually runs within the PC framework.
  2. Confusing comparison operator direction: Beginners sometimes write pc_turn < 20 intending "valid within the first 20 rounds," but forget that PC system rounds count from 1, causing the condition to already be met on round 1. Always carefully verify the greater-than/less-than direction against your PC flow's starting round and intended trigger window.