Hands-On Usage
This trigger is particularly useful when you need to dynamically unlock features or restrict policies based on the equipment type currently managed by a military industrial organization. For example, when creating a specialized armor or aviation-focused MIO mod, you can use it to ensure that certain bonuses or missions only apply to MIOs handling specific equipment types.
# Allow activation of a policy only when this MIO is responsible for tank equipment
mio:my_armor_mio = {
limit = {
has_mio_equipment_type = mio_equipment_type_armor
}
add_mio_research_bonus = {
specialization = land
bonus = 0.10
}
}
Synergy
[has_mio_research_category](/wiki/trigger/has_mio_research_category): Often used in conjunction with this trigger, the former filters by equipment type while the latter further narrows down research categories, creating a dual-condition system to ensure precise bonus distribution.
[is_mio_trait_completed](/wiki/trigger/is_mio_trait_completed): Check whether a trait is completed simultaneously while filtering by equipment type, useful for constructing prerequisite chains for trait unlocks.
[add_mio_research_bonus](/wiki/effect/add_mio_research_bonus): Typically serves as the direct reward following equipment type condition validation, making it the most common effect output pairing with this trigger.
[has_mio_size](/wiki/trigger/has_mio_size): When combined with equipment type checks, enables complex unlock conditions such as "the organization must reach a certain size AND specialize in the corresponding equipment type."
Common Pitfalls
- Misspelled equipment type tokens: Valid values come from
script_enum_equipment_bonus_type and common/equipment_groups. Beginners often fabricate strings based on intuition (e.g., infantry instead of the correct enum value), causing the condition to never fire without raising an error. Always cross-reference against source files to verify.
- Wrong scope: This trigger only works within the
INDUSTRIAL_ORG scope. Placing it directly in country scope or other contexts will silently fail. You must first switch to the appropriate MIO scope using mio:your_mio_tag = { ... } before using it.