Hands-On Usage
has_mio_size is commonly used in events, decisions, or trait unlock conditions related to military industrial organizations to determine whether an MIO has reached a specific size threshold, thereby triggering rewards or unlocking new features. For example, you can restrict high-tier trait unlocks to only organizations that have grown to a certain scale by using it in the available block of an MIO trait:
# In MIO trait definition, requires organization size greater than 5 to unlock
available = {
has_mio_size > 5
}
You can also combine it with variables for dynamic comparisons, allowing thresholds to vary flexibly based on mod logic:
available = {
has_mio_size > var:required_mio_tier
}
Synergy
[add_mio_size](/wiki/effect/add_mio_size): Often serves as a companion effect to "reward further expansion after reaching size conditions"—first use has_mio_size to check size, then use this effect to add size values.
[is_mio_trait_completed](/wiki/trigger/is_mio_trait_completed): Combined usage can construct multiple thresholds—requiring both sufficient organization size and completion of specific traits, commonly seen in elite trait unlocks.
[has_mio_number_of_completed_traits](/wiki/trigger/has_mio_number_of_completed_traits): Used alongside size checks to jointly measure the "overall maturity" of an MIO, preventing overly powerful abilities from being unlocked based solely on size.
[add_mio_task_capacity](/wiki/effect/add_mio_task_capacity): In scenarios where additional task capacity is only unlocked after reaching size thresholds, has_mio_size serves as a prerequisite limit condition.
Common Pitfalls
- Scope Error:
has_mio_size can only be used under the INDUSTRIAL_ORG scope. If written directly in trigger blocks of country or state scope, it will silently fail or even cause errors. You must first switch to the correct scope (such as entering the organization context block through MIO iteration) before using it.
- Comparison Operators Cannot Be Omitted: This trigger must be paired with
< or > operators and does not support direct equality checks like has_mio_size = 5. Beginners copying the equals syntax from regular triggers will cause script parsing failures.