trigger · `planning_skill_level`

Definition

Supported scope:CHARACTER, COMBATANT
Supported target:none

Description

Compares planning skill level of a unit leader.
Example: planning_skill_level > 5

实战 · 配合 · 坑

实战内容由 AI 生成,并已对照 vanilla 命令词表校验 —— 请当作起点而非权威依据。上方的定义节才是游戏自带文档原文。

实战用法

planning_skill_level 常用于判断某位将领是否具备足够的计划能力，以解锁特殊决议、激活特定 AI 加成或在事件中触发差异化选项。例如在自定义将领成长系统中，只有规划值达标才允许晋升或获得稀有特质：

# 在将领晋升事件的 trigger 块中
character_event = {
    id = my_mod.101
    trigger = {
        is_corps_commander = yes
        planning_skill_level > 3
        has_trait = organizer
    }
    # 满足条件后授予进阶特质
    option = {
        add_trait = brilliant_strategist
    }
}

配合关系

[has_trait](/wiki/trigger/has_trait)：通常与特质检测联用，确认将领同时拥有特定特质且规划值达标，构成"特质 + 能力值"的双重门槛。
[min_planning](/wiki/trigger/min_planning)：两者共同用于精确校验将领当前规划增益状态，前者看基础等级，后者看战役中的实时规划积累。
[add_planning](/wiki/effect/add_planning)：在 trigger 判断通过后，通过该 effect 对满足条件的将领进一步叠加规划能力，形成"检测-奖励"闭环。
[add_trait](/wiki/effect/add_trait)：当 planning_skill_level 达到阈值时授予新特质，是将领培养类 mod 最常见的搭配模式。

常见坑

比较运算符混用：新手容易写成 planning_skill_level = 5（等于），但该 trigger 设计上用于大小比较（>、<、>=），等号判断行为不稳定且通常不是预期意图，应明确使用比较运算符。
Scope 未切换至 CHARACTER/COMBATANT：在国家 scope 或州省 scope 下直接写此 trigger 会导致报错或静默失败；必须先通过 any_army_leader、every_character 等语句切入正确的将领 scope，再执行判断。

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

planning_skill_level is commonly used to determine whether a commander possesses sufficient planning capability to unlock special decisions, activate specific AI bonuses, or trigger differentiated options in events. For example, in a custom commander progression system, only commanders with adequate planning values are permitted to be promoted or acquire rare traits:

# In the trigger block of a commander promotion event
character_event = {
    id = my_mod.101
    trigger = {
        is_corps_commander = yes
        planning_skill_level > 3
        has_trait = organizer
    }
    # Grant advanced trait upon meeting conditions
    option = {
        add_trait = brilliant_strategist
    }
}

Synergy

[has_trait](/wiki/trigger/has_trait): Typically used in conjunction with trait detection to confirm a commander possesses both a specific trait and meets the planning value threshold, establishing a "trait + ability value" dual gate.
[min_planning](/wiki/trigger/min_planning): Both are used together for precise verification of a commander's current planning bonus state; the former checks the base level while the latter monitors real-time planning accumulation during a campaign.
[add_planning](/wiki/effect/add_planning): After the trigger condition passes, use this effect to further stack planning capability for qualifying commanders, forming a "check-reward" feedback loop.
[add_trait](/wiki/effect/add_trait): When planning_skill_level reaches a threshold, grant new traits; this is the most common pairing pattern in commander development mods.

Common Pitfalls

Mixing comparison operators: Beginners often write planning_skill_level = 5 (equals), but this trigger is designed for magnitude comparison (>, <, >=); equality checks produce unstable behavior and typically don't match the intended purpose. Always use explicit comparison operators.
Scope not switched to CHARACTER/COMBATANT: Directly writing this trigger under country scope or state scope causes errors or silent failures; you must first transition to the correct commander scope via statements like any_army_leader or every_character before executing the check.

trigger · planning_skill_level