trigger · logistics_skill_level

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

1. 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."
2. 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.