trigger · `logistics_skill_level`

Definition

Supported scope:CHARACTER, COMBATANT
Supported target:none

Description

Compares logistics skill level of a unit leader.
Example: logistics_skill_level > 5

实战 · 配合 · 坑

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

实战用法

logistics_skill_level 常用于根据将领的后勤技能等级动态解锁特质、触发事件或限制指令可用性，例如制作"精英后勤将领"相关内容的 mod。也可以在 available 块中限制某些顾问角色或特质只对高后勤技能将领开放，实现技能门槛机制。

# 示例：仅当后勤技能达到 4 级时才允许添加某个特质
add_unit_leader_trait = {
    limit = {
        logistics_skill_level > 3
        is_corps_commander = yes
    }
    trait = supply_master
}

配合关系

[planning_skill_level](/wiki/trigger/planning_skill_level) — 常与后勤技能判断并列，同时检查规划技能，构建"全能型将领"的综合条件筛选。
[attack_skill_level](/wiki/trigger/attack_skill_level) / [defense_skill_level](/wiki/trigger/defense_skill_level) — 搭配使用可对将领多维技能设置阈值，避免单一技能溢出导致判定失真。
[add_logistics](/wiki/effect/add_logistics) — 在 effect 侧配合使用，先用 trigger 判断当前后勤等级是否不足，再通过该 effect 补充后勤技能点，防止重复叠加。
[has_trait](/wiki/trigger/has_trait) — 与技能等级判断配合，确保将领同时满足"特质"和"技能数值"双重条件，使触发逻辑更精确。

常见坑

比较运算符写错：logistics_skill_level 必须配合比较运算符（>、<、>=、<=、==）使用，直接写 logistics_skill_level = 5 在部分版本下语义与 == 不同，容易造成判断结果不符合预期，建议明确使用 >= 或 > 来表达"至少达到某等级"的意图。
Scope 混用：该 trigger 仅在 CHARACTER / COMBATANT scope 下有效，若在国家 scope（如国家事件的 trigger 块顶层）直接使用而不先切换到对应将领 scope，脚本将静默失败或报错，需通过 any_army_leader、has_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

logistics_skill_level is commonly used to dynamically unlock traits, trigger events, or restrict command availability based on a leader's logistics skill level, such as when creating mods related to "elite logistics commanders." It can also be used within available blocks to restrict certain advisor roles or traits exclusively to leaders with high logistics skills, implementing a skill threshold mechanism.

# Example: Allow adding a specific trait only when logistics skill reaches level 4
add_unit_leader_trait = {
    limit = {
        logistics_skill_level > 3
        is_corps_commander = yes
    }
    trait = supply_master
}

Synergy

[planning_skill_level](/wiki/trigger/planning_skill_level) — Often used alongside logistics skill checks to simultaneously verify planning skill, creating comprehensive filtering conditions for "well-rounded commanders."
[attack_skill_level](/wiki/trigger/attack_skill_level) / [defense_skill_level](/wiki/trigger/defense_skill_level) — Can be used together to set multi-dimensional skill thresholds for leaders, preventing judgment distortion caused by single-skill overflow.
[add_logistics](/wiki/effect/add_logistics) — Used in conjunction on the effect side; first use a trigger to check if the current logistics level is insufficient, then supplement logistics skill points via this effect to prevent duplicate stacking.
[has_trait](/wiki/trigger/has_trait) — Combined with skill level checks to ensure the leader meets both "trait" and "skill value" conditions simultaneously, making trigger logic more precise.

Common Pitfalls

Incorrect comparison operators: logistics_skill_level must be used with comparison operators (>, <, >=, <=, ==). Writing logistics_skill_level = 5 directly may have different semantics from == in some versions, easily causing unexpected judgment results. It is recommended to explicitly use >= or > to express the intent of "at least reaching a certain level."
Scope mixing: This trigger is only valid in CHARACTER / COMBATANT scope. If used directly at the national scope level (such as the top level of the trigger block in national events) without first switching to the corresponding leader scope, the script will silently fail or throw an error. Use any_army_leader, has_character, or similar methods to enter the correct scope first.

trigger · logistics_skill_level