trigger · division_has_battalion_in_template

Hands-On Usage

Commonly used to check whether a division template contains specific battalion types, allowing you to restrict or unlock divisions with particular compositions in the available/trigger blocks of focuses, events, or decisions. For example, in an "Armored Breakthrough" national focus, you can require the player to have at least one division template containing medium armor battalions before triggering it:

available = {
    any_division_template = {
        division_has_battalion_in_template = medium_armor
    }
}

Synergy

Since the current whitelist contains no effects or triggers in this scope, there are no same-scope commands available for cross-reference. Therefore, synergy relationships cannot be listed.

Note: The available scope list for this trigger is empty. In actual usage, you must combine it with an outer iterating scope (such as any_division_template) to target a specific division template, otherwise it cannot be evaluated properly.

Common Pitfalls

1. Writing directly under country scope: Beginners often forget that this trigger must exist within a division template scope to function. Writing division_has_battalion_in_template = xxx bare under country-level scope will cause the condition to never evaluate or produce errors. You must wrap it with iteration blocks like any_division_template/every_division_template.

2. Confusing battalion type names: The parameter passed must be the actual token name of a sub_unit defined in /common/units/ (such as light_armor, motorized). Typos or using display names (localization strings) will cause the condition to fail silently with no error messages.