Wiki

effect · clr_mio_flag

Definition

  • Supported scope:INDUSTRIAL_ORG
  • Supported target:none

Description

Clear the matching flag in the military industrial organization in scope.
ex:
var:my_mio_var = {
  clr_mio_flag = my_flag
}

Hands-On Notes

Hands-on notes are AI-generated and checked against the vanilla command vocabulary — treat them as a starting point, not authoritative reference. The definition above is the game's own documentation.

Hands-On Usage

clr_mio_flag is commonly used in dynamic state management scenarios for military industrial organizations. It typically clears temporary markers previously set via set_mio_flag, resetting organizational behavior switches or trigger conditions. Typical use cases include clearing "in-progress" flags after an industrial organization completes a phase of work, or removing corresponding record flags when a player cancels a policy.

# Clear temporary progress flags on an MIO after an event fires
some_mio_scope = {
    clr_mio_flag = upgrade_phase_in_progress
}

# Target an MIO via variable reference and clear its flag
var:my_mio_var = {
    clr_mio_flag = special_contract_active
}

Synergy

  • [set_mio_flag](/wiki/effect/set_mio_flag): These two are complementary operations. Typically set_mio_flag is used to mark first, then clr_mio_flag is used to clear once specific conditions are met, forming a complete state lifecycle management cycle.
  • [has_mio_flag](/wiki/trigger/has_mio_flag): Before clearing a flag, use this trigger to check whether the flag exists first. This prevents executing meaningless clear operations when the flag doesn't exist, resulting in more robust code logic.
  • [modify_mio_flag](/wiki/effect/modify_mio_flag): When you need to modify a flag's value rather than completely remove it, use modify_mio_flag instead. This forms a "modify vs clear" complementary relationship with clr_mio_flag—choose whichever suits your needs.

Common Pitfalls

  1. Incorrect scope type: Beginners often write this command directly within a COUNTRY scope or PROVINCE scope, causing script errors or silent failures. You must ensure the execution environment is an INDUSTRIAL_ORG scope, typically requiring entry through var:xxx references or dedicated MIO iteration blocks.
  2. Flag name spelling inconsistency: The flag name cleared by clr_mio_flag must exactly match the name used when setting it with set_mio_flag (case-sensitive). If the names don't match, the clear operation won't throw an error but effectively does nothing, leaving the old flag in place and causing triggers to continue returning true.