Hands-On Usage
In MIO-related events or decisions, when you need to execute conditional logic for a specific military industrial organization, use this trigger within the scope referenced by a variable to confirm the current organization's identity and avoid logical errors. A common scenario is iterating through multiple MIO variables and then applying rewards or restrictions to a particular organization.
# In event options, unlock a trait only for a specific military industrial organization
var:selected_mio = {
is_military_industrial_organization = tank_manufacturer_alpha
add_mio_research_bonus = {
specialization = mio_cat_spec_tank
bonus = 0.10
}
}
Synergy
[has_mio_flag](/wiki/trigger/has_mio_flag): Typically use this trigger first to confirm the target organization, then check whether that organization has already set a specific flag, forming a precise dual-filter condition.
[has_mio_trait](/wiki/trigger/has_mio_trait): After confirming the organization's identity, further determine whether it already possesses a certain trait to decide the subsequent logic flow.
[complete_mio_trait](/wiki/effect/complete_mio_trait): After confirming the organization matches, immediately follow up with this effect to directly complete a trait—the standard workflow of "identity verification → reward execution".
[set_mio_flag](/wiki/effect/set_mio_flag): Immediately apply a flag as a marker after the organization identity is confirmed, preventing the event from repeatedly triggering the same logic for the same organization.
Common Pitfalls
- Calling directly under national scope: This trigger is only valid under
INDUSTRIAL_ORG scope. Beginners often forget to first enter the MIO context via a variable or dedicated scope and write it directly in the national event trigger block, which causes script errors or the condition to always evaluate to false.
- Token name inconsistent with actual MIO definition: The token you provide must exactly match the
token = xxx field of the corresponding organization in the mio folder (case-sensitive). Even a single character misspelling will make the condition never true, and the game typically will not provide an obvious error message.