Hands-On Usage
This effect is commonly used to set the daily Political Power cost for production line assignments to a specific military industrial organization. For example, after a special technology or event is triggered, you can grant the player a "low-cost rapid expansion" reward. It can also be used to dynamically adjust assignment costs when unlocking MIO traits through scripting, combined with variables to implement scalable difficulty systems.
# In an event option, reduce the production line assignment cost for the target MIO
mio:my_tank_manufacturer = {
set_mio_industrial_manufacturer_assign_cost = 0.1
}
Synergy
[add_mio_industrial_manufacturer_assign_cost](/wiki/effect/add_mio_industrial_manufacturer_assign_cost): When you need to make relative adjustments on the existing base value (rather than direct overwriting), use the add command in conjunction; together they enable a "reset baseline then fine-tune" combined logic.
[set_mio_design_team_assign_cost](/wiki/effect/set_mio_design_team_assign_cost): MIOs have two independent cost values for design team assignment and production line assignment; they typically need to be set together to maintain consistency in numerical design.
[has_mio_size](/wiki/trigger/has_mio_size): Before executing, use this trigger to check the MIO scale, thereby deciding whether it's appropriate to modify assignment costs and avoid applying unreasonable values to underdeveloped organizations.
[is_mio_assigned_to_task](/wiki/trigger/is_mio_assigned_to_task): Confirm whether the MIO currently has an active task before modifying assignment costs, preventing logic confusion from cost changes triggered in inappropriate states.
Common Pitfalls
- Passing negative values causes script errors: This effect explicitly prohibits negative number inputs. If newcomers want to implement "reverse subsidies" (i.e., make assignments consume no PP), they should set the value to
0 rather than a negative number; otherwise the game will ignore it or produce a script error.
- Mistaking the scope as a country rather than an MIO: This effect only works within the
INDUSTRIAL_ORG scope. Calling it directly in a country scope (for example, without mio:xxx = { } wrapping) causes the command to silently fail without obvious error messages, making it time-consuming to debug.