effect · add_logistics

Hands-On Usage

add_logistics is commonly used to grant newly generated commanders initial logistics skills, or to reward player officer growth through scripted events or decisions. For example, after completing a technology tree branch or campaign objective, you can boost a specific officer's logistics capability, enabling them to perform better on supply-constrained battlefields:

# Grant logistics skill to a specific character within an event option
some_character = {
    add_logistics = 2
}

Synergy

• [add_skill_level](/wiki/effect/add_skill_level): Overall skill level increases are often combined with individual skill bonuses. Pairing with add_logistics creates a "holistic growth" reward package for commanders.
• [add_unit_leader_trait](/wiki/effect/add_unit_leader_trait): Logistics skill improvements typically work alongside logistics-related traits (such as supply expert traits), jointly strengthening a commander's supply management capabilities.
• [logistics_skill_level](/wiki/trigger/logistics_skill_level): Before executing add_logistics, use this trigger to check the current logistics level. This allows you to set upper limit conditions and prevent stacking beyond reasonable bounds.
• [gain_xp](/wiki/effect/gain_xp): If your mod uses an experience-driven growth system, you can first accumulate experience with gain_xp, then complement it with add_logistics for direct value adjustment—the two approaches are mutually reinforcing.

Common Pitfalls

1. Incorrect scope: add_logistics must execute within a CHARACTER scope. Newcomers often write it directly in country or province scopes, causing script errors or silent failures. You must first enter the character scope using constructs like some_character = { ... }.
2. Ignoring skill caps: In-game commander skills have hidden upper limits. Inputting excessively large values won't cause infinite growth, nor will it produce error messages—making it easy for developers to assume the script worked while the actual value gets capped. It's recommended to pair this with [logistics_skill_level](/wiki/trigger/logistics_skill_level) for conditional checks.